8 replies
by rob baugh
My initial guess would be to check the DNS settings of the PC. Maybe drop the network card and all the settings and reinstall it. The problems I've had with AD usually center around DNS problems.
One note, can you ping your DNS server by Name as well as IP?
by rejohnson
by expertpc
by rejohnson
It's not the DC that was upgraded, it's a client workstation. The W2K DCs are working fine, as well as accepting administrative access from other W2K Pro clients (new and upgraded). If I knew what '0x80040e37' meant, that might help.
Thanks, anyway.
by expertpc
Sorry about the DC mistake. I reread it and did notice the Pro part. What can I say it was like 2 in the morning when I was answering a lot of questions.
Can you use the net use command? It sounds like you are not "completely" on the network.
I would remove yourself from the domain, then get rid of the TCP/IP protocol stack and everything else. Reinstall all the network "stuff", reboot and try to reenter the domain.
NT to 2000 upgrade tend to cause more headaches then reinstalling all the software and going fresh. Besides, M$ and the Gartner Group recommend that after you do an upgrade you should optimally reinstall all the software so it can make any neccessary registry settings for best performance.
Good Hunting
by rejohnson
by rejohnson
We found out what happened. This PC had the DSCLIENT s/w on it at one point. Although it had been uninstalled months prior to the upgrade, enough of the client remained to hose up subsequent AD access. The fix was to re-install the dsclient (onlyneeded the adsix86.exe part).
KUDOS to Jamie who responded directly to me. They had the same problem, though dsclient was uninstalled after the upgrade in their case.
by rejohnson
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending