I’m having issues with joining a domain I set up on my openSUSE 11.2 server. I’m getting a “The network path was not found” error. I have been working at this for hours now and I was wondering if anyone else had some ideas about the problem.
I used the tutorial found here:
How To : Samba PDC+OpenLDAP on openSUSE/SLES Part 1 | Spirit of Change
I am using Windows 7 Ultimate.
I believe I have set all the appropriate Registry values to get Windows 7 to work with Samba 3.4.
Any ideas?
Check out @swerdna’s help
openSUSE SuSE Linux HOWTOs and Tutorials by Swerdna
Thanks for the link. I checked out some of his tutorials, but there wasn’t anything in any of them about setting up a samba server as a primary domain controller.
On Tue April 20 2010 10:56 pm, jrmorrill wrote:
>
> Thanks for the link. I checked out some of his tutorials, but there
> wasn’t anything in any of them about setting up a samba server as a
> primary domain controller.
>
>
jrmorrill;
I assume you have read this, but just in case:
http://wiki.samba.org/index.php/Windows7
What version of Samba are you currently using? Samba 3.4.3 has some serious
problems. I would suggest you try upgrading to Samba 3.5.2, the current
release. The sticky at the top of this forum by swerdna gives details for
the upgrade. I seem to remember that some versions of Samba threw this error
on Win7, but unfortunately I can not find the reference. If I locate it I’ll
post back. We are using 3.4.7 on the PDC and 3.5.2 on the BDC without issue.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Yes, I double checked and all the registry values are there.
My smbstatus says I’m using, Samba version 3.4.2-1.1.3.1-2229-SUSE-SL11.2
On Tue April 20 2010 11:24 pm, PV wrote:
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
On Tue April 20 2010 11:46 pm, jrmorrill wrote:
>
> venzkep;2155384 Wrote:
>>
>> jrmorrill;
>> I assume you have read this, but just in case:
>> ‘Windows7 - SambaWiki’ (http://wiki.samba.org/index.php/Windows7)
>>
>
> Yes, I double checked and all the registry values are there.
>
> venzkep;2155384 Wrote:
>>
>> What version of Samba are you currently using?
>>
>
> My smbstatus says I’m using, Samba version
> 3.4.2-1.1.3.1-2229-SUSE-SL11.2
>
>
jrmorrill;
My last post may not be of much use as it deals with a different problem.
AFAIK, 3.4.2 is OK.
Is this only a problem with Win7 or does the same problem exist with other
flavors of Windows?
Have you ruled out a firewall problem? This could be on Win7 or Linux.
Are the client and PDC on the same subnet? If not, is there a DNS entry
for the PDC or a Wins Server?
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
I do not have any XP machines to test it on at the moment. I can get one to test on tomorrow though.
Yes, I know it’s not firewall issues.
They are on the same subnet but I also have the PDC acting as the WINS server and I included this in my IP configuration for the Win7 Client.
Win7 Client:
10.1.10.160
255.255.255.0
openSUSE Server:
10.1.10.20
255.255.255.0
I seem to have fixed the network path problem. I discovered by pinging the NETBIOS for my domain controller that I was getting two different addresses when I appended the domain suffix.
Server NETBIOS name: ELITE
Domain name: TNWS
From a cmd prompt on my Windows 7 machine:
C:\Windows\system32>ping ELITE
Pinging ELITE [10.1.10.20] with 32 bytes of data:
Reply from 10.1.10.20: bytes=32 time<1ms TTL=64
Reply from 10.1.10.20: bytes=32 time<1ms TTL=64
Reply from 10.1.10.20: bytes=32 time<1ms TTL=64
Reply from 10.1.10.20: bytes=32 time<1ms TTL=64
Ping statistics for 10.1.10.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Windows\system32>ping ELITE.TNWS
Pinging ELITE.TNWS [127.0.0.2] with 32 bytes of data:
Reply from 127.0.0.2: bytes=32 time<1ms TTL=64
Reply from 127.0.0.2: bytes=32 time<1ms TTL=64
Reply from 127.0.0.2: bytes=32 time<1ms TTL=64
Reply from 127.0.0.2: bytes=32 time<1ms TTL=64
Ping statistics for 127.0.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
I checked my local hosts file and then I checked the /etc/hosts file on the domain controller and found that my problem was there.
/etc/hosts
127.0.0.2 elite.TNWS elite
I changed it to be:
10.1.10.20 elite.TNWS elite
This fixed my network path issues, however, I got a new error now…
Any ideas? It could be an authentication problem because I get the same error no matter what credentials I put in. I am not sure what logs to check though.
On Wed April 21 2010 02:26 pm, jrmorrill wrote:
>
<snip>
>
>
> This fixed my network path issues, however, I got a new error now…
>
> [image: http://i.imgur.com/VAGPw.jpg]
>
> Any ideas? It could be an authentication problem because I get the same
> error no matter what credentials I put in. I am not sure what logs to
> check though.
>
jrmorrill;
Check your LDAP entries to look for an existing machine name. If it exists
you could try deleting it and rejoin. Did you try the -i option to the add
machine script? (see the link in my second post)
The default samba logs are in /var/log/samba/log.smbd, this can be changed in
your smb.conf file. If insufficient information is there, try upping the log
level of samba. Add to your /etc/samba/smb.conf a parameter like:
log level = 1 auth:3
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
I ran through all my LDAP settings and I found that my Administrator password was encrypted with a different hash, not SMD5 like the client expected. Fixing this allowed me to join the domain!! I am now a very happy camper.
@venzkep Thank you so much for all the help!!