Well, if it were me....
Microsoft has a nasty habit of wanting to be its REAL ip address. When it
reaches out with RPC and when it tries to register with WINS it tries to
hand off its configured (not its NAT'ed) ip address. So this could be one
issue.
....I'd use a really dumb, cheap box (OpenBSD, Linux, etc.etc.etc.) running
QMail, SMail or SendMail as the inbound mail gateway. I believe you can do
the same thing with a little more work using Microsoft products if you
configure IIS (of some flavor) for mail.
Dan
-----Original Message-----
From: Stacy Williams [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 16, 2001 12:43 PM
To: '[EMAIL PROTECTED]'
Subject: SMTP Gateway for Microsoft - Relaying Purposes
I think the problem that I'm having may be a configuration issue, but I'm
hoping that
someone here can tell me exactly. Here's my situation:
We have a DMZ 172.16.x.x address that has a NAT translation to the public
Internet,
using one network card to access both public and private resources. I'm
having trouble
with authenticating to a Domain in a 192.168.x.x address. The Domain
Controller is also
configured with a NAT translation of 172.16.x.x address. We are basically
attempting to
place a SMTP gateway server to relay inbound and outbound messages to our
internal
Exchange 2000 Server.
Does anyone have any suggestions on either Best Practices or examples of
implementing
a Smart Host / Gateway / SMTP Gateway for an Exchange Server 2000
environment.
Seeking suggestions on the systems aspect, as well as the networking aspect.
Thanks,
> Stacy M. Williams
>
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
