|
Home > Archive > IIS and SMTP > January 2004 > SMTP Virtual Server Address
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 Virtual Server Address
|
|
|
| I have a Win2k machine IIS/SMTP server set up to forward all the mail for my
domain to an Exchange2000 server that is not published externally. I have
setup the Exchange2000 box to use the SMTP server as it's smart host for
delivering mail external to the LAN.
All is well with receipt and delivery of both internal and external mail --
but there is a strange peculiarity in that the (ISA) firewall that
(successfully) delivers outbound mail from the internal IIS/SMTP
server reports (in the firewall log) that the IP address of this outbound
mail connection is that of the IIS/SMTP server machine itself -- and not the
IIS/SMTP Virtual Server's IP address.
The upshot of this is that I cannot configure my ISA Server's protocol rules
to limit the outbound SMTP client address to the IIS/SMTP server's virtual
server IP address -- because all of the outbound traffic seems to show up
labeled as the IP address of the machine itself, and not the virtual
server's address. (Thus, if I limit the SMTP outbound traffic client to only
the IIS/SMTP virtual server, it results in no mail delivery. Setting it to
allow the IIS/SMTP machine address makes it work again.)
I have double and triple checked the SMTP virtual server's IP configuration,
and removed and recreated it several times as well. I have check DNS more
times than I can even remember now, to be sure that the virtual server's IP
address is listed properly.
Shouldn't I expect that the IIS/SMTP outbound traffic would appear as
sourced from the virtual server's address, and >not< from the machine's
address?
Thanks in advance for any insight.
-afh3
| |
| =?Utf-8?B?VG9ueSBTdQ==?= 2004-01-24, 2:05 am |
| Although I haven't seen what you describe, I can guess at the solution...
Disable SMTP socket pooling. By default it's enabled which has the result of the Service operating on all addresses on all interfaces rather than the configured address.
Sound familiar?
Good luck,
Tony Su
| |
|
| Did that already. Didn't matter.
Thanks anyway.
Still hoping for the answer here.
-afh3
"Tony Su" <anonymous@discussions.microsoft.com> wrote in message
news:17DAD374-5329-47D3-AFEF-7B4C3CD33B0F@microsoft.com...quote:
> Although I haven't seen what you describe, I can guess at the solution...
>
> Disable SMTP socket pooling. By default it's enabled which has the result
of the Service operating on all addresses on all interfaces rather than the
configured address.quote:
>
> Sound familiar?
>
> Good luck,
>
> Tony Su
|
|
|
|
|