Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problems with Exchange on W2K server

Status
Not open for further replies.

Yellowbeard

Vendor
May 19, 2003
3
US
Before I ask my question(s), here is my setup

Workstation<-->W2K Server<-->ADSL modem

Workstation
===========
IP - 10.0.0.4
mask - 255.255.255.240
Gateway - 10.0.0.2
DNS - 10.0.0.2
4.2.2.1 (ISP)

***********

W2K Server
===========
Private network
IP - 10.0.0.2
mask - 255.255.255.240
Gateway - None
DNS - 10.0.0.2
4.2.2.1 (ISP)

Public network
IP - 66.58.94.194
mask - 255.255.255.248
Gateway - 66.58.94.193
DNS - 4.2.2.1 (ISP)
216.183.103.5 (ISP)

NAT installed in both interfaces.
Specific port translations in public interface: 21,23,25,80,110

DNS server and Exchange server installed

***********

ADSL modem
===========
Cisco 678
IP - 66.58.94.193
mask - 255.255.255.248

=============================================

I am able to telnet from the outside to ports 25 and 110 on the Exchange server and I can send mail to the outside world, but e-mails I've sent from four different servers on Saturday, have yet to arrive by this morning.

Does anyone see problems with the way this is setup? Is it feasible to run Exchange on the same server that is doing your NAT?

Thanks in advance.....
 
so you've sent mail to your internal exchange server from some outside source (like hotmail) and it's not getting delivered, correct? What about your MX records, have you checked those?
 
Thanks for responding, Bronty...
The MX records are pointing to the right server.
 
Judging from your original post, the Public nic DNS is only pointing to an external IP, and not to your internal DNS. Incoming request could be hitting 66.58.94.194 but not getting resolved since the request is being set back out to 4.2.2.1 (ISP), 216.183.103.5 (ISP). Shouldn't a 3rd address be specified, pointing to 10.0.0.2? You mentioned that the MX records are correct, internally but if no external requests are getting to that internal server, then maybe thats where the problem lies.

Just a thought....


Hewissa

MCSE, CCNA, CIW
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top