Click here to Skip to main content
15,886,422 members
Please Sign up or sign in to vote.
2.00/5 (1 vote)
See more:
iam hosting my website on IIS. I am able to access the website via localhost and the system's IP address, but iam unable to access it outside of my local network. I am able to remotely control that machine using mstsc.

I believe that the firewall is completely disabled. What could be the cause of this?
Posted

1 solution

Not very clear. Let me summarize it. You have:
-------   LAN   ------------   WAN   ------------
| IIS |---------| Firewall |---------| Computer |
-------         ------------         ------------

Is this correct?
And you say, from Computer you can access IIS with RDP, but not it's website?

The reason should be that, on the firewall, there is a NAT (Network Address Translation) rule that redirects incoming packets on port 3389 (rdp) to IIS Server.
If you want to also access the website, then there should be a rule for port 80 (http) and/or 443 (https).

EDIT:
It could also be possible that your website is listening on address 127.0.0.1 (localhost), but not on LAN address (which I don't know). You can fix that in IIS MMC console. Not it can't, I misread and thought the site were only accesible through localhost.
 
Share this answer
 
v5
Comments
Sergey Alexandrovich Kryukov 29-Apr-14 18:11pm    
5ed. Also, it's possible that IIS is not exposed to WAN at all.
"I am able to access the website via localhost and the system's IP address" is not clear. Access from where? "Via localhost" means that this is still done from the same computer... :-)
—SA
phil.o 30-Apr-14 3:23am    
It means that it is working when accessing the site through http://127.0.0.1 or http://192.168.0.1, obviously on the same computer. But if it is working locally with LAN address, then it should work on every other equipment on the same LAN segment. At least, that is the way I understand the issue :)
Sergey Alexandrovich Kryukov 30-Apr-14 3:54am    
I know, but it would be impossible to connect to from WAN anyway. That's the point. What I meant is: it could be literally written "http:/localhost", which would also work, but only on the same computer. Or it could be LAN address (which is not really localhost). The expression is not clear, OP should be requested for clarification.
—SA
phil.o 30-Apr-14 3:56am    
OP does not seem to have read the answer. Or at least did not answer to clarification request. Time will tell :)
ashok_89 1-May-14 3:44am    
Hi,<br>
to be clear website is working in lAN and not working when accessed outside through internet iam having an public ip.the same system(where website is there) iam able to take remote using mstsc.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900