|Subject:||Basic setup of client e-mail on an externally-hosted domain/server|
|Posted by:||Brendhan (Brendh…@discussions.microsoft.com)|
|Date:||Wed, 15 Mar 2006|
I have been running servers with Windows 2000 Server for several years.
Recently, we set up a brand-new LAN in one of our buildings and the new
server has Windows 2003 Server on it. Our e-mail is hosted by a provider
(Verizon) and clients that are using a private IP address range connect fine
through my firewall/router device on my LANs that have a server running
Windows 2000 Server. Two separate domains are in this category and one of
them connects to through the firewall/router device in the other building
using a trust. When I set up my new server (that runs Windows 2003 Server),
I duplicated all of my internal routes, etc. thinking that this new domain
would get through to the firewall router in another building just like the
other "slave" domain does (we are a Town and we are connected over the cable
Clients on the new domain and new LAN can access the Internet just fine but
cannot send or receive mail. Also, interestingly, if I configure a client's
NIC to bypass the server and to access the cable modem directly, it can
access the web AND mail works fine.
As such, it seems that something that I am not familiar with in Windows 2003
Server needs to be configured in order that the mail requests can come and go
freely between the LAN NIC on the server and the cable link NIC on the
server. Again, this is not a general connectivity issue since the web
What gadget in Windows 2003 Server that controls the simple pass through of
e-mail to and from clients do I need to find and how do I need to configure
it. This must be a new element that was not found in Windows 2000 Server.
Thanks for the help.