Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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 have a virtual machine on some public cloud. the physical IP is not routeble. the ISP provided for me with a public IP and the NAT is being done using the ISP FW.

on that Server I'm running WowzaServer that is running on port TCP 1935 and TCP 80.

when I log in to that server and try to telnet to the public IP on these ports I get connection refused. when I do the same to the physical IP it's working. (it's also working to the public IP when I try to telnet from a remote computer other than the local computer). My ISP says he can't do anything to solve it - I also have the same server on Amazon VPC and it works great!! is there a work around to make my server to listen to my public IP as well? THnaks! Dotan.

share|improve this question
Do you understand how NAT really works? Because here I don't see anything wrong (ie "working as designed(tm)"). – petrus Mar 10 '13 at 14:42
up vote 2 down vote accepted

As you are trying to talk to your own public IP address from behind the NAT I think you need a NAT hairpin. The owner of the router dong the NAT would have to configure this for you but not all routers are capable of this. If your ISP cannot or won't supply you with a hairpin then there isn't very much you can do.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.