Welcome to ISAserver.org

Suddenly Lost OWA

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Publishing] >> Exchange Publishing >> Suddenly Lost OWA

Page: [1]

Message

<< Older Topic Newer Topic >>

Suddenly Lost OWA - 16.Aug.2007 11:20:51 PM

briano@ounsted.ca

Posts: 12
Joined: 15.Jul.2006
Status: offline

Suddenly our Formes Based OWA has stopped working. The only thing we were doing was moving around a couple of internel DNS servers. I have checked and double checked and I can't understand how this could be the problem. Even though OWA stopped around the same time.

The site was copied from Microsoft's "Publishing Exchange Server 2003 with ISA Server 2006". And Liran Zamir's Step-by-Step Publishing a single Exchange 2003 OWA etc etc. The ISA server is joined to the domain.

We have a private and a public certificate joining the servers together and the certs seem to be intact. I can ping the site name from a client and it resolves to the proper external IP. There is a hosts file on the ISA server resolving the OWA web address to the internal IP of the Exchange server. The only clue I have is that the ISA server log shows "connection denied" for the incoming client IP's.

Active Directory seems fine with all network resources functioning OK. ISA server also provides Email and Web browsing. And there is a DMZ with a functioning Web server.

I have really exhausted all my resources. I don't know what to do next. I guess I could rebuild the ISA server but that is about a 4-6 hour job. I would really appreciate any input anyone might have to help me out.

Thanks
Brian O.

Post #: 1

Featured Links*

RE: Suddenly Lost OWA - 25.Aug.2007 12:35:41 AM

briano@ounsted.ca

Posts: 12
Joined: 15.Jul.2006
Status: offline

Well, I hate to be a party pooper but I really thought someone out there would come up with some suggestion for my problem. But I guess it was far too complex and/or mundane for the lot of you. Nobody wanted to take a stab.

Oh well, I fixed it myself. Maybe no one reads Jim Harrison's efforts, available in a number of places on the web, but I did. And using some of the utilities discussed in his articles, I was able to figure out I was the victim of a socket pooling problem.

Anyway it cost me a lot of time which I feel could have been shortened considerably if somebody out there would have taken my problem to heart and passed on their experiences. I can't be the first, and I won't be the last, to disable socket pooling, but find out 3 days later it does not actually get disabled.

Brian

(in reply to briano@ounsted.ca)

Post #: 2