| Author |
Message |
Steve Manatt
Guest
|
 Posted:
Tue Nov 08, 2005 12:32 am Post subject:
IIS SMTP Mail sent to Exchange 2003 SP2 not being delivered |
|
|
I have serveral web applications (ASP using CDO) that send email messages
based on user input. These applications are run on a dedicated web server
(Windows Server 2003 SP1) on the fbclr.local domain and are sent via the
Smart Host configuration in SMTP to our Exchange Server (Exchange 2003 SP2)
on the fbclr.local domain for delivery.
Sometime around the time SP2 was applied to Exchange I noticed that messages
were no longer being delivered via these ASP applications. Investigation led
me to notice that these messages were in fact in the IIS server's SMTP Queue
folder. The Event Viewer showed the followign message:
Source: smtpsvc
Event ID: 4006
Message delivery to the host '192.168.168.13' failed while delivering to the
remote domain 'comcast.net' for the following reason: The connection was
dropped by the remote host.
These messages happen for any domain.
On the Exchange side, the IIS server is listed under the SMTP protocol as a
Current session and will stay there until it times out.
My guess is that something in SP2 has killed this process because it doesn't
meet some security setting. I guess I have two questions:
1. Is this a SP2 problem/symptom? If so, is there a way to bypass the
security measures for specific servers on Exchange?
2. What specific configuration changes need to be made on the IIS SMTP
service on the web server to meet the new security requirements?
This behavior has been replicated on a Windows 2000 Server and my XP Pro
box. That is why I believe it is the Exchange Server holding the key. There
are two strange behaviors that confound the issue, but may shed some light
too:
1. We have a public web server that is not part of the AD Domain, but still
part of the same IP network. It has no difficulty sending messages using the
same ASP code. I have compared the SMTP settings and nothing is different,
except for the results.
2. If I were to reboot the offending web server, the messages will be
delivered. I thought this was a fluke until I replicated it on my XP box.
Hope you guys can help - been at this for a week now and it is eating my
lunch.
|
|
| Back to top |
|
 |
Steve Manatt
Guest
|
| Posted:
Tue Nov 08, 2005 12:45 am Post subject:
RE: IIS SMTP Mail sent to Exchange 2003 SP2 not being delive |
|
|
One note that I forgot to add - all web servers have been added to the Relay
section of the Exchange's SMTP Protocol.
"Steve Manatt" wrote:
| Quote: | I have serveral web applications (ASP using CDO) that send email messages
based on user input. These applications are run on a dedicated web server
(Windows Server 2003 SP1) on the fbclr.local domain and are sent via the
Smart Host configuration in SMTP to our Exchange Server (Exchange 2003 SP2)
on the fbclr.local domain for delivery.
Sometime around the time SP2 was applied to Exchange I noticed that messages
were no longer being delivered via these ASP applications. Investigation led
me to notice that these messages were in fact in the IIS server's SMTP Queue
folder. The Event Viewer showed the followign message:
Source: smtpsvc
Event ID: 4006
Message delivery to the host '192.168.168.13' failed while delivering to the
remote domain 'comcast.net' for the following reason: The connection was
dropped by the remote host.
These messages happen for any domain.
On the Exchange side, the IIS server is listed under the SMTP protocol as a
Current session and will stay there until it times out.
My guess is that something in SP2 has killed this process because it doesn't
meet some security setting. I guess I have two questions:
1. Is this a SP2 problem/symptom? If so, is there a way to bypass the
security measures for specific servers on Exchange?
2. What specific configuration changes need to be made on the IIS SMTP
service on the web server to meet the new security requirements?
This behavior has been replicated on a Windows 2000 Server and my XP Pro
box. That is why I believe it is the Exchange Server holding the key. There
are two strange behaviors that confound the issue, but may shed some light
too:
1. We have a public web server that is not part of the AD Domain, but still
part of the same IP network. It has no difficulty sending messages using the
same ASP code. I have compared the SMTP settings and nothing is different,
except for the results.
2. If I were to reboot the offending web server, the messages will be
delivered. I thought this was a fluke until I replicated it on my XP box.
Hope you guys can help - been at this for a week now and it is eating my
lunch. |
|
|
| Back to top |
|
|
Steve Manatt
Guest
|
| Posted:
Tue Nov 08, 2005 1:58 am Post subject:
RE: IIS SMTP Mail sent to Exchange 2003 SP2 not being delive |
|
|
The solution ended up being to put the IP address of the IIS Server in it's
SMTP Server's list of allowed Relay hosts. Why, I don't know why - perhaps
one of you smartheads will know why.
Just so it is clear what I did:
The IIS Server that hosts the ASP code has an IP address of 192.168.168.25.
1. I went to the IIS Admin MMC, went to the SMTP Server properties ~ Access
~ Relay
2. I chose "Only the list below" and added 19.168.168.25 to the list
3. I left the bottom checkbox checked that talks about authenticated users
4. Hit OK and mail immediately was delivered
"Steve Manatt" wrote:
| Quote: | I have serveral web applications (ASP using CDO) that send email messages
based on user input. These applications are run on a dedicated web server
(Windows Server 2003 SP1) on the fbclr.local domain and are sent via the
Smart Host configuration in SMTP to our Exchange Server (Exchange 2003 SP2)
on the fbclr.local domain for delivery.
Sometime around the time SP2 was applied to Exchange I noticed that messages
were no longer being delivered via these ASP applications. Investigation led
me to notice that these messages were in fact in the IIS server's SMTP Queue
folder. The Event Viewer showed the followign message:
Source: smtpsvc
Event ID: 4006
Message delivery to the host '192.168.168.13' failed while delivering to the
remote domain 'comcast.net' for the following reason: The connection was
dropped by the remote host.
These messages happen for any domain.
On the Exchange side, the IIS server is listed under the SMTP protocol as a
Current session and will stay there until it times out.
My guess is that something in SP2 has killed this process because it doesn't
meet some security setting. I guess I have two questions:
1. Is this a SP2 problem/symptom? If so, is there a way to bypass the
security measures for specific servers on Exchange?
2. What specific configuration changes need to be made on the IIS SMTP
service on the web server to meet the new security requirements?
This behavior has been replicated on a Windows 2000 Server and my XP Pro
box. That is why I believe it is the Exchange Server holding the key. There
are two strange behaviors that confound the issue, but may shed some light
too:
1. We have a public web server that is not part of the AD Domain, but still
part of the same IP network. It has no difficulty sending messages using the
same ASP code. I have compared the SMTP settings and nothing is different,
except for the results.
2. If I were to reboot the offending web server, the messages will be
delivered. I thought this was a fluke until I replicated it on my XP box.
Hope you guys can help - been at this for a week now and it is eating my
lunch. |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in