Psst! Did you know DevelopmentNow is a mobile web site design agency?

Contact us for help mobilizing your site, or to sign up for our beta Mobile Web SDK!
all groups > inetserver iis > june 2005 >

inetserver iis : Serving Pages


Kristofer Gafvert [MVP]
6/30/2005 1:21:22 PM
Many ISPs block port 80. Perhaps your ISP do that? You could try to run
IIS on a different port. This may however violate the agreement you have
signed with your ISP (for example if they forbid you to run servers)

You would then access the website using:

http://123.123.123.123:8080/whatever

Assuming 123.123.123.123 is the public IP, and port 8080 is the port you
used instead of 80.


--
Regards,
Kristofer Gafvert (IIS MVP)
www.gafvert.info - My Articles and help
www.ilopia.com


[quoted text, click to view]
James
6/30/2005 2:56:07 PM
I have a cable modem (Adelphia) connection at home. I have IIS installed
and I have a ton of ASP pages and a few virtual directories set up. They
have expected behavior using http://localhost/whatever. I have a router,
and have forwarded port 80 to my machine. I am unable to access
pages/directories using:

http://myipaddress/whatever

....from work. Does this have something to do with my ISP not accepting
traffic of this kind? Is there a way around this? I don't want to run a
public site, just a private one.

Thanks,
James

James
6/30/2005 4:47:19 PM
Bingo...that worked. I figured that was the problem but was unaware of a
setting in IIS to change the port it operates on. You inspired me to find
it and it works just fine now. Thank you. I'll contact them and see if
this falls under acceptable use.

[quoted text, click to view]

AddThis Social Bookmark Button