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

Having trouble SSH'ing to an internal server that is outside of an enterprise level firewall. I have a fresh install of Fedora 17. Here is the command I'm running:

ssh root@<example-domain.my-company-server.net>

Unfortunately, I get this error response:

ssh: connect to host <example-domain.my-company-server.net> port 22: Connection timed out

I've turned off my local firewall, browsers are connecting to the web fine, and Socks5 proxy is correctly configured. I've hit a brick wall at this point and don't know how to proceed. I can't SSH to the server ... Is it my fault, or could it be a problem beyond my immediate control (like the corporate firewall, or the server configuration)??

New to SSH and would appreciate any help! Thanks and Cheers.


locked by HopelessN00b Jan 21 at 21:38

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as off-topic by HopelessN00b Jan 21 at 21:37

  • This question does not appear to be about server, networking, or related infrastructure administration within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

Check sudo iptables -L and make sure there are no filters at all. –  David Schwartz Jan 30 '13 at 0:48
Is the Fedora 17 the client computer you are using to connect to the remote ssh server? Please clarify. –  Daniel t. Jan 30 '13 at 1:01
Outside a firewall as in not behind the firewall therefore not blocked? The first thing you need to check is that you have SSHD running and listening to port 22. –  Bart Silverstrim Jan 30 '13 at 3:11
Maybe something along the lines of sudo yum install openssh-server ? –  Bart Silverstrim Jan 30 '13 at 3:14
@DavidSchwartz: Hi David. Below is the result of that command. I'm not sure what you mean by filters, because I've been a linux user for 3 years, but I'm sort of newbie when it comes to linux administration. Don't be afraid of offending me with too much information. ;) Thanks for your help! :) Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination –  CodeSlayer2010 Jan 30 '13 at 15:45

2 Answers 2

up vote 0 down vote accepted

Yes, it may be your corporate firewall blocking the port to SSH.

You have to try and access the machine from a place outside the firewall perimeter.

Thanks for the response. I feel like if I was reading my post as someone else, I might think "This guy is trying to hack the corporate intranet and/or do something illegal. That is not the case. My company actually owns the server that I am trying to ssh to, it's just that neither me, nor my supervisor know why the SSH connection keeps hanging, aside from a vague guess that it is proabably the corporate firewall. I'm getting real frustrated because I've got to show some results soon, but haven't been able to do any development because I can't access the dev server. lol. :) –  CodeSlayer2010 Jan 30 '13 at 16:21
I want to add that I have a request into LINUX IT support onsite here to test and see if they are able to SSH to the server in question. However, as yet there has been no response from them. Aslo, in response to your suggestion, that's not a viable solution because _the project requires that I be able to develop on the server from within the corp. intranet_. Thanks. –  CodeSlayer2010 Jan 30 '13 at 16:23
Since you don't seem to have access to the corporate firewall, it will be virtually impossible to troubleshoot this problem without help of your firewall staff. Everything points toward a firewall blocking. –  fboaventura Jan 30 '13 at 20:41
You are correct. It turns out (IT just replied back) there is a new security policy regarding SSH which requires tunneling, that neither I nor my manager were aware of. :P [I'm marking your answer as correct because you're the only one who posted one. Though, if @BartSilverstrim had a votable answer I would have selected him because I feel his answers were most helpful] THANKS TO YOU & EVERYONE WHO HELPED ON THIS ISSUE! –  CodeSlayer2010 Jan 30 '13 at 22:19

I know it's been awhile but I felt I needed to revisit this post to clarify something. It seems now that time has passed and I've learned a little more, that the real problem was my lack of understanding of ssh tunneling. Here are some things that I learned, which may help other newbie LAMP programmers and Network Admins who don't already know this stuff:

1) Port Forwarding and SSH Tunneling ARE THE SAME THING.

2) Basic tunneling from the command line takes this format:

ssh -l<username> -p<ftp_port> <localhost_alias>

Thanks again to everyone who contributed to furthering my understanding on these things. As a community, we help each other grow.



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