Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I have the openssh-server installed in one pc and I was connecting normally to it from outside and inside the LAN using SSH in the port 10465. However, one week ago or so, I could not connect to it anymore from outside the LAN.

I checked the configuration in the server (sshd_config) and everything seemed just fine, the port was still the same, AllowTcpForwarding was active, the rsa key was fine and also iptables was not blocking that port.

I even checked the port usign www.canyouseeme.org and it was visible from outside, so I don't understand why I can't connect anymore.

I looked over and over google and I can't seem to find something to solve my problem or at least find an explanation to why this is happening. Now it only works from outside the lan if I set the port to 22. Does anyone know how to fix this?

PS: by the way, I'm using ubuntu 13.04 in the client and 12.04 in the server...


share|improve this question
Is there a router between the LAN and the outside? if so, that router's configuration may have been changed and is no longer forwarding port 10465. That's the first thing I'd check. Also, if you're able to connect from other systems in the same LAN when you set it to port 10465, it means Ubuntu is working fine, so there'd be no changes to make there. Let us know about the router. –  roadmr Jul 16 '13 at 20:01
Yeah, there is, but I don't have access to it. In this case, is there a way to find out if the router is blocking ssh access via this port? –  Trino00 Jul 16 '13 at 23:25
If you configure your sshd to listen on port 10465 and you can't connect from outside, it means the router is not forwarding connections from the outside to your computer. I can't tell you more than that, since I don't know your network configuration. If the router is doing NAT (like a home router) then it needs a specific port forwarding configuration for this to work. If your computer has a public IP address and the router just routes packages, then it's most likely explicitly blocking this (and possibly other) port(s). Without more information on network configuration it's hard to say more. –  roadmr Jul 17 '13 at 0:53
add comment

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer


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

Browse other questions tagged or ask your own question.