localhost pages hanging (possibly because of firewall install)

Hi,

I've suddenly started having problems running pages on my localhost and can't get my head around why. (I'm using IIS 5.1 on Windows XP pro.)

It started yesterday morning when i did 2 things that may have caused the problem:

1) I ran spy-buster, ad-aware and hijack-this trying to stop links to URL randomnly appearing as certain words on any webpage.

2) I installed McAfee firewall plus for the first time.

After this, when I tried to run at php pages that access a mysql database I kept getting an error saying "mysql can't connect to server on localhost" and some number like "1000025" - can't remeber exactly...

Now its gotten worse - no pages on localhost (php, asp or anything) load. I'm not even getting errors anymore - the page just hangs.

I've recovered all the stuff that I quarantined using spy-buster etc. and disabled my firewall - no luck.

Does this sound familiar to anyone?

S

I'm having a similar issue on XP Pro I think due to a recent ZoneAlarm update. If I turn off the firewall IIS and asp are fine.

I'm having the same problem and wondered if anyone has solved this.
I am using iis 5.1 and have frontpage extensions installed. I can't access .htm or .asp. Pages just hang.
I'm using mcafee security center (firewall plus)
cannot access localhost. even if i close mcafee, not that mcafee really closes as i have to manually end processes.
i can ping localhost / 127.0.0.1, but pages hang.
I've tried adding 127.0.0.1 as a trusted ip
I've tried trusting everything on my lan
I've tried opening port 80
Nada!
Would really appreciate a workaround for this.

I managed to solve my problem thus:

I unistalled Windows (don't worry, it was pointless and didn't change anything). I even swicthed from McAfee to Norton and found that I still had more or less the same problem.

The solution I found (for Norton, but hopefully this helps) involved stopping the firewall (Norton Internet Security Center) from running automatically at start-up (aparently this gives IIS a chance to get running properly).

Not sure if there is an equivalent in McAfee (so this may not be relevant to you) but I also found that Norton Anti-Virus' "script-blocking" facility was giving me trouble (simple to disable).

Hope this helps you...

I now have it working. All i did was un-install privacy service. I am not re-installing it either as i've spent too long trying to get this sorted. I tried everything to configure privacy service before un-installing it. Good luck to anyone trying to get a decent answer out of mcafee as well. It's taken me a week to solve what should be an extremely easy fix. I suppose i should have un-installed earlier...I just didn't think that such an obvious requirement would be made unattainable. Maybe there is way to configure privacy service to allow localhost, if i find out i will post it, but don't hold your breath...