Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

ssh tunneling to a windows box problem

Subject: ssh tunneling to a windows box problem
Date: Wed, 11 Jan 2006 11:19:32 +0000
Hi guys,

I'm trying to tunnel from my FC4 box (OpenSSH_4.0p1) through a firewall box (RH9, sshd: SSH Secure Shell 3.2.0 (non-commercial version), TCP forwarding is on) to a Windows 2000 server machine (on which I have deactivated the firewall and set VNC to allow incoming connections from the firewall box) so I can connect securely with VNC. Something is going wrong though. I make the tunnel like this:

ssh -vv -L 5901:192.168.1.112:5900 root@firewall

This is the verbose output:

...
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
debug1: Local connections to LOCALHOST:5901 forwarded to remote address 192.168.1.112:5900
debug1: Local forwarding listening on 127.0.0.1 port 5901.
debug2: fd 4 setting O_NONBLOCK
debug1: channel 0: new [port listener]
debug1: Local forwarding listening on ::1 port 5901.
debug2: fd 5 setting O_NONBLOCK
debug1: channel 1: new [port listener]
debug1: channel 2: new [client-session]
debug2: channel 2: send open
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 2
debug2: channel 2: request pty-req confirm 0
debug2: channel 2: request shell confirm 0
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 2: open confirm rwindow 100000 rmax 16384
...


ok now the tunnel is connected.. I do a vncviewer localhost::5901

...
debug1: Connection to port 5901 forwarding to 192.168.1.112 port 5900 requested.
debug2: fd 9 setting TCP_NODELAY
debug2: fd 9 setting O_NONBLOCK
debug1: channel 3: new [direct-tcpip]
debug1: channel 0: free: port listener, nchannels 4
debug1: channel 1: free: port listener, nchannels 3
debug1: channel 2: free: client-session, nchannels 2
debug1: channel 3: free: direct-tcpip: listening port 5901 for 192.168.1.112 port 5900, connect from 127.0.0.1 port 41657, nchannels 1
Connection to 192.168.1.118 closed by remote host.
Connection to 192.168.1.118 closed.
debug1: Transferred: stdin 0, stdout 0, stderr 89 bytes in 86.8 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 1.0
debug1: Exit status -1
...


And that's where it ends (and the connection to the firewall gets severed as well). Anybody got any ideas?

Cheers,
Tim

p.s. I can VNC into the machine normally from the one I'm trying to do this from (both are on the same side of the firewall at the moment but if I get it working I'll be coming in from the other side)

<Prev in Thread] Current Thread [Next in Thread>
  • ssh tunneling to a windows box problem, Tim Nugent <=