Windows·65,545 discussions

Active Directory Failure

Locked

After upgrading NT 4.0 SP6a PC to Win2K Pro SP2, can’t browse Directory via explorer, can’t access AD thru snap-ins for Users & Computers or WINS. Can connect with DNS and GPO snap-ins. No error on browse, just displays domain name with nothing else. Admin tools return error: “Active Directory Failure with code ‘0x80040e37′”. The user account can run the admin tools from other PCs and servers, so problem appears local to this upgraded PC.

Topic

Active Directory Failure

In reply to Active Directory Failure

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?

Active Directory Failure

In reply to Active Directory Failure

Re-installing NIC and network did not help, nor did upgrading the driver. DNS and NT browser working, it’s just the remote access into AD that’s not working. I’ve done everything short of re-installing W2K. But the last time I tried that on a PC,I had to format and start over, which is what I’m trying not to do by upgrading from NT 4. Thanks for the suggestions…

Active Directory Failure

In reply to Active Directory Failure

Did you DCPROMO after the upgrade? Has it ever worked sinced the upgrade?

Active Directory Failure

In reply to Active Directory Failure

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.

Active Directory Failure

In reply to Active Directory Failure

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

Active Directory Failure

In reply to Active Directory Failure

I can do everything on the network except run the AD tools. I have already tried it: removed the PC from the domain, removed all networking components and re-installed them, then back into the domain. No good. I got a note from another person who has run into this problem and has a call open with MS. Hopefully, we can all leverage that assistance. We may do application re-installations/upgrades afterward, but all we want to do right now is have the base upgrade work with new W2K software like Admin Tools.

Active Directory Failure

In reply to Active Directory Failure

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.

Active Directory Failure

In reply to Active Directory Failure

This question was closed by the author

[Author]

Replies