Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am trying to connect to my server from my laptop. I have done the port forwarding to the local IP that corresponds to the local IP of my server, using port 3389. The firewall is allowing RDP through and I am able to connect to 192.168.1.100 (the server's local IP) But as soon as I use the public IP of the WAN, I cannot connect

When listening with wireshark, I see that my laptop's ip .102 is trying to reach the server's ip .100 : wireshark screen capture

share|improve this question
    
Which model firewall are you using? –  Wesley Jul 31 '11 at 1:26
add comment

2 Answers

up vote 1 down vote accepted

From the Internet or across your internal network?

If the failure is from inside the network, through the public IP, then it is probably a networking equipment functionality limitation where a lot of SOHO NAT equipment notoriously will not pass traffic from the inside network to its outside WAN interface only to have that traffic attempt to travel back onto the inside interface. In those situations, the port forward/mapping will work correctly when the connection is from the Internet/WAN side.

share|improve this answer
    
It makes sense, I'll give it a try tomorrow! –  JFB Jul 31 '11 at 1:22
    
It's a very common limitation with a lot of the "lower end" networking equipment. –  user48838 Jul 31 '11 at 1:24
    
It works! So the problem was that I was trying to access the server from inside the private network using the public IP! From work, I can connect to the public IP no problem! –  JFB Aug 1 '11 at 13:12
    
Glad it worked out for you. –  user48838 Aug 2 '11 at 4:18
add comment

I have done the port forwarding to the local IP that corresponds to the local IP of my server, using port 3389.

The first thing to do is to launch Network Monitor or Wireshark to find if the RDP traffic is even making it to your server's interface. Perhaps the router isn't even forwarding the traffic. If it's hitting your server but being rejected, it's likely a local firewall issue. I've seen some firewalls present traffic that is from the outside being translated in as the remote IP address. For example, on a SonicWall under certain circumstances the IP address of the remote machine is presented, and not the LAN interface of the SonicWall. Why is this important? Most default Windows firewall instances reject all traffic that isn't from their own subnet.

The firewall is allowing RDP through

Are you sure? Do you have empirical evidence of this?

share|improve this answer
    
The traffic is going through the firewall, because when I am listening on my laptop's ip, i see the packets comming to the local network interface. (see screenshot) When I turn off the firewall, I get the same results. –  JFB Jul 31 '11 at 1:43
    
The screenshot shows to LAN IP addresses, however, what happens when the laptop is off of the LAN and is trying to go through the firewall? –  Wesley Jul 31 '11 at 2:45
add comment

Your Answer

 
discard

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.