ISA web publishing very slow/unresponsive
I tried the ISAserver.org community for this one but nobody has replied in several weeks. I recently configured a new network with ISA server 2006 as a web publishing reverse proxy. I have 3 main servers behind it. No clients, literally a network of 4 machines. 1 ISA server firewall/reverse proxy, 1 web server [server 2008], one database server [server 2003 with MySQL], and 1 mail server [server 2003 running hMailServer with RoundCube as a webmail client]. I originally configured this setup because I wanted to have webmail on the mail server and the websites on IIS 7 using host headers, using the same port 80. Previously I always had to have a different port number on the webmail interface.
What I may do if I can't figure this out, is ditch ISA, and then go for something like smoothwall and just use port forwarding and have the webmail client installed on the main web server and point to the mail server. The webmail interface isn't integrated into the mail server software so I should be able to do that.
Thanks for your time in advance, here's the copy paste from ISAserver.org, really hoping someone can help me figure this out.
Hello! I've been running ISA as a reverse proxy in production now for a few weeks and I have to say it's done an excellent job for the most part. Nice and fast. I do have one concern however. [note to edugeek, this is getting far far worse...]
For the most part, EduGeek.net runs quite nicely and very fast. However, once in awhile when you click a link, the browser taskbar will say "Waiting for...." or "Loading...." and the page won't ever load. We are running the latest version of the phpbb forum software [3.0.6] on our website. Not all of our users know to just reclick the link or hit refresh, so sometimes if they come across an endless loading screen they'll just sit and wait. My guess is that there's something wrong with ISA and that it's not passing through the request. Why, I'm not sure. Again, it's very fast, and works very well for the most part, but clicking the odd link will yield "Waiting..." and nothing will happen unless you re-send the request by clicking the link again or hitting refresh. Worse, I've had this happen once where I sit down at my computer, and instead of a few clicks in until I see "Waiting...", it's the first time I visit the site, so right after I type EduGeek.net into the web address bar and hit enter. To me, that's not good because it would make people think the website is down if it doesn't come up right away.
Anybody else noticed this? Again, it could be the web server [Windows Server 2008 running IIS and PHP with FastCGI installed by Web Platform Installer] or it could be something else, but I'm curious to know if this IS ISA or not.
I also have my web server and database server on separate boxes. I have skip-name-resolve enabled on MySQL's my.ini config file and that speeds up the processing to what it should be, but I'm not sure if that would be the issue either. My bets are still on ISA but I can't be sure.
Please let me know if you need any more information from my web publishing rules or network configuration and I'd be happy to share that information to get an answer.
Still trying to figure this out. It was working great, and now I'm having difficulties with all websites on the system. I can't track down whether it's ISA or whether it's the new server [2008 running IIS]. I'm at work at the moment so I can't go restart them, but I'm thoroughly confused. I couldn't access the website at all this morning when I woke up and I tried to check the ISA logs, but when I started a logging session, all I could see was each time I clicked a button on the website [which of course yielded an endless loading page] all the log would show was "Initiated connection..." from what I can remember, and Allowed, and nothing else. Just initiated connection each time I click a link on the website.
Anybody else have any ideas? I'm really confused and can't seem to pinpoint where the problem lies. I think it must be ISA. I'm tempted to just try smoothwall in front and use port forwarding instead of a reverse proxy and see if it's any better. My home router and port forwarding with an old 500MHz server worked more reliably than this.
Thanks so much!