Re: Using putty to debug ssh through a firewall
- From: NightStrike <nightstrike@xxxxxxxxx>
- Date: Mon, 20 Aug 2007 05:30:35 -0000
On Aug 18, 11:58 am, purpmint...@xxxxxxxxx wrote:
As for your problem with connecting, the system admin could easily (if
he/she is smart enough) block SSH connections from occuring. It
wouldn't be too hard. And I kind of disagree with J. Nevins, if it
worked before why is it not working now?
Man, I'm dumbfounded: Did you try reinstalling Cygwin's OpenSSH?
The firewall would have to watch for packets containing, for instance,
the version strings of an SSH connection. Remember, I'm going over
port 23, not port 22. Port 23 is still open, so it's not a simple
port closure.
Reinstalling cygwin's openssh would not make sense. Again, it doesn't
work connecting to not one, but two totally separate sshd
installations that worked perfectly and both stopped at the same time,
one on cygwin and another on gentoo.
What I need is a better way to get lower level debugging to see
exactly where it's dying in the handshaking. 'ssh -vvv' obviously
isn't enough.
Oh, and for the record, I have tried from numerous workstations behind
the firewall that all worked fine until some concrete time at which
everything stopped working.
I will also try a different port.. 21 or 80 or something else that's
open.
.
- References:
- Using putty to debug ssh through a firewall
- From: NightStrike
- Re: Using putty to debug ssh through a firewall
- From: purpmint008
- Re: Using putty to debug ssh through a firewall
- From: NightStrike
- Re: Using putty to debug ssh through a firewall
- From: purpmint008
- Using putty to debug ssh through a firewall
- Prev by Date: SSH - Limiting Simultaneous Connections Per User Account
- Next by Date: Re: Using putty to debug ssh through a firewall
- Previous by thread: Re: Using putty to debug ssh through a firewall
- Next by thread: Re: Using putty to debug ssh through a firewall
- Index(es):
Relevant Pages
|
|
