T
Tim Anderson
I have never had any problems joining machines to NT or Win2K domains.
Until now...
New Win2K system (it's SBS 2000 but I don't think that's relevant). Most
PCs connect fine, but on a few we've had strange problems. It first
cropped up on a Win2K client - when you tried to join it to the domain it
came up with a "no domain controller found" error message. We checked and
rechecked DNS and DHCP on the server, DCDiag reported no problems.
Ipconfig on the client showed exactly correct results, DNS pointing at the
server, dns suffix correct, etc. You can ping the server by machine name,
by FQDN, by ip number, no problem. You can browse the web through the
server's proxy.
After much googling and half a day on the 'phone with MS tech support
(although Google supplied the answer in the end) we fixed the problem by
deleting two winsock entries from the registry, uninstalling and
reinstalling TCP/IP.
However, we now have the same issue on an XP Pro machine. All as above.
Bizarrely, if you try to join the domain, the error message says "No
domain controller could be found", but the detail of the message reports
that DNS was successfully queried for the DC.
The only clue is that netdiag reports an error of wsasysnotready when
trying to find the DC. This is a low-level error received when trying to
create a socket. We also sometimes get messages about "no network provider
available" or some such. However, there is no way to reinstall TCP/IP on
XP Pro, so the win2k trick won't work. We've tried a couple of things
which claim to reset TCP/IP on XP but they don't work. We tried deleting
the winsock reg entries but that made XP very unhappy and they had to be
restored.
Further info -
The XP machine is fully patched with all the critical updates from Windows
Update
We tried joining a different domain in case this is actually a server
problem. Same error, which pretty much convinces me it is the workstation
rather than the server that is having problems.
Both IP number and DNS are set to automatic via DHCP. We went down the
path of static IP, lmhosts and so on with the errant win2k box, it didn't
help and it shouldn't be necessary anyway.
I believe we could fix it by a complete XP reinstall but I'd much rather
understand what is wrong and fix it, especially as we have it on two
different PCs. They are laptops btw.
Any ideas?
Tim
Until now...
New Win2K system (it's SBS 2000 but I don't think that's relevant). Most
PCs connect fine, but on a few we've had strange problems. It first
cropped up on a Win2K client - when you tried to join it to the domain it
came up with a "no domain controller found" error message. We checked and
rechecked DNS and DHCP on the server, DCDiag reported no problems.
Ipconfig on the client showed exactly correct results, DNS pointing at the
server, dns suffix correct, etc. You can ping the server by machine name,
by FQDN, by ip number, no problem. You can browse the web through the
server's proxy.
After much googling and half a day on the 'phone with MS tech support
(although Google supplied the answer in the end) we fixed the problem by
deleting two winsock entries from the registry, uninstalling and
reinstalling TCP/IP.
However, we now have the same issue on an XP Pro machine. All as above.
Bizarrely, if you try to join the domain, the error message says "No
domain controller could be found", but the detail of the message reports
that DNS was successfully queried for the DC.
The only clue is that netdiag reports an error of wsasysnotready when
trying to find the DC. This is a low-level error received when trying to
create a socket. We also sometimes get messages about "no network provider
available" or some such. However, there is no way to reinstall TCP/IP on
XP Pro, so the win2k trick won't work. We've tried a couple of things
which claim to reset TCP/IP on XP but they don't work. We tried deleting
the winsock reg entries but that made XP very unhappy and they had to be
restored.
Further info -
The XP machine is fully patched with all the critical updates from Windows
Update
We tried joining a different domain in case this is actually a server
problem. Same error, which pretty much convinces me it is the workstation
rather than the server that is having problems.
Both IP number and DNS are set to automatic via DHCP. We went down the
path of static IP, lmhosts and so on with the errant win2k box, it didn't
help and it shouldn't be necessary anyway.
I believe we could fix it by a complete XP reinstall but I'd much rather
understand what is wrong and fix it, especially as we have it on two
different PCs. They are laptops btw.
Any ideas?
Tim