|
Home > Archive > IIS and SMTP > May 2005 > SMTP relay from W2K IIS to Exchange 5.5/NT 4.0
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 relay from W2K IIS to Exchange 5.5/NT 4.0
|
|
|
| We have an NT 4.0 domain using WINS.
Our NT 4.0 domain has a name that looks like 'ABCD' (no dot com etc).
We run MS Exchange 5.5 on an NT 4.0 box.
Our mx record points to our public IP address of our SDSL acct.
Our firewall then forwards SMTP email to our Exchnage 5.5
We have been successfully sending/receiving internet email for years and
do not have an open relay.
Let's call my internet email domain address abcdnet.com. This as well
as mail.abcdnet.com point to our public IP address.
Last week I setup a Windows 2000 IIS server to act as a SMTP relay for
inbound mail only. I got it to work and it worked fairly well until
yesterday. I started to receive event log messages stating:
"Message delivery to remote domain 'abcdnet.com' failed ...: The
connection was dropped by the remote host'.
I'm not sure why after 5 days of working this started to happen. How
woudl I trouble shoot this? Here is what I did when I installed the
SMTP relay.
1) Edited Exchange Server's file c:\winnt\system32\driver\etc\services
to default SMTP to port 26 (previously 25).
2) On the IIS box Default SMTP Server Properties->General->Connection I
changed the Outgoing TCP port to 26
3) On the IIS box UNDER the Default SMTP Server I created a remote
domain named called "abcdnet.com". Under properties I have checked
'Allow incoming mail to be relayed through this domain' checked. I also
'Forward all mail to smart host': internal IP address of Exchange Server.
4) I then pointed the smtp port in the firewall to point to the IIS box.
This setup was partially due to Symantec's suggestions for setting up a
relay to be used with their anti-spam server, whcih is currently not setup.
So I am wondering if perhaps I did something wrong. It worked for
awhile then stopped. We did get hit by some virus yesterday (sobe?) so
we did have a higher than normal load, yet nothign seems to have become
infected.
Keep in mind we do not use DNS for local resolution.
| |
|
| Typical Mickeysoft. Would it be too hard for them to answer my
questions? Too bad for them because I am the lone supporter on Windows
in my corporation. We are moving away from Mickeysoft just for this
reason, no suppor. Hello Linux! Their loss.
and to think we were this close to spending thousands upgrading to e2k3.
ZZTop wrote:
> We have an NT 4.0 domain using WINS.
> Our NT 4.0 domain has a name that looks like 'ABCD' (no dot com etc).
> We run MS Exchange 5.5 on an NT 4.0 box.
> Our mx record points to our public IP address of our SDSL acct.
> Our firewall then forwards SMTP email to our Exchnage 5.5
> We have been successfully sending/receiving internet email for years and
> do not have an open relay.
>
> Let's call my internet email domain address abcdnet.com. This as well
> as mail.abcdnet.com point to our public IP address.
>
> Last week I setup a Windows 2000 IIS server to act as a SMTP relay for
> inbound mail only. I got it to work and it worked fairly well until
> yesterday. I started to receive event log messages stating:
> "Message delivery to remote domain 'abcdnet.com' failed ...: The
> connection was dropped by the remote host'.
>
> I'm not sure why after 5 days of working this started to happen. How
> woudl I trouble shoot this? Here is what I did when I installed the
> SMTP relay.
>
> 1) Edited Exchange Server's file c:\winnt\system32\driver\etc\services
> to default SMTP to port 26 (previously 25).
>
> 2) On the IIS box Default SMTP Server Properties->General->Connection I
> changed the Outgoing TCP port to 26
>
> 3) On the IIS box UNDER the Default SMTP Server I created a remote
> domain named called "abcdnet.com". Under properties I have checked
> 'Allow incoming mail to be relayed through this domain' checked. I also
> 'Forward all mail to smart host': internal IP address of Exchange Server.
>
> 4) I then pointed the smtp port in the firewall to point to the IIS box.
>
>
> This setup was partially due to Symantec's suggestions for setting up a
> relay to be used with their anti-spam server, whcih is currently not setup.
>
> So I am wondering if perhaps I did something wrong. It worked for
> awhile then stopped. We did get hit by some virus yesterday (sobe?) so
> we did have a higher than normal load, yet nothign seems to have become
> infected.
>
> Keep in mind we do not use DNS for local resolution.
>
>
>
>
| |
|
| "ZZTop" <zz@topp.com> wrote in message
news:upHz92cUFHA.1796@TK2MSFTNGP15.phx.gbl...
> Typical Mickeysoft. Would it be too hard for them to answer my
> questions? Too bad for them because I am the lone supporter on Windows
> in my corporation. We are moving away from Mickeysoft just for this
> reason, no suppor. Hello Linux! Their loss.
>
> and to think we were this close to spending thousands upgrading to e2k3.
You were expecting MS to give you support in a newsgroup?
-Dr.X
| |
| Jeff Cochran 2005-05-07, 2:47 am |
| On Thu, 05 May 2005 16:54:10 -0700, ZZTop <zz@topp.com> wrote:
>Typical Mickeysoft. Would it be too hard for them to answer my
>questions? Too bad for them because I am the lone supporter on Windows
>in my corporation. We are moving away from Mickeysoft just for this
>reason, no suppor. Hello Linux! Their loss.
If you want a timely and direct answer from Microsoft, you'll need to
call Microsoft and open a support case. And yes, it isn't free.
[vbcol=seagreen]
>
>and to think we were this close to spending thousands upgrading to e2k3.
>
>ZZTop wrote:
You'll need to post the entire event log error, including source and
ID. Check the SMTP logs on both the W2K and Exchange servers to track
this as well.
[vbcol=seagreen]
First would be to figure out what changed after five days.
[vbcol=seagreen]
> Here is what I did when I installed the
Was there a reason you did 1 and 2?
[vbcol=seagreen]
And is this still configured this way?
[vbcol=seagreen]
Partially? What other parts weren't?
[vbcol=seagreen]
What did you do to clean this? Could you have changed some security
that broke your link? Was this when it stopped working?
[vbcol=seagreen]
No name resolution or relying on broadcast, WINS, HOSTS files or what?
Not that it matters if your IP's are static and you're using IP's for
everything.
Jeff
|
|
|
|
|