Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I recently moved, and at the same time purchased a new router (Linksys E1200). Prior to the move, I had my old router set up to forward a port for SSH to servers on my LAN, and I was using DynDNS to manage the external IP address. Everything worked great.

I moved and set up the new router (unfortunately, the old one is busted so I can't try things out with it), updated the DynDNS address, and attempted to restore my port forwarding settings. No joy. SSH connections time out, and pings go unanswered.

But here's the weird part (i.e., key to the whole thing?): I can ping and SSH just fine from within this LAN. I'm not talking about the local 192.168.1.* addresses. I can actually SSH from a computer on my LAN to the DynDNS external address. It's only when the client is outside the LAN that connections are dropped.

This surely suggests a particular point of failure, but I don't know enough to figure out what it is. I can't figure out why it would make a difference where the connections originate, unless there's a filter for "trusted" IP addresses, which is perhaps just restricted to my own. No settings have been touched on the servers, and I can't find any settings suggesting this on the router admin interface. I disabled the router's SPI firewall and "Filter anonymous traffic" setting to no avail.

Has anyone heard of this behavior, and what can I do to get past it?

share|improve this question

migrated from serverfault.com Jun 28 '13 at 3:31

This question came from our site for professional system and network administrators.

    
have you gone to canyouseeme.org to test your port? –  Frank Thomas Jun 28 '13 at 3:33
    
I couldn't find a way to put in an arbitrary IP at canyouseeme.org, so I went to yougetsignal.com/tools/open-ports... It says port 22 is closed. But again, when SSHing to the DynDNS address from within the LAN, I can get both servers correctly (according to the port specified). –  WinnieNicklaus Jun 28 '13 at 13:00
    
I believe that your router is not actually sending the traffic out and then back in via your nat. if the port appears closed from the outside, that is likely the case. Check your port forwarding rules and your firewall to confirm that they are both set up to allow traffic on the port and send it to the right place. –  Frank Thomas Jun 28 '13 at 13:15

Your Answer

 
discard

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

Browse other questions tagged or ask your own question.