Databases
StackOverflow2013
Postsdbo
POWhy can't I make an http request to the ASP.NET development server on localhost?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy can't I make an http request to the ASP.NET development server on localhost?
    text
    copied!<p>I have an ASP.NET project (VS2008 on Windows 7 with either webforms, MVC1, or MVC2 -- all the same result for me) which is just the File->New hello world web project. It's using the default ASP.NET development server, and when I start the server with F5, the browser never connects and I get a timeout. I tried to debug this by telnetting to the development server's port while it was running, and I got the same result:</p> <pre><code>C:\Users\farmercs&gt;telnet localhost 54752 Connecting To localhost...Could not open connection to the host, on port 54752: Connect failed </code></pre> <p>I can see in the system tray that the server thinks it's running, and a <code>netstat -a -n</code> command shows that there is indeed an active TCP listener on that port.</p> <p>This worked in the not-too-distant past, and I could work on web projects using the development server. One thing that has changed since then was that <a href="https://superuser.com/questions/117507/how-can-i-change-the-binding-order-of-network-adapters-in-windows-7">I installed the Microsoft Loopback Adapter</a> to accommodate a local development Oracle installation. I'm not sure this is the problem, but it seems a likely culprit.</p> <p>I also tried to hit the port using the server name itself (<code>http://mycomputername:54752</code>) but with the same result.</p> <p>So, what could be blocking me from connecting? And if it's the loopback, then what is a good way for me to retain my ability to connect to my development Oracle server while still being able to use the ASP.NET development server?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload