Xp Clients Cannot Join Server 2008 Domain, But Windows 7 Can Join

[epcdaniel]

I tried to search for such an issue but have had no luck finding answers that cure the issue. We have an array of XP clients that cannot join the domain offered by the Server 2008 box.

I can get Windows 7 to join the domain, but not any XP machines. I have tried manually setting the DNS server on the client machines to reflect the IP on the same subnet they get an IP from; I can ping the domain from client machines and receive replies. I cannot figure out why they won't join the domain. It errors with cannot join domain.local. Network path not found.

Many forums blame DNS, but if that were the case, why would the client be able to ping the server? Doesn't make any sense. Any enlightenment on this issue would be appreciated. Thank you for your time.

 

[ICTCity]

Hi,

It makes sense!

When you ping something: my.domain.local, the clients looks at resolution of my.domain.local. Which is ok.

When you join a domain, the queries are more than one.

Anyway, try the following (on client side):

route /F
ipconfig /flushdns

Add the following line to the
C:\Windows\System32\drivers\etc\HOST file:
IP_DC domain.local
IP_DC DC.domain.local

Let me know.

 

[epcdaniel]

Hi,

It makes sense!

When you ping something: my.domain.local, the clients looks at resolution of my.domain.local. Which is ok.

When you join a domain, the queries are more than one.

Anyway, try the following (on client side):

route /F
ipconfig /flushdns

Add the following line to the
C:\Windows\System32\drivers\etc\HOST file:
IP_DC domain.local
IP_DC DC.domain.local

Let me know.

Thank you so much for the help. I did however fix the issue as well and one W7 client that wouldn't join. The issue with the XP machines is the service TCP/IP NetBIOS Helper were disabled. Once enabled and started, they were able to join the domain. The one W7 machine that was having an issue I was unaware of when I posted my issue was a service as well.. The NetLogon service was enabled but not starting. When I tried to start it manually, it would start and stop. So I disabled and renabled it (set Automatic), rebooted and it was able to join the domain.

Thank you again. This forum is great.

 

[ICTCity]

Thank you so much for the help. I did however fix the issue as well and one W7 client that wouldn't join. The issue with the XP machines is the service TCP/IP NetBIOS Helper were disabled. Once enabled and started, they were able to join the domain. The one W7 machine that was having an issue I was unaware of when I posted my issue was a service as well.. The NetLogon service was enabled but not starting. When I tried to start it manually, it would start and stop. So I disabled and renabled it (set Automatic), rebooted and it was able to join the domain.

Thank you again. This forum is great.

I'm happy that you resolved your issue... but...

NetBios is required ONLY for netbios names, not for FQDN.

According to this KB http://support.microsoft.com/kb/204279/en-us it can be permanently disabled. There are apps which still use netbios, but actually I think let netbios active is not a great (security) idea...