Exchange Server 2007 Edge Server DNS DMZ IP problems?

160 pts.
Tags:
DMZ
DNS
Edge Transport Server
IP
Microsoft Exchange 2007
Ok, so we deployed Exchange server 2007 with an Edge server. The Edge server has two network cards. 1 Card for the DMZ in the 10.10.10.x range and 1 in the internal 192.168.13.x. Problem is when it is up and running it works fine, for ~10-12 hours. After it stops receiving email but can still send. I think it has something to do with the server having two default gateways, one to DMZ 10.10.10.1 and the other to the internal gateway of 192.168.13.1. I read up on Harold's Blog (An Exchange Member) and he says that you can't have two gateways. http://blogs.technet.com/haroldwong/archive/2007/03/27/exchange-server-2007-series-part-12-of-24-questions-and-answers-log-02-28-07.aspx I remove the 192.168.13.1 and receiving works but sending fails. Questions are : -What needs to be in the hosts file? -What DNS servers should each NIC be using? Do the DMZ nic use outside DNS? or should it be using internal? -Do I need to resubscribe the edge to the hub after I remove the Internal Gateway? and that would fix sending? Any help is appreciated. Thanks

Answer Wiki

Thanks. We'll let you know when a new response is added.

Again answering my own question here.

Removed the internal gateway. Added to hosts file the correct internal.

Got everything up and running, found out it was the DMZ on the cisco 5505.

Fixed that and everything works.

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Labnuke99
    I'm not sure why you really need 2 NIC's in the edge server. As you see it complicates implementation. Why not go with a single NIC and configure the connectors using that NIC.
    32,960 pointsBadges:
    report
  • ITKE
    Thanks for posting the fix.
    351,865 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following