|
|
You're in the
iis smtp nntp
group:SMTP relay from W2K IIS to Exchange 5.5/NT 4.0
iis smtp nntp:
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. [quoted text, click to view] 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. > > > >
[quoted text, click to view]
"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
[quoted text, click to view]
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. [quoted text, click to view] > >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'. 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. [quoted text, click to view] >> I'm not sure why after 5 days of working this started to happen. How >> woudl I trouble shoot this? First would be to figure out what changed after five days. [quoted text, click to view] > 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 Was there a reason you did 1 and 2? [quoted text, click to view] >> 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. And is this still configured this way? [quoted text, click to view] >> 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. Partially? What other parts weren't? [quoted text, click to view] >> 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. What did you do to clean this? Could you have changed some security that broke your link? Was this when it stopped working? [quoted text, click to view] >> Keep in mind we do not use DNS for local resolution. 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.
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |