Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Mar 12, 2009 09:11 AM by asmund
Mar 09, 2009 11:44 PM|LINK
Been working for over a year with Visual Studio 2005, debugging on localhost (IIS and file system) with no problem. Recently installed Vis Web Developer 2008, and have been debugging on localhost (file system) with no problem.
All of a sudden, when I click on Debug I get error message in IE, with error details stating: "localhost" is not setup to establish a connection on port "49232" with this computer.
I tried System Restore to latest point (an automatic Windows Update install), but the System Restore "did not complete successfully -- unspecified error". Tried to restore to an even earlier point -- same thing.
IE seems to work OK when URL is something like:
http://localhost/mysite/mypage.aspx, but throws the error when URL is
Since system restore doesn't work, I'm dead in the water.
Help will be GREATLY appreciated.
Mar 09, 2009 11:47 PM|LINK
That's a strange one. Perhaps you can try turning off any Virus Scanners / Windows Firefall
temporarily to see if they are causing the problem? I had something similiar where a Windows Firewall rule wasn't playing well with local debugging.
Mar 10, 2009 12:02 AM|LINK
Tried turning off firewalls, still same result.
Any idea where the "allowed" ports for "localhost" are specified?
Mar 10, 2009 02:14 AM|LINK
Other safer things to try first.
(never turn off the firewall without disconnecting internet or turning off modems first)
You might try just creating a new profile on the local machine and see if debugging works for that profile? Have your collague sign on to your machine and test if it works for them?
Mar 10, 2009 04:56 AM|LINK
One possible thing to check is that in IE settings, on the advanced tab under section browsing, make sure that "disable script debugging" is unchecked for IE and other.
Mar 10, 2009 10:30 AM|LINK
All our developers have the same problem today.
Yesterday everything worked fine, but without anything being changed, we have the same problem today.
We fixed it by replacing "::1 localhost" by "127.0.0.1 localhost" in the hosts file.
Don't know why it worked yesterday and not today, but at least we can continue developing now.
-- Pieter Jan
Mar 10, 2009 11:06 AM|LINK
Thanks, just spent an hour and a half in the middle of an urgent project trying to fix that!
Mar 10, 2009 07:01 PM|LINK
WOW -- that did the trick.
How in the world did you come up with that?
BTW, I suspect that an automatic Windows Update is what caused the mischief to begin with.
THANKS VERY MUCH.
Mar 11, 2009 02:10 AM|LINK
Thanks this worked for me too. It would be interesting to know what caused it to quit working.
replacing "::1 localhost" by "127.0.0.1 localhost"
Mar 12, 2009 09:11 AM|LINK
This update caused this:
Definition Update for Windows Defender - KB915597 (Definition 1.53.256.0)
It caused a removal of the IP mapping to localhost in the hosts file located in
You should include this line to the hosts file:
See this thread for details: