|
Home > Archive > IIS and SMTP > November 2005 > smtp delivery failure, connection is dropped by remote host.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
smtp delivery failure, connection is dropped by remote host.
|
|
|
| SMTP mail sends upon boot then the connection is dropped.
We are using MS Exchange smtp server in Exchange 2003 on SBS 2003.
This is a new installation replacing an older server which is just
overloaded.
After building the server, installing exchange with service packs etc.. It
will send mail for a few seconds upon booting then the connection is dropped
by the remote server and no more mail is sent. Recieving mail is no problem
and works fine.
Using a smal host at the isp. I think that DNS is OK. SMTPDiag tests OK. I
have reinstalled IIS and Exchange with no change. This server uses SBS 2003
hence next step is a complete rebuild so would prefer to avoid this as we
have some vertical applications install by vendor on the box and would have
to pay them to come and reinstall.
The first error is:
MSExchangeTransport, Connection Manager
Error 4006, message delivery to the host '123.123.123.123' failed while
delivering to the remote domain 'post.isp.co.uk' for the following reason.
The connection was dropped by the remote hsot.
The old server (which this one is to replace) is configured exactly (!) the
same and works just fine.
smtpdiag will deliver to the smart host and is happy that smtp is configured
OK.
Some message get 'out' but something seems to 'time out' or similar. After
10 to 30 seconds the connection is dropped and will not reconnect.
Using broadband etc...! Browsing is OK.
I have been getting some other error messages that I do not understand as
follows:
MSEcxhangeTransport
Routing Engine/Service
967 (also error 969)
this master server recieved a one level (connector) call back. However no DS
chang has been detected and no major increase will occur as a result. This
should not result in reset route or updated routing packets being sent out to
its subordinate servers and neighboring routing groups.
Since we do not use routing groups I have ignored these to date, but now
think that there must be some connection.
I have other routing group messages - one says that the connectors linkstate
is up (id 973), later followed by one (id 994)saying that the following
connectors linkstate is suppressed because it points to or comes froma leaf
RG node .
However I have not configured a RG, nor do I wish to.
Comments please....
regards
Peter
|
|
|
|
|