Windows – Can’t connect to local web server

networkingweb-serverwebsitewindows

I can't access web content (like a simple HTML file) on my Windows 7 Ultimate x64 machine, either locally or remotely. I tried connecting to IIS (running on port 80) and the built-in Visual Studio web server (running on port 23456) but for some reason, the request never makes it to the web server and both IE and Firefox timeout. The firewall and antivirus have been stopped. I tried accessing the web server using http://localhost, http://127.0.0.1 and http://192.168.1.109 and none work. The hosts file looks like this:

    127.0.0.1       localhost
#   ::1

I tried commenting out both lines and un-commenting both lines. No difference.

So I assume something with the networking stack must be screwed up on this machine. Any advice on diagnosing/fixing this?

Best Answer

Are you sure the web server are running? Type the following commands in a command prompt:

netstat -an | find "80"
netstat -an | find "23456"

If the web servers are running, you should have a similar output:

C:\Documents and Settings\Benoit>netstat -an | find "80"
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING

By the way, if Visual Studio web server is running on port 23456, you must use the following URIs:

According to your output, it really seems a firewall is running on your computer. Have you tried to connect from another computer on your network?

Related Solutions

Web-server – How to make Apache Web Server listen on two different ports

A standard Debian install of apache will have the following fragment of configuration:

Listen 80

<IfModule mod_ssl.c>
    # SSL name based virtual hosts are not yet supported, therefore no
    # NameVirtualHost statement here
    Listen 443
</IfModule>

This is telling apache to listen on port 80 and to listen to port 443 if mod_ssl is configured. In your case you'd want:

Listen 80
Listen 8080

You need to make sure you run a restart, not a reload operation on apache for it to pay any attention to new Listen directives. The safest thing to do is to stop apache, make sure it is dead and start it again.

If this configuration does not work, check the log files for any error messages. You could use "netstat -lep --tcp" to see if there is anything listening on port 8080. Finally, if everything else doesn't work, try running apache under strace to see if it's trying to bind to that port and failing, but not logging the problem.

Windows – Can’t connect to sql server 2008 named instance

Have you tried your.sql.server.fqdn\MC08.

The port specification in SSMS is totally braindead though. For whatever reason they decided to use comma(,) as host and port delimeter instead of colon(:). So if you want to use a port number use this connection string: your.sql.server.fqdn,1045.

Best Answer

Related Solutions

Web-server – How to make Apache Web Server listen on two different ports

Windows – Can’t connect to sql server 2008 named instance

Related Topic