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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange & Pix 501 Firewall 2

Status
Not open for further replies.

BobLong

IS-IT--Management
Apr 6, 2006
1
NZ
We are in the process of creating a separate and more secure LAN (Secure LAN) from the Corporate LAN (Corp LAN). I have a Windows 2003 SBS Server with Exchange. The Secure LAN will have an NT4.0 Server for DNS, DHCP and Wins functions for the Secure LAN. There is a mixture of Win 2000 Pro with Outlook XP & XP Pro with Outlook.

The Secure LAN is to have access to the Corp LAN to access Exchange and File services but there will be no access from the Corp to the Secure. I have used an experienced Cisco engineer to setup the Pix and all services are function effectively and immediately except Outlook (Secure LAN) to Exchange (on the Corp LAN) both OS and Outlook versions. Outlook will eventually connect but XP takes several retries and 2003 in cached mode takes approx. 2 minutes to connect. The firewall engineer’s logs are not showing any traffic inside or out until just before Outlook eventually connects. DNS & Wins is functioning correctly (NT4.0 & DNS for a legacy OS).

The Cisco engineer can’t help and I am not sure where to go from here. I am sure/hoping it is a simple fix. It has wasted a lot of time mine and the Tech’s. I would be very grateful if someone would be able to shed some light on my problem.

Best regards.
 
Looks like a DNS issue, try adding exchange IP to hosts file on one of your clients desktop to confirm.

The fact that clients eventually connect proves the correct ports are open on PIX, the fact they take so long proves the name resolution is an issue. I suggest implementing Win2K or newer DNS instead of WinNT.
 
I agree with N0ktar. But I have some other questions.

Did you create some static entries for the CorpLan servers in the SecureLan WINS database? Sounds like you don't even have the NT DNS/WINS/DHCP server set up yet, and this problem will probably go away once you do, and it's configured properly.

ShackDaddy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top