Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MSExchangeAL Event ID 8026 Exchange 2003 SP2

Status
Not open for further replies.

davidyaman

Technical User
Mar 9, 2004
5
NL
I have Exchange 2003 with SP on a Win 2k3 with SP2.
I have DC’s that are GC’s.

Suddenly I receive this error. When it happens the users loose connection. It sometimes is fixed after a few minutes. Sometimes I need to restart the server.

MSExchangeAL
Event ID 8026

LDAP Bind was unsuccessful on directory [Name DC] for distinguished name ''. Directory returned error:[0x51] Server Down.


The solution in the MS KB is not the solution because I haven’t added, promoted or demoted a DC recently.

Is there anything else I can do?

PS if this is answered anywhere else just give me the link. I did a search first and couldn’t find anything.
 
Bump.

I saw this after i migrated my DC 2003 and added a secondary DC as well.

Tried upgrading domain and forest functionality, still getting this.

It lasts for about 10 minutes.

Robert Liebsch
Systems Psychologist,
Network Sociologist,
Security Pathologist,
User Therapist.
 
I't wouldn't be the RUS endpoints, that would not cause users to lose connection. 8026 is also logged in situations where there's only one GC and a kerberos tiket expires. Users can lose connection, evetually the server does get a new ticket, and in the end it starts working on it's own again.

This sounds much more like the issue; i'd explore that route.


rliebsch: Are both DCs GCs?

 
yes both DCs are GCs.

DNS looks fine. Going through the error events seems to hint the problem is somewhere between kerberos and dns.



Robert Liebsch
Systems Psychologist,
Network Sociologist,
Security Pathologist,
User Therapist.
 
I bought a new NIC and after that, the problem was solved. None of the errors have returned. I’ve been error free for about a month now.

So if you have the error try a ne NIC.
 
What was the original NIC? What was the replacement? (Brand, Mode, Driver, firmware)

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top