exchangesmith
asked on
Event ID 2101
In my exchange 2000 server I noticed an error message as below:
Process MAD.EXE (PID=1560). All Domain Controller Servers in use are not responding.
This is a Topology category error.
Can anyone suggest what caused the error and how to fix it?
Thanks!
Process MAD.EXE (PID=1560). All Domain Controller Servers in use are not responding.
This is a Topology category error.
Can anyone suggest what caused the error and how to fix it?
Thanks!
What is the event ID? Run a dcdiag /v on the computer that is giving the errors, if it is not a dc, then run netdiag /v.
Ok sorry bout that, I saw the ID after I posted that. Not much on that specific event 2101. The source is MSExchangeDSAcess correct? Turn up diagnostics loggin to maximum on DSAccess and also go to MSExchangeSA and turn up NSPI Proxy and RFR Interface to maximum, you do not have to restart any services. Let that run and see if you get any errors.
How many DC's GC's do you have and is the Exchange server a DC or GC?
How many DC's GC's do you have and is the Exchange server a DC or GC?
ASKER
Event ID is 2102, it is a DC but can't run either dcdiag /v nor netdiag /v
Event ID is 2102 or 2101????? Do you get a event ID 9154 also?
ASKER
It is the only DC in the domain.
Please advise how to turn up diagnostics to maximun on DSAccess...
Please advise how to turn up diagnostics to maximun on DSAccess...
ASKER
event ID 2102, no 9154...
Hold off on the logging for now. IF this is the only DC in the Domain then it must be the Global Catalog server also. Save out your application and system log files and send them to me to review at a-jmart@microsoft.com
Hold off on the logging for now. IF this is the only DC in the Domain then it must be the Global Catalog server also. Save out your application and system log files and send them to me to review at a-jmart@microsoft.com
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
A-JMART!! DANG man! I didn't know you were on here too! LOL -
What do you think about the hotfix in Q318067?
Also, let's check DNS -
Is the DC/GC hosting internal A.D. integrated DNS?
If so, does the Exchange server point to itself first for DNS with forwarders setup to external ISP?
We might have to look into creating a topology creation timeout key per Q312859 -
Later,
a-kevcar
What do you think about the hotfix in Q318067?
Also, let's check DNS -
Is the DC/GC hosting internal A.D. integrated DNS?
If so, does the Exchange server point to itself first for DNS with forwarders setup to external ISP?
We might have to look into creating a topology creation timeout key per Q312859 -
Later,
a-kevcar
What happens if this error occurs on SBS2011 / Exchange 2010?