Atomic75
asked on
Exchange 2003 MSEchangeAL event ID 8026
I found some reference on this site regarding this problem, but did not seem to locate an actual resolution. I was hoping someone could lend a hand regarding the message ID.
I seem to be getting this message quite often, multiple times a minute. We are currently running 1 Windows 2000 Server DC, one Windows 2003 Server DC, and one Exchange 2003 server. Both DC's are also Global Catalogs I am receiveing this error message on the exchange server and it references both domain controlers in the message description.
I did see some reference to Port 389 and testing connectivity between my DC and my exchange server. Here is what i discovered if this helps.
In Exchange system Manager i am showing LDAP ports of 389 for my DC's and port 3268 for my GC's (both are represented here)
From Exchange server to both DC's i can telent on both ports (389 and 3268)
From both DC's to Exchange i cannot telent on either port.
Do I need to open these ports for LDAP bind to occur? If so, then how do I open those ports?
I seem to be getting this message quite often, multiple times a minute. We are currently running 1 Windows 2000 Server DC, one Windows 2003 Server DC, and one Exchange 2003 server. Both DC's are also Global Catalogs I am receiveing this error message on the exchange server and it references both domain controlers in the message description.
I did see some reference to Port 389 and testing connectivity between my DC and my exchange server. Here is what i discovered if this helps.
In Exchange system Manager i am showing LDAP ports of 389 for my DC's and port 3268 for my GC's (both are represented here)
From Exchange server to both DC's i can telent on both ports (389 and 3268)
From both DC's to Exchange i cannot telent on either port.
Do I need to open these ports for LDAP bind to occur? If so, then how do I open those ports?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Here is what has transpired.
Existing domain consisted of 1 windows 2000 server.
We implemented 2 windows 2003 servers. 1 as file\print server,DC, DNS,DHCP, FTP and the other one for exchange.
We transferred all the roles and global catalog functions to the new DC, everything appeared to be working fine.
We then implemented Exchange server. We began migrating users over to the exchange server from their existing externally hosted POP3 accounts.
At times Active becomes unavailable from Exchange, i cannot get into the Exchange system manager either. It tells me that the domain controller can't be found, or some verbage similar to that. At the same time this happens we record the event ID i listed aobve in the Application event viewer. The server either needs to be rebooted or it will recover itself.
One interesting note. I did notice that all this seems to occur during the time we are importing some rather large PST files into Exchange, some are over 1gig.
I am wondering if this could just be a network saturation problem? Or is Exchange getting bogged down due to the PST file import? Maybe something is not configured properly on Exchange. I do notice I get the same message ID pointing to both of our domain controllers. We got pretty decent hardware for exchange server: 3GHz Intel, 3gig of RAM, Dell Poweredge 2800.
Also I am not logging any errors on either of the domain controllers.
Existing domain consisted of 1 windows 2000 server.
We implemented 2 windows 2003 servers. 1 as file\print server,DC, DNS,DHCP, FTP and the other one for exchange.
We transferred all the roles and global catalog functions to the new DC, everything appeared to be working fine.
We then implemented Exchange server. We began migrating users over to the exchange server from their existing externally hosted POP3 accounts.
At times Active becomes unavailable from Exchange, i cannot get into the Exchange system manager either. It tells me that the domain controller can't be found, or some verbage similar to that. At the same time this happens we record the event ID i listed aobve in the Application event viewer. The server either needs to be rebooted or it will recover itself.
One interesting note. I did notice that all this seems to occur during the time we are importing some rather large PST files into Exchange, some are over 1gig.
I am wondering if this could just be a network saturation problem? Or is Exchange getting bogged down due to the PST file import? Maybe something is not configured properly on Exchange. I do notice I get the same message ID pointing to both of our domain controllers. We got pretty decent hardware for exchange server: 3GHz Intel, 3gig of RAM, Dell Poweredge 2800.
Also I am not logging any errors on either of the domain controllers.
Sorry essaydave...
Looks like I was a little slow on the typing. :-)
Yes Atomic75, it could be as you guessed network saturation.
If this is only happening during importation of 1Gig files then that is the case.
What kind of network cards, switches, hubs etc are you using for your network infrastructure?
Looks like I was a little slow on the typing. :-)
Yes Atomic75, it could be as you guessed network saturation.
If this is only happening during importation of 1Gig files then that is the case.
What kind of network cards, switches, hubs etc are you using for your network infrastructure?
Open Exchange System Manager.
Expand the Recipients container, and then click Recipient Update Services.
Double-click each Recipient Update Service, and then change the Windows domain controller setting to the new Windows domain controller in the domain.
http://support.microsoft.com/kb/272552/en-us