AD Failed after replacing NIC

[Richard]

Hi there,

The old NIC in my win2k server just died, to the point
where the server doesn't boot up if the thing is plugged
in.

So I replaced it with another one and now AD isn't
working. I've tried following the instructions in
articles such as Q263532, however not even DCDiag will
run, giving the following error:

[DC01] LDAP bind failed with error 31,
A device attached to the system is not functioning..

netdiag also shows up errors, as does ntdsutil.

I can't even get AD users and computers up, and ADSI edit
says "No authority could be contacted for authentication"

It's a domain controller (the only one), running on win2k
sp4, with exchange 2003 installed.

I had this problem on another server a whlie ago when
upgrading the NIC to a GB card, is there any way I can
restore connectivity to the AD database without doing a
re-install?

We even considered bringing forward our 2k3 roll-out,
adprep won't run either, so even upgrading is out of the
question.

Any ideas?

Thanks in advance

Richard

 

[Jason Robarts [MSFT]]

Does Device Manager indicate the network card is working correctly? Can you
use it to connect to other services? Have you set the IP address and DNS
servers correctly on the new interface?

Many AD tools use the DC locator to find the DC a DC to connect to. The DC
locator will do a DNS query to find the DC. If the DNS settings on your
computer are not configured correctly you will have problems. The
diagnostic tools will indicate problems if this is not setup correctly.

I'd also check the eventlog for errors.

Jason