Can't connect to ssh on domain network at work
up vote
0
down vote
favorite
I have a remote Ubuntu server that I connect to via SSH on a non-standard port. I also have SSH keys set up and have PasswordAuthentication set to no. I am able to connect via PuTTY on Windows machines and ssh on *nix systems just fine, except from my work network. When I'm at work, I try to connect using my Windows laptop. I am able to connect just fine from this laptop at home but not at work. I thought it might be the issue described in this question but I tried changing the ports without success. I even tried allowing traffic on the non-standard port on my Windows Firewall but no luck.
I also have fail2ban enabled, but my work IP is not blocked in ufw or iptables.
The interesting thing is that before I changed the port, disabled password auth, and started using keys, I was able to connect on port 22 just fine at work. But now from PuTTY it just tells me that the connection timed out.
Any ideas?
networking ssh proxy
asked Nov 26 at 23:50
MattR
64
add a comment |
up vote
0
down vote
favorite
I have a remote Ubuntu server that I connect to via SSH on a non-standard port. I also have SSH keys set up and have PasswordAuthentication set to no. I am able to connect via PuTTY on Windows machines and ssh on *nix systems just fine, except from my work network. When I'm at work, I try to connect using my Windows laptop. I am able to connect just fine from this laptop at home but not at work. I thought it might be the issue described in this question but I tried changing the ports without success. I even tried allowing traffic on the non-standard port on my Windows Firewall but no luck.
I also have fail2ban enabled, but my work IP is not blocked in ufw or iptables.
The interesting thing is that before I changed the port, disabled password auth, and started using keys, I was able to connect on port 22 just fine at work. But now from PuTTY it just tells me that the connection timed out.
Any ideas?
networking ssh proxy
asked Nov 26 at 23:50
MattR
64
2
Your work network might have a firewall blocking outbound SSH connections to ports other than port 22.
– Christoph Sommer
Nov 27 at 0:05
I thought that might be the case, but when I change SSH to port 22, I still can't connect.
– MattR
Nov 27 at 16:05
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a remote Ubuntu server that I connect to via SSH on a non-standard port. I also have SSH keys set up and have PasswordAuthentication set to no. I am able to connect via PuTTY on Windows machines and ssh on *nix systems just fine, except from my work network. When I'm at work, I try to connect using my Windows laptop. I am able to connect just fine from this laptop at home but not at work. I thought it might be the issue described in this question but I tried changing the ports without success. I even tried allowing traffic on the non-standard port on my Windows Firewall but no luck.
I also have fail2ban enabled, but my work IP is not blocked in ufw or iptables.
The interesting thing is that before I changed the port, disabled password auth, and started using keys, I was able to connect on port 22 just fine at work. But now from PuTTY it just tells me that the connection timed out.
Any ideas?
networking ssh proxy
asked Nov 26 at 23:50
MattR
64
I have a remote Ubuntu server that I connect to via SSH on a non-standard port. I also have SSH keys set up and have PasswordAuthentication set to no. I am able to connect via PuTTY on Windows machines and ssh on *nix systems just fine, except from my work network. When I'm at work, I try to connect using my Windows laptop. I am able to connect just fine from this laptop at home but not at work. I thought it might be the issue described in this question but I tried changing the ports without success. I even tried allowing traffic on the non-standard port on my Windows Firewall but no luck.
I also have fail2ban enabled, but my work IP is not blocked in ufw or iptables.
The interesting thing is that before I changed the port, disabled password auth, and started using keys, I was able to connect on port 22 just fine at work. But now from PuTTY it just tells me that the connection timed out.
Any ideas?
networking ssh proxy
networking ssh proxy
asked Nov 26 at 23:50
MattR
64
asked Nov 26 at 23:50
MattR
64
asked Nov 26 at 23:50
MattR
64
asked Nov 26 at 23:50
MattR
64
asked Nov 26 at 23:50
MattR
64
64
2
Your work network might have a firewall blocking outbound SSH connections to ports other than port 22.
– Christoph Sommer
Nov 27 at 0:05
I thought that might be the case, but when I change SSH to port 22, I still can't connect.
– MattR
Nov 27 at 16:05
add a comment |
2
Your work network might have a firewall blocking outbound SSH connections to ports other than port 22.
– Christoph Sommer
Nov 27 at 0:05
I thought that might be the case, but when I change SSH to port 22, I still can't connect.
– MattR
Nov 27 at 16:05
2
2
Your work network might have a firewall blocking outbound SSH connections to ports other than port 22.
– Christoph Sommer
Nov 27 at 0:05
Your work network might have a firewall blocking outbound SSH connections to ports other than port 22.
– Christoph Sommer
Nov 27 at 0:05
I thought that might be the case, but when I change SSH to port 22, I still can't connect.
– MattR
Nov 27 at 16:05
I thought that might be the case, but when I change SSH to port 22, I still can't connect.
– MattR
Nov 27 at 16:05
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1378591%2fcant-connect-to-ssh-on-domain-network-at-work%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Your work network might have a firewall blocking outbound SSH connections to ports other than port 22.
– Christoph Sommer
Nov 27 at 0:05
I thought that might be the case, but when I change SSH to port 22, I still can't connect.
– MattR
Nov 27 at 16:05