Win2K server and XP pro w/ SP2

[bill s via WinServerKB.com]

Does anyone think that using a 2002 copy of Win server 2K (and no updates or
patches) and then trying to join PC's with XP pro and SP2 might cause
problems joining? I am racking my brains over this and even managed to stump
some experts. The only thing that blows this theory away is that the first
time I tried this it seemed Okay. At least for the first 19 out of 21
computers.
I can ping the DC by IP
I can ping by domain name
I can ping by FQDN
My netdiag /fix dispalys everything Okay, but..............still get "cannot
find domain name" when trying to join a PC.
Norton firewall seemed to hold me back too but I since removed it from the
PC's.

thanks

 

[Robert L [MS-MVP]]

I think the DNS has a configuration issue. To test it, ping the problem workstation FQDN from DNS server. Can you ping it (FQDN)? or check this case study,

can't join domain
"A domain controller for the domain could not be contacted" ... Situation: The
client has a domain network and DC, DNS and DHCP is on a Windows 2000 server. ...
www.howtonetworking.com/casestudy/cannotjoindomain1.htm


Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Does anyone think that using a 2002 copy of Win server 2K (and no updates or
patches) and then trying to join PC's with XP pro and SP2 might cause
problems joining? I am racking my brains over this and even managed to stump
some experts. The only thing that blows this theory away is that the first
time I tried this it seemed Okay. At least for the first 19 out of 21
computers.
I can ping the DC by IP
I can ping by domain name
I can ping by FQDN
My netdiag /fix dispalys everything Okay, but..............still get "cannot
find domain name" when trying to join a PC.
Norton firewall seemed to hold me back too but I since removed it from the
PC's.

thanks

 

[bill s via WinServerKB.com]

Robert..
You are getting hotter. Though I can ping from the PC all of IP, domain name,
and the FQDN I cannot do so FROM the DC to the PC. This indicates DSN
problems??
Any advice would be helpful.....meantime I will look at the links you gave me.

Also...
From the server, nslookup says "cannot find server name for address 192.168.1.
4, which is the server IP.
From the PC, nslookup yields the IP address of the DC and lists the DNS
server as the DC.
Should I focus on the Zone files???
Thanks

 

[bill s via WinServerKB.com]

Robert..
You are getting hotter. Though I can ping from the PC all of IP, domain name,
and the FQDN I cannot do so FROM the DC to the PC. This indicates DSN
problems??
Any advice would be helpful.....meantime I will look at the links you gave me.

Also...
From the server, nslookup says "cannot find server name for address 192.168.1.
4, which is the server IP.
From the PC, nslookup yields the IP address of the DC and lists the DNS
server as the DC.
Should I focus on the Zone files???
Thanks

I think the DNS has a configuration issue. To test it, ping the problem workstation FQDN from DNS server. Can you ping it (FQDN)? or check this case study,

[quoted text clipped - 28 lines]

Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/windows-2000-networking/200507/1

Richard...
belay that last message about the PC
nslookup from the PC lists the IP of the DC but says the name cannot be found.

ipconfig/all from the PC lists the IP address of the DC both for DHCP and DNS

 

[bill s via WinServerKB.com]

Robert..
You are getting hotter. Though I can ping from the PC all of IP, domain name,

[quoted text clipped - 15 lines]Richard...
belay that last message about the PC
nslookup from the PC lists the IP of the DC but says the name cannot be found.

ipconfig/all from the PC lists the IP address of the DC both for DHCP and DNS

I mean Richard.............sorry, talking to too many people at once.

 

[bill s via WinServerKB.com]

[quoted text clipped - 6 lines]

ipconfig/all from the PC lists the IP address of the DC both for DHCP and DNS

I mean Richard.............sorry, talking to too many people at once.

No...I mean Robert......(damn)