mgraveney
asked on
Additional Exchange 2003 server on remote site - Mail Queues backing up.
Hi,
I am having all sorts of problems with mail delivery on a new exchange server which I setup in our NYC office. I configured this server in the same way as one a couple of weeks ago on our London site however I am getting queued messages in the Q's.
I have a single SMTP connector on the London site
Both servers are in the same routing group.
The only server allowed to send to the ISP is the london server which is functioning correctly.
Can someone give me some pointers as to why a remote exchange server might be having issues delivering mail to the bridgehead server in london.
I really need to get this sorted this morning as NYC will be in and expect it to be working at lunchtime.
I am having all sorts of problems with mail delivery on a new exchange server which I setup in our NYC office. I configured this server in the same way as one a couple of weeks ago on our London site however I am getting queued messages in the Q's.
I have a single SMTP connector on the London site
Both servers are in the same routing group.
The only server allowed to send to the ISP is the london server which is functioning correctly.
Can someone give me some pointers as to why a remote exchange server might be having issues delivering mail to the bridgehead server in london.
I really need to get this sorted this morning as NYC will be in and expect it to be working at lunchtime.
ASKER
Mailflow between servers is also affected.
Messages stuck in the following q's:
londonserver.domain.com SMTP default virtual smtp
smtp connector - external cluster.com (smtp connector)
Basically anything remote of the server.
Message tracking tells me nothing. I do not get any responses.
I do not have any smart hosts configured on the NYC server.
I suspect there may be some issue with the local domain controller as replication doesn't seem to be happening either. I set up a new user this morning and that has still to arrive on the london DC's.
Getting autoenrollment error 13 on the nyc DC??
Messages stuck in the following q's:
londonserver.domain.com SMTP default virtual smtp
smtp connector - external cluster.com (smtp connector)
Basically anything remote of the server.
Message tracking tells me nothing. I do not get any responses.
I do not have any smart hosts configured on the NYC server.
I suspect there may be some issue with the local domain controller as replication doesn't seem to be happening either. I set up a new user this morning and that has still to arrive on the london DC's.
Getting autoenrollment error 13 on the nyc DC??
try a telnet between the servers and see if that works..
regarding autoenrollment error you can check
https://www.experts-exchange.com/questions/21558305/AutoEnrollment-error-Access-denied-when-trying-to-obtain-domain-controller-certificate.html
regarding autoenrollment error you can check
https://www.experts-exchange.com/questions/21558305/AutoEnrollment-error-Access-denied-when-trying-to-obtain-domain-controller-certificate.html
ASKER
Telnet between domain controllers failed.
I have since run dcdiag which is erroring all over the place about rpc binds.
Found a good link which might be it.
I am now pretty sure the mail is not flowing from the nyuc server to the london server because of the domain controller not functioning correctly.
I have found a usefull article and have applied this patch as this guy did:
https://www.experts-exchange.com/questions/21556078/Active-Directory-Replication-Problem.html?query=server+not+responding+to+rpc+bind&clearTAFilter=true
http://support.microsoft.com/kb/898060/
Just waiting for the DC to reboot.
I have since run dcdiag which is erroring all over the place about rpc binds.
Found a good link which might be it.
I am now pretty sure the mail is not flowing from the nyuc server to the london server because of the domain controller not functioning correctly.
I have found a usefull article and have applied this patch as this guy did:
https://www.experts-exchange.com/questions/21556078/Active-Directory-Replication-Problem.html?query=server+not+responding+to+rpc+bind&clearTAFilter=true
http://support.microsoft.com/kb/898060/
Just waiting for the DC to reboot.
ASKER
The hotfix did not resolve the issue.
I am really stuck here and think its DC related so I am going to close this unless anyone has any brighter ideas and relog as a Domain controller issue.
I am really stuck here and think its DC related so I am going to close this unless anyone has any brighter ideas and relog as a Domain controller issue.
do you have any firewall between the two servers?
ASKER
There are 2 Cisco VPN concentrators setup with a LAN to LAN vpn which allows ANY to ANY traffic.
why?
why?
was thinking whether any ports are blocked or not..
because for the mail flow to work the telnet should work fine..
are you able to do a local telnet on the exchange server itself?
you mentioned earlier that telnet between the domain controllers failed.
is exchange installed on domain controllers?
because for the mail flow to work the telnet should work fine..
are you able to do a local telnet on the exchange server itself?
you mentioned earlier that telnet between the domain controllers failed.
is exchange installed on domain controllers?
ASKER
Sorry, I got that wrong.
Telnet on the domain controllers worked on the ldap port 389
Telnet between the mail servers on port 25 was OK.
Exchange is not on a domain controllers.
I am fairly sure the whole problem is related the the domain controller not even replicating and producing loads of errors from dcdiag.
Starting test: Advertising
......................... servername passed test Advertising
Starting test: KnowsOfRoleHolders
[BBAMDCPRD01] DsBindWithSpnEx() failed with error 1727,
The remote procedure call failed and did not execute..
Warning: xxxxxxxx is the Schema Owner, but is not responding to DS R
PC Bind.
[xxxxxxxx] LDAP bind failed with error 1053,
The service did not respond to the start or control request in a timely
fashion..
Warning: xxxxxxxx is the Schema Owner, but is not responding to LDAP
Bind.
Warning: xxxxxxxx is the Domain Owner, but is not responding to DS R
PC Bind.
Warning: xxxxxxxx is the Domain Owner, but is not responding to LDAP
Bind.
Warning: xxxxxxxx is the PDC Owner, but is not responding to DS RPC
Bind.
Warning: xxxxxxxx is the PDC Owner, but is not responding to LDAP Bi
nd.
Warning: xxxxxxxx is the Rid Owner, but is not responding to DS RPC
Bind.
Warning: xxxxxxxx is the Rid Owner, but is not responding to LDAP Bi
Telnet on the domain controllers worked on the ldap port 389
Telnet between the mail servers on port 25 was OK.
Exchange is not on a domain controllers.
I am fairly sure the whole problem is related the the domain controller not even replicating and producing loads of errors from dcdiag.
Starting test: Advertising
......................... servername passed test Advertising
Starting test: KnowsOfRoleHolders
[BBAMDCPRD01] DsBindWithSpnEx() failed with error 1727,
The remote procedure call failed and did not execute..
Warning: xxxxxxxx is the Schema Owner, but is not responding to DS R
PC Bind.
[xxxxxxxx] LDAP bind failed with error 1053,
The service did not respond to the start or control request in a timely
fashion..
Warning: xxxxxxxx is the Schema Owner, but is not responding to LDAP
Bind.
Warning: xxxxxxxx is the Domain Owner, but is not responding to DS R
PC Bind.
Warning: xxxxxxxx is the Domain Owner, but is not responding to LDAP
Bind.
Warning: xxxxxxxx is the PDC Owner, but is not responding to DS RPC
Bind.
Warning: xxxxxxxx is the PDC Owner, but is not responding to LDAP Bi
nd.
Warning: xxxxxxxx is the Rid Owner, but is not responding to DS RPC
Bind.
Warning: xxxxxxxx is the Rid Owner, but is not responding to LDAP Bi
so were u able to drop a mail when u did a telnet between the exchange servers and was the mail delivered?
XFOR: Telnet to Port 25 to Test SMTP Communication
http://support.microsoft.com/kb/153119/en-us
http://support.microsoft.com/kb/153119/en-us
ASKER
Post Can be closed. I logged a call with microsoft. the probelm was indeed with ad replication and after applying many hotfixes and making changes to reg for ip packet sizes the replication continued. no problems since.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
in which queue are the messages stuck
do you have any smart host configured on the NYC server
what does message tracking tell you