IT Employment

Ask something
Discussion Locked

XP Pro cannot join domain-DNS

0 helpful
4 replies

by /usr 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is the issue. I had expanded a scope to allow more XP clients on a Win2k domain. One client can ping the server, but cannot join domain.
It times out stating the domain controller is not found. I've changed cables, ping LoopBK, and it doesn'tsee the server. It must be some DNS issue,right? With nslkup, it doesn't see itself.

Any clues, cause I'm fried...

4 replies

by timwalsh

Is the computer actually getting an IP address from the DHCP server?

If it isn't, it is probably automatically assigning a private IP address not recognizable on your network segment. Run ipconfig and see what IP is assigned.

by sean d.

go to the command prompt and try doing a ipconfig /flushdns. I had the same problem with a Windows 2k client, and this did the trick. Also are you using DHCP to allocate IP and DNS info? Try setting a static IP.

by michael.schaeffner

Hi,
Could be useful to use /flushdns like mentioned above. You can ping your DC, right? In the same subnet? Or outside? Check your scope again. And again. Try a static IP for your DNS. Did you watch the packets of your workstation?
Hope it helps, have luck
Michael

by /usr

I have been agressivly searching for a solution. I had to rebuild DNS and DHCP. It cannot see the DC on the same subnet. Static did nothing. Even used netdiag and dcdiag. For the whole story, go to http://x220.minasi.com/forum/topic.asp?TOPIC_ID=1585.
I can't of anything else to try. I had read 23 KB articles and they get close but not answer the direct issue.

This discussion is closed to new replies.