Cannot run default web page

I cannot run my default web page from my Terminal Server. I right click the Default Web Site\Browse option in IIS and get the message 'web page is under construction.'

The Default Web Site has (stopped) written after it. Attempted to start it in IIS and get error message: 'The network location could not be reached'.

IIS\Default Web Site\Properties\Web Site Identification details, I have an IP Address of the Terminal Server and Port 80 stated - there are no Host Header Values.

In event log the following error shows with a Source of W3SVC and Event ID of 1130 which states:

"Cannot register the URL prefix 'http://x.x.x.x:80/' for site '1'. The IP address for the site is not in the HTTP.sys IP listen list. The site has been deactivated. The data field contains the error number."

Have run the Httpcfg.exe\Httpcfg query listen and receive: Gateway IP:80 ( not sure whether this should be the IP of the terminal server).

What version of Windows? I don't know anything about Terminal Server connections. www.iisfaq.com is a helpful IIS site, maybe they have something about IIS and Terminal Server.

The terminal server is running Windows 2003 server.

I am running into this same situation. Have you found any resolution to your problem. I am however not useing TS for anything other then remote administration on this W2K3 server. Any input on how you resolved this would be great. Thank you.

On any web server One IP and Port combination can be used for only one site. For example if your Machine IP is 192.168.10.1 and you use Port 80. If you have assigned this IP and Port to one Website, Say default Web Site, and you have another web site on the Same server say abcd.com and you assign the Same IP and Port to that site also, then in that case one one of these 2 sites can run at a time.

To over come this issue you will need to use Host Header. The best usage is Set the IP to (All Unassigned) and Set the Port to 80 for all the Websites configured on the server. On the Advanced properties of the Default Web Site leave the host header blank and add additional identities if required. On the Advanced Properties of other Web Sites remove the Identity with the Blank Host Header and assign a unique Host Header.

This Should Fix your Problem.

------------
Bhaski
------------
Register Domain Names for Less @ NetTicks.com