We're not using any Windows-based NAT service that I'm aware of - we're
just using the NAT capabilities of our humble Linksys BEFSX41 router.
Which is how we had the old server setup (192.168.0.3). And so I just
switched the Port Forwarding to the new server (192.168.0.4) and kept
the rest
Your router may NAT the old IP (192.168.0.3) to a public IP address,
but it may not NAT the new IP (192.168.0.4) to a public IP address.
Can you disable the old box and change the new box to use the old IP
(192.168.0.3) or verify in your router that the new IP (...4) is
properly NAT'ed to a
Matt wrote:
I haven't followed this thread much, but it seems fairly obvious what
the the problem is related to.
When your server is connecting to the recipient's server, it fails to
establish a connection with that server. This log line indicates the
likely source of the problem:
I appear to be able to telnet to that address - it says 220
mailgate02.healthnet.com ESMTP * SMTP Ready *
Darrell ([EMAIL PROTECTED]) wrote:
Matt wrote:
I haven't followed this thread much, but it seems fairly obvious what
the the problem is related to.
When your server is
