I asked this question a few days ago: http://forums.iis.net/t/1192715.aspx
I've been fighting with this for 3 days now and have finally made some headway into determining what the problem is, but still lost on a solution. I noticed that my site that uses ssl (port 443) never had a hiccup on any page requests. I therefore started thinking maybe it was port 80 so I created a few more bindings on one of my sites. The site normally uses an IP like this: 166.99.132.78:80. I added: 166.99.132.78:40050 and 127.0.0.1:40050 for this site particularly and hit both of those bindings over 100x w/o any problems on the server locally. When I try to hit the same site on port 80, I run into the issue where it won't load the page every time. It loads it about three out of seven times on the first try. The other four, I have to hit refresh over and over to get it to load.
It's obviously not a networking issue because I'm calling the pages just fine when on a different port on the server machine itself. As indicated in my other post that's linked above, this server has been serving pages perfectly for over a year and this mess just started a few days ago.
I'm at a complete loss as to what could have caused this and what I can do to fix it. I'm assuming that something else is binding to port 80 on all of my IPs but don't know what or why?
I did a full virus scan the other day and found no problems on that front. Also did a windows update and disk defrag.
how can I see what's being bound to port 80 (assuming that is the culprit). What else could be causing this behavior? I also recreated the windows firewall rule to allow port 80 through and that didn't fix it either.
↧