Windows 2003 can't find domain

Our System...
We have a SBS 2003 box running our network but this concerns a 2003 box that is secondary
domain control, terminal server, fax server, print server, and Autodesk Vault on SQL 2005 express.

How I got into this mess...
We had an auto update from MS (sql 2005 express SP4) which disabled Autodesk Vault.
SP4 can't be uninstalled so I had to uninstall Vault and SQL. Unfortunately they wouldn't reinstall.
Our vendor advised us that the server would need a rebuild in order to reinstall the product. At this
point the server was working fine, just Vault wasn't working. Then I did the dumb thing. I restored the
server from a backup tape to it's state before the problem (which by now was 10 days old)

The problem...
Everything appeared to work fine except that the server cannot find the domain. I can see the network
and mapped drives ok but not much else works. No internet access, ipconfig /renew give " adapter
in permissible state". Netdiag says winsock test faileddns, test failed, dc discovery test failed,
trust relationship test failed, ldap test failed. Obviously active directory isn't working either since it
can't see the domain.

If I just get this talking to the domain again I think I'm actually in good shape and the original software
issue will be resolved as well.
Who is Participating?
Cliff GaliherConnect With a Mentor Commented:
If you have a spare switch, plug the machine into that switch (aka completely isolated) then make sure that its DNS settings only point to itself. It should then see itself as a DC and allow it to demote. This clearly won't replicate back to SBS hence the need to clean up manually, but should *eventually* get you back to a consistent state.

Cliff GaliherCommented:
Sounds like your AD state is very broken. My advice would be to dcpromo the machine in questoin to demote it from thinking it is a domain controller.

On the SBS side of things, go in and manually remove the server from AD and use ntdsutil to clean up the metadata.

Then join the machine to the domain as a member server. Since your AD is still intact and the rest of your backup succeeded, the SIDs should all still be the same and *most* everything should snap back and start working.

Then, if you so choose, you can re-dcpromo the server as a secondary DC (although personally with that many other roles running, I *don't* recommend it...)

RogerC70Author Commented:
Hi Cliff,
Thanks for responding. I tried dcpromo but it fails because it can't see the domain controller. The error message suggests making it a member of a workgroup but this isn't an available option either.
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

RogerC70Author Commented:
Also dcpromo has a message support for specified socket type does not exist in this address family. Forgot to mention I've already tried winsock repairs with the usual netsh int ip... and netsh winsock reset.
RogerC70Author Commented:
I'll try that thanks Cliff.
RogerC70Author Commented:
Thanks for your help Cliff, sorry for taking so long to get back on this.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.