Forefront Edge Security TechCenter >
Forefront Edge Security Forums
>
Forefront Edge Security - General
>
ISA 06, Exchange 07 OWA & Win2k8
ISA 06, Exchange 07 OWA & Win2k8
- I have a problem when I try to access OWA it doesn't let me in. But if i ping my exchange server then try OWA it works fine. It's the strangest thing. If I try to log the traffic on the ISA server I don't see traffic until I ping the server first.
After about 3-5 minutes of an idle connect to reverts back to not working then I have to ping it again.
Ideas?
Thanks
-B
Answers
- Figured it out. It was a third part Traffic shaping application that was causing the problem. It was install on the ISA Server.
- Marked As Answer byNick Gu - MSFTMSFT, ModeratorMonday, October 19, 2009 7:33 AM
All Replies
- Hi,
which guide did you use as the reference?
Here is a good ref:
http://technet.microsoft.com/en-us/library/bb794751.aspx
http://www.msexchange.org/tutorials/Publishing-Exchange-2007-OWA-ISA-Server-2006.html
regards Marc
www.nt-faq.de
www.it-training-grote.de
www.forefront-tmg.de - Marc, I had followed your guide. Only difference is I'm using a signed SSL from godaddy. The weird thing is I have no problems with activesync. If you have any other suggestions please let me know.
Thanks,
-Bryan - Bryan, Is this just for external access? ie if you attempt OWA access from within the network are you seeing the same symptoms?
Can you confirm you have both the ISA2006 supportability update and the ISA2006 sp1 applied?- Edited byKeith AlabasterMVP, ModeratorSunday, October 11, 2009 10:55 AMTypo
- Keith,
This only happens for external access. Yes both the supportability and SP1 are install. I did try changing the external IP on a fluke chance it was related to that, but same problem new IP. I was also wondering if it was Windows 2008 firewall related but I turned it off and still get the same results. I have to ping the server before I can access owa externally.
Thanks,
-Bryan - My ISA 2006 is a two NIC setup and the external NIC has multiple IP's assigned. I didn't think it would matter but do I need to setup something extra? When I created the rules I setup the external network and assosiated said IP for OWA; I did the same with the listener. This is driving me crazy. Any help pointers or suggestions.
Thanks,
-Bryan - Everything else works OK continually? RWW? SMTP? IIS?
Anything else that is a published service on this connection?
Anything popped out from the BPA?
Is it just you having the issue with OWA or all users?
Anything noticed in the isa gui - monitoring - alerts tab?
Anything in the Exchange logs? - Everything else works ok continually.
Exchange 2007 is the only thing published on this IP.
I will check BPA; haven't yet.
We only have a few users on the Exchange 2007 OWA and all users get the same result.
Nothing shows up in the Monitoring / Logging until I ping the server or try to connect to owa multiple times.
Alerts tab doesn't show anything that would point to a cause.
Again same in the logs I don't see anything until it connects or ping the server. - Just a quick check based on your comment, do you have only ex2007 or are you using ex2003 servers in the same exchange group? ie publishing owa from ex2003 as well?
- We have both ex2k3 and ex2k7 one of each in the same group.
I also found that after running BPA I got this
TCP Connections per Minute from One IP Address .... And it's pointing to the internal IP of the Exchange07 Server. Checked the server no viruses but looks like it opening random TCP connections on random ports in the 30000 range. I'm assuming this is why it's blocking the connection until I ping it. figure out how to stop or allow these connections and see what happens - Corrected the issue above and still get the same results.
- Guessed as much - and you are publishing OWA from both? Is it the 2007 or the 2003 service that is giving you issues?
I think the next step will be run a capture through the repro and see if we can determine what is happening. - 2007 is giving me the issues. I will run the repro and see what I come up with, and report back
Thanks Keith,
-Bryan - Figured it out. It was a third part Traffic shaping application that was causing the problem. It was install on the ISA Server.
- Marked As Answer byNick Gu - MSFTMSFT, ModeratorMonday, October 19, 2009 7:33 AM
- Excellent Job Bryan - well done :)
