Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I know this topic is quite old, but, nevertheless, I am doing this in a first time and I have some troubles with it. I try to open public access to my sites, hosted on IIS 7.5 web server on my Windows 7 operation system.

What have I already done:
1. Read a lot of documentation/articles about site hosting, for example:
Besides those links I read Russian documentations, but, since this resource's preferred language is English, I will not post those links.

2. I requested and got public static IP from my provider.

3. Checked this IP value by

4. Hosted simplest site (just some static html page) on my IIS server.

5. Forwarded port 80 on my router:
• Configured virtual server to redirect all requests sent to my public static IP to local IP ( in my case) of my PC where IIS server is running.
• Checked my port 80 on this site. Port is open.
• This is my virtual server configuration:
enter image description here
When I change Interface from <All> to WAN - port is closed
When I add public/private port (end) 80 - port is closed
When I change protocol to TCP/UDP - port is closed
Server name can be any. I even wrote my domain name as server name value - the same result.
When I set remote IP value to my public static IP - port is closed

6. Checked IIS server by typing in browser's address bar. My hosted html page displayed correctly, so server is running.

7. Configured windows firewall to pass all incoming requests by starting firewall from command line and adding new inbound rule, as described here.
• Tried to turn firewall off but result is still the same - could not connect, so I suggest my inbound rule configuration is fine.

8. Turned on all windows IIS features.

9. Got free domain name on
• Successfully pinged domain name. My public static IP was displayed.

10. Flushed DNS cache by ipconfig /flushdns from command line.

But, nevertheless, after all these steps I still get Could not connect to remote server error by requesting my public IP in web browser.

P.S. There was a moment when I got my router's home page, when requested public IP, and a friend of mine also got this page. As Google said, this was some kind of port forwarding error so I think I fixed it, but now I just get could not connect error.


share|improve this question

migrated from Feb 20 '13 at 17:20

This question came from our site for professional and enthusiast programmers.

This might be a better for for Super User or Server Fault. – jadarnel27 Feb 15 '13 at 15:12
@jadarnel27, at server fault I had the same comment, that the question is off topic. – Dmytro Tsiniavskyi Feb 15 '13 at 15:19
Yeah, that's why I also mentioned Super User =) Server Fault is more for corporate environments, but Super User seems like it would be a good fit. – jadarnel27 Feb 15 '13 at 15:42
@jadarnel27, how can I move this question to Super User? – Dmytro Tsiniavskyi Feb 15 '13 at 15:48
@jadarnel27, delete here and repost there? – Dmytro Tsiniavskyi Feb 15 '13 at 15:54
up vote 2 down vote accepted

The problem you are running into is caused by your router not supporting hairpin NAT. A quick search here pulls up some great answers: Unable to outside access service from inside LAN

Basically, your router doesn't know that it needs to convert your request for the external IP to the internal IP of your server. The quickest "fix" is to create an entry in your hosts file.

share|improve this answer
I've already done that, but it doesn't fix the problem... I can't connect to any of my sites via, for example, my android tablet or phone to test and see how those pages look on these devices. – Dmytro Tsiniavskyi Feb 20 '13 at 18:40
Are those devices connected to the same network via Wifi as the server? There's not much else that can be done besides running an internal DNS server, or getting a new router. – KJ-SRS Feb 20 '13 at 20:43
Well, thanks... – Dmytro Tsiniavskyi Feb 21 '13 at 15:52

Site is available from remote machines, but not from my own. From none of my local network machines.

That is completely different issue. You need to directly plug the internet cable to your computer to see the difference.

share|improve this answer
6. Checked IIS server by typing in browser's address bar. My hosted html page displayed correctly, so server is running. – Dmytro Tsiniavskyi Feb 15 '13 at 13:08
Well, here is the funny story )))) A friend of mine tried to request my server, and he got my hosted web page... That means that everything works fine... But I still don't understand why can't I get my page via public IP, only via my local IP. I've already tried on/off trick with windows firewall, result is the same - could not connect. – Dmytro Tsiniavskyi Feb 15 '13 at 13:41
Have you tried flushing your DNS cache? ipconfig /flushdns – levelnis Feb 15 '13 at 13:57
@levelnis, yes, just tried. The same. Site is available from remote machines, but not from my own. From none of my local network machines. – Dmytro Tsiniavskyi Feb 15 '13 at 14:10
You haven't got anything in your hosts file that could be interfering perhaps? – levelnis Feb 15 '13 at 14:58

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .