AD Failed after replacing NIC
From: Richard (anonymous_at_discussions.microsoft.com)
Date: 04/19/04
- Next message: Cley: "Re: Win2kPro to Win2kServer"
- Previous message: Dan: "Adding users to a domain group via a tool or scripting..."
- Next in thread: Jason Robarts [MSFT]: "Re: AD Failed after replacing NIC"
- Reply: Jason Robarts [MSFT]: "Re: AD Failed after replacing NIC"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 18 Apr 2004 18:50:05 -0700
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
- Next message: Cley: "Re: Win2kPro to Win2kServer"
- Previous message: Dan: "Adding users to a domain group via a tool or scripting..."
- Next in thread: Jason Robarts [MSFT]: "Re: AD Failed after replacing NIC"
- Reply: Jason Robarts [MSFT]: "Re: AD Failed after replacing NIC"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|