LinHES Forums http://forums.linhes.org/ |
|
Can't SSH externally. http://forums.linhes.org/viewtopic.php?f=11&t=17194 |
Page 1 of 1 |
Author: | Gibble [ Tue Nov 06, 2007 3:06 pm ] |
Post subject: | Can't SSH externally. |
I can't seem to SSH from my work PC into my mythtv box. I was thinking it was because our firewall is pretty strict here, so, I setup my router to forward requests on external port 21 to port 22 of the mythtv box since I know port 21 is open, I can ftp to download stuff. But, when I try and connect with putty to port 21 of my machine I get "Network Error: Software caused connection abort", almost immediately. Not sure if it's because external ssh access is disabled on the mythtv box, OR if it's my network here at work... Thanks for any suggestions you have, -C |
Author: | manicmike [ Tue Nov 06, 2007 4:00 pm ] |
Post subject: | Re: Can't SSH externally. |
Gibble wrote: I can't seem to SSH from my work PC into my mythtv box.
I was thinking it was because our firewall is pretty strict here, so, I setup my router to forward requests on external port 21 to port 22 of the mythtv box since I know port 21 is open, I can ftp to download stuff. But, when I try and connect with putty to port 21 of my machine I get "Network Error: Software caused connection abort", almost immediately. Not sure if it's because external ssh access is disabled on the mythtv box, OR if it's my network here at work... Thanks for any suggestions you have, -C Routers normally have ports 21 and 23 forwarded to the router itself. The router would always drop connections to these ports. Try a safe port (>1023), such as :2222 forwarded to mythbox:22. Mike |
Author: | Gibble [ Tue Nov 06, 2007 4:06 pm ] |
Post subject: | |
Probably blocked from work, but I tried port 80 since I know it's not blocked outbound from here, and rather than getting the error...it just sorta hung up on a black shell screen with nothing but a cursor. |
Author: | manicmike [ Tue Nov 06, 2007 4:35 pm ] |
Post subject: | |
Gibble wrote: Probably blocked from work, but I tried port 80 since I know it's not blocked outbound from here, and rather than getting the error...it just sorta hung up on a black shell screen with nothing but a cursor.
Safe ports aren't usually blocked unless you have to connect to the web through a proxy (do you?). If you do have to use a proxy, you could poke around a bit and do a port scan, using nmap, of your work's firewall (if you know its IP address) to see what ports are open. Just a small warning, though. Port scanning usually causes network admins to panic a bit (if they notice). Mike |
Author: | Gibble [ Tue Nov 06, 2007 4:36 pm ] |
Post subject: | |
It appears it works fine if I go through port 443 ![]() At least now I know I can get it to work! Now, I just need to find a couple other holes out of this network ![]() |
Author: | nigelpearson [ Tue Nov 06, 2007 6:56 pm ] |
Post subject: | |
Gibble wrote: It appears it works fine if I go through port 443
OK. That probably means that your work has a proxying firewall. Try installing and using a program like ProxyTunnel at work. Here is how I configure it for my employer's firewall: % cat ~/.ssh/config CheckHostIP = no StrictHostKeyChecking = ask Host 134.159.90.120 ProxyCommand /Users/nigel/Bin/proxytunnel -p our-firewall:80 -u nigel -s nigel-password -d %h:22 |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |