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

OWA will not connect outside, works fine inside

Status
Not open for further replies.
Jan 15, 2002
126
I just recently set up an ISA 2006 server to use for OWA. The connection goes through my PIX firewall to the ISA box and then to my back-end Exchange box. Everything works fine through the ISA box internally. From the internet, I see some attempted connections on the ISA box but it won't go through. I.E. just sits there for around 30 seconds and then says 'the page could not be displayed'. In the ISA monitor, all I get is 'initiated connection' and 'closed connection'. What could be preventing me from accessing OWA externally? Thanks

----------------
Thanks!
cahelmster [lookaround]
 
I hope hope hope someone answers this because I am having the same problem.

Colleen Gayle Lane
Milton Public Library
 
Initiated / closed on ISA box means that ISA successfully passes the traffic through.
In your case the problem,probably, is with routing. Check it carefully. Check the whole path that each part has a route to the destination.



Victor K (Microsoft Consulting Services)
MCSA/MCSE:Security & Messaging;CNE;CCSE+;CIWSP;CIWSA;Network+;Security+;CCNA;nCSE;CISSP
 
We have two separate Internet connections in my organization with completely different sets of IPs. Right now, our default Internet route is going out the 'old pipe' by default for everything in the organization. So, apparently since I have OWA set to come in the 'new pipe' that it's coming in the new and by default not going back out the new but is being routed out the old pipe.

Apparently, routing was the problem. Thanks GENEnG! I added a route for an IP assigned to the 'old pipe' on my main router pointing to the 'new pipe' and I got it to work externally for that one IP.

Now my situation is figuring out how to leave the organizational default route pointing to the 'old pipe' but have any IPs that come in the 'new pipe' for OWA access to be routed back out the 'new pipe' instead of being sent toward the 'old pipe'. Any ideas?

----------------
Thanks!
cahelmster [lookaround]
 
What you cn try to do i to set 2 Default gateways: 1 per external NIC. Use Metric value to differentiate them.

OWA publishing rule have to have a listener which is listening on both External IP addresses.

In this conf I assume it should work,because both NICs have a default gateway ....

Try that and give your results.



Victor K (Microsoft Consulting Services)
MCSA/MCSE:Security & Messaging;CNE;CCSE+;CIWSP;CIWSA;Network+;Security+;CCNA;nCSE;CISSP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top