Trouble tunneling from debian to Windows 7 within LAN

3 posts / 0 new
Last post
lethal-duck
Offline
Last seen: 8 years 1 month ago
Joined: 08.08.2010 - 12:41
Trouble tunneling from debian to Windows 7 within LAN

Hi.

I'm having a problem being able to tunnel from my debian lenny box to a Windows 7 64 bit machine.
I installed copSSH the usual way. By following the directions here http://www.itefix.net/i2/copssh
I can ssh to the Windows machine, but not tunnel.
My intention is to ... once the tunnel is up ... RDP.
I've done this before and have been doing so for quite some time, using OpenSSH to a Windows XP SP3 box without issue.
I would have continued to use OpenSSH with out copSSH if it worked for Windows 7.
I use almost an idendticle command to establish my tunnel to the XP box.
ssh -v -f -L 3390:localhost:3389 -C -N MyUser@MyXPServerBox
So I'm picking my client is setup fine.
I've oppened port 22 on the windows firewall (this should be fairly obvious as straight SSH works fine). I'm just having trouble with establishing a tunnel.
Once the tunnel is up, I'll RDP through to the Windows 7 box, the same as I normaly do with my XP Server.
This is the output of my client ssh

MyUser@MyClientBox:~$ ssh -v -f -L 3392:localhost:3389 -C -N MyUser@MyServerBox
OpenSSH_5.1p1 Debian-5, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to MyServerBox [192.168.0.253] port 22.
debug1: Connection established.
debug1: identity file /home/MyUser/.ssh/identity type -1
debug1: identity file /home/MyUser/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/MyUser/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.4
debug1: match: OpenSSH_5.4 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-5
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 zlib@openssh.com
debug1: kex: client->server aes128-cbc hmac-md5 zlib@openssh.com
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'MyServerBox' is known and matches the RSA host key.
debug1: Found key in /home/MyUser/.ssh/known_hosts:6
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering public key: /home/MyUser/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Trying private key: /home/MyUser/.ssh/identity
debug1: Trying private key: /home/MyUser/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
MyUser@MyServerBox's password:
debug1: Enabling compression at level 6.
debug1: Authentication succeeded (password).
debug1: Local connections to LOCALHOST:3392 forwarded to remote address localhost:3389
debug1: Local forwarding listening on 127.0.0.1 port 3392.
bind: Address already in use
debug1: Local forwarding listening on ::1 port 3392.
bind: Address already in use
channel_setup_fwd_listener: cannot listen to port: 3392
Could not request local forwarding.
debug1: Requesting tun unit 2147483647 in mode 1
debug1: sys_tun_open: failed to open tunnel control interface: Permission denied
Tunnel device open failed.
Could not request tunnel forwarding.
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
MyUser@MyClientBox:~$

In looking at the file permissions of the default copSSH install. They appear considerably more open that I'm used to seeing with a standard (say Linux/BSD) SSH install.
The C:\Program Files (x86)\ICW\home\MyUser dir I would have thought should be read, wright for the user and by none other. but it's available to all users of the box.
It's been a while since I've done a full SSH setup incl key pair.
I'm just trying to get the password auth method tunneled, then I'll look at setting up key pair auth.

Any help will be appreciated.
 

lethal-duck
Offline
Last seen: 8 years 1 month ago
Joined: 08.08.2010 - 12:41
Solved.

Got this sorted. I'll try and get my solution to this posted soon.

lethal-duck
Offline
Last seen: 8 years 1 month ago
Joined: 08.08.2010 - 12:41
Post