asked on

IIS 7.5 does not seem to be working

I am running IIS 7.5 on WinSvr2k8R2. I have added web sites. If I browse a site on port 81 inside IIS Manager, it displays fine. If I try to access the site from another computer on my lan I get the dreaded IE cannot connect to nnn,nnn

I have port range forwarding (80-85) in my router to my server IP enabled.

Any ideas?

Mike

becraig

First you need to specify the non-standard port when you browse:

You want to look into host headers so you can bind the site to port 80 without specifying a port.

http://www.iis.net/configreference/system.applicationhost/sites/site/bindings/binding

rg20

or
http://yoursite.com:81

Aaron Tomosky

And probably open those ports in windows firewall if you do go that route, but I agree host headers Is much much better

David Johnson, CD

Windows Firewall is probably the problem you need to add the additional ports into the incoming area. and as stated above
http:\\servername:81\
http:\\servername:82\ etc

msoul

ASKER

Thanks for the ideas. I don't think it is the firewall since I turned it off on both the server and client and no effect.

Mike

msoul

ASKER

Alright folks, I have been up all night trying your suggestions and some of my own. I have attached a summary of what is happening. I can supply anything else that would help you figure this out. It has gone truly weird on me as you will see if you read the summary. May the force be with you and I really do appreciate your help.

Mike
IIS-Problem-background.docx

becraig

I am guessing port binding is not configured correctly.

Your doc indicates you are binding the sites w/o additional hostnames.

1. If you have additional sites will they have their own host headers ?

you need to have a hostnane bound e.g site1.domain.com

ASKER CERTIFIED SOLUTION

David Johnson, CD

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

msoul

ASKER

Thank you, thank you, thank you! Problem is solved. And each of you contributed a piece to the overall solution. You are all rock stars in my book. I had purchased a Seagate SAN and installed it in my network. What they don't tell you in their documentation is that they hijack port 80 to permit remote access to the SAN. Frustrated with the SAN for unrelated reasons I disconnected it from the network and uninstalled their software. The next time my Web server was accessed the bogus screen started to appear. Unfortunately I did not connect the two events in my head. Turns out that the bogus screen was in the Web server cache and kept reappearing. As soon as I click the refresh button on the browser the problem went away and everything works as it should. You folks are great.