janhoedt
asked on
SSh-Tunnel via putty
Hi,
I succeeded to make a ssh-tunnel to my home network via putty (logged in, can ping ip's).
Now I would like to redirect my browser to be able to connect to my home configs, pc's. That what doesn't work. I've set firefox to use 127.0.0.1 on port 1080. Putty shows D1080 underneith the tunnel option.
Now when I try to connect to any address, it doesn't do anything. Don't know how to troulbeshoot since everything looks ok ....
Please advise.
J.
I succeeded to make a ssh-tunnel to my home network via putty (logged in, can ping ip's).
Now I would like to redirect my browser to be able to connect to my home configs, pc's. That what doesn't work. I've set firefox to use 127.0.0.1 on port 1080. Putty shows D1080 underneith the tunnel option.
Now when I try to connect to any address, it doesn't do anything. Don't know how to troulbeshoot since everything looks ok ....
Please advise.
J.
yobri
You have Firefox configured to use SOCKS for proxy connections, right?
ASKER
Correct
ASKER
Correct
What OS and SSH server product are you using?
ASKER
Xp and synology nas
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I've actually configured two WinSSHD (Bitvise) servers in the last two weeks; both work great for all traffic (http/https included.) If you need to redirect traffic from command-line (or any other applications which do not support proxies directly), I recommend Proxifier. This point here is you do NOT generally need to configure a separate http/https proxy.
Going back to your problem... have you verified the user account itself has been configured on the server side to permit C2S/S2C port forwarding. With WinSSHD, the port forwarding configuration is on the user/group configuration level rather than server.
Going back to your problem... have you verified the user account itself has been configured on the server side to permit C2S/S2C port forwarding. With WinSSHD, the port forwarding configuration is on the user/group configuration level rather than server.
ASKER
Have been able to make it work. However only over an openvpn-tunnel.
http://www.nikhef.nl/~janjust/nikhef-proxy/, the thing is, only proxy socks 5 should be used.
Now this works over the proxy-tunnel, not when I go via putty only (directly to my dyndns-address), I get stuck at the proxy (port 80). It won't authenticate, however I've set the proxy-settings in putty.
Note: when I connect over port 8080 (they all redirect to port 22 = ssh on my NAS) it works fine, but I need port 8080 for my openvpn.
So in short: I can connect via putty to port 8080 (reroutes to 22 on my NAS), not via port 80 or 443 (also reroutes to 22 on my NAS), connection is stuck on proxy local network (work).
http://www.nikhef.nl/~janjust/nikhef-proxy/, the thing is, only proxy socks 5 should be used.
Now this works over the proxy-tunnel, not when I go via putty only (directly to my dyndns-address), I get stuck at the proxy (port 80). It won't authenticate, however I've set the proxy-settings in putty.
Note: when I connect over port 8080 (they all redirect to port 22 = ssh on my NAS) it works fine, but I need port 8080 for my openvpn.
So in short: I can connect via putty to port 8080 (reroutes to 22 on my NAS), not via port 80 or 443 (also reroutes to 22 on my NAS), connection is stuck on proxy local network (work).