SMTPSVC: EventId 4006 (The remote server did not respond to a connection attempt)

  • Thread starter Thread starter mejje
  • Start date Start date
M

mejje

I'm running the IIS SMTP and DNS service on the same server, outgoing
mail to most (!) domains fails with an event log id 4006:

Message delivery to the host 'xxx.xxx.xxx.xxx' failed while delivering
to the remote domain 'remotedomain.com' for the following reason: The
remote server did not respond to a connection attempt.

Manually NsLookup:ing the MX-records of the remote domains works fine,
however the eventlog ip-address differs from the NsLookup:ed
MX-records, always on the same subnet, just a different computer
(where port 25 usually is closed).

Server configuration follows:

Host: MAILSERVER
Primary DNS suffix: domain.com
Workgroup: domain.com

2 nics, both adapters configured static ip-adresses and no DNS entries
(popup telling me local server is running DNS service), no connection
specific dns suffix.

DNS server:
SOA: domain.com
NS: ns1.domain.com
NS: ns2.domain.com
MX: domain.com
A: ns1
A: ns2
Listening on all (2) ip-addresses, forwarders configured.

SMTPSvc:
Listening on all (unassigned) ip-addresses, FQDN: domain.com, no
masquerade domain or smart host.

SMTPSvc\Domains:
mailserver.domain.com Local (Default)
domain.com Local (Custom)

Any and all help will be much appreciated, I believe I've tried every
solution mentioned here on the related error EventId 4000 with no
success.
 
In
mejje said:
I'm running the IIS SMTP and DNS service on the same server, outgoing
mail to most (!) domains fails with an event log id 4006:

Message delivery to the host 'xxx.xxx.xxx.xxx' failed while delivering
to the remote domain 'remotedomain.com' for the following reason: The
remote server did not respond to a connection attempt.

Manually NsLookup:ing the MX-records of the remote domains works fine,
however the eventlog ip-address differs from the NsLookup:ed
MX-records, always on the same subnet, just a different computer
(where port 25 usually is closed).

Server configuration follows:

Host: MAILSERVER
Primary DNS suffix: domain.com
Workgroup: domain.com

2 nics, both adapters configured static ip-adresses and no DNS entries
(popup telling me local server is running DNS service), no connection
specific dns suffix.

DNS server:
SOA: domain.com
NS: ns1.domain.com
NS: ns2.domain.com
MX: domain.com
A: ns1
A: ns2
Listening on all (2) ip-addresses, forwarders configured.

SMTPSvc:
Listening on all (unassigned) ip-addresses, FQDN: domain.com, no
masquerade domain or smart host.

SMTPSvc\Domains:
mailserver.domain.com Local (Default)
domain.com Local (Custom)

Any and all help will be much appreciated, I believe I've tried every
solution mentioned here on the related error EventId 4000 with no
success.
Click to expand...

Is there anything else installed? Such as:
Symantec AV? If so, did you update it? I had a client just the other day
using a Symantec product getting the same exact message and it happened
right after he installed SP4. I ran Live Update on it and the errors went
away.

If not, what other software, SP level, etc.

Also, not sure what you mean by this:
Manually NsLookup:ing the MX-records of the remote domains works fine,
however the eventlog ip-address differs from the NsLookup:ed
MX-records, always on the same subnet, just a different computer
(where port 25 usually is closed).
Click to expand...
Do you mean you are getting an internal IP on your same subnet for the
record when you use nslookup?


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Is there anything else installed? Such as:
Symantec AV? If so, did you update it? I had a client just the other day
using a Symantec product getting the same exact message and it happened
right after he installed SP4. I ran Live Update on it and the errors went
away.

If not, what other software, SP level, etc.
Click to expand...

No, Symantec AV is not installed, the os is Windows 2003 (fully
updated). Also running DHCP server, RRAS and Media Services.
Also, not sure what you mean by this:
Do you mean you are getting an internal IP on your same subnet for the
record when you use nslookup?
Click to expand...

No, if the manual nslookup resolves the MX record to 100.100.100.5 for
domain.com, the eventlog says it tried 100.100.100.4 for example. I'm
certain it's not a MX-record but instead another host on the same
domain.

I think I solved the problem just now by entering 127.0.0.1 as
DNS-servers on the NIC properties! When left blank Windows responded
with something like "DNS configured to local machine", but ipconfig
/all didn't show any DNS-entries on the NIC:s. As soon as the
DNS-server was configured manually the Queue folder emptied :-).

Thanks for helping though!
 
In
mejje said:
No, Symantec AV is not installed, the os is Windows 2003 (fully
updated). Also running DHCP server, RRAS and Media Services.


No, if the manual nslookup resolves the MX record to 100.100.100.5 for
domain.com, the eventlog says it tried 100.100.100.4 for example. I'm
certain it's not a MX-record but instead another host on the same
domain.

I think I solved the problem just now by entering 127.0.0.1 as
DNS-servers on the NIC properties! When left blank Windows responded
with something like "DNS configured to local machine", but ipconfig
/all didn't show any DNS-entries on the NIC:s. As soon as the
DNS-server was configured manually the Queue folder emptied :-).

Thanks for helping though!
Click to expand...

No problem for the help. My only concern is that it's recommended NOT to use
127.0.0.1 for the DNS address, but rather your own intenral server. Now if
you had other DNS servers stated in your properties (such as your ISP's),
unpredicatable results can occur.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top