It might just be me, but I have noticed in the past that the tunneled
VNC session isn't as responsive as the unsecure and untunneled session.
Obviously, secure is better than unsecure, but I was wondering if anyone
knew why the tunneled session is so much slower?
Randy
David McDowell wrote:
No one has mentioned using Putty on your WinXP workstation yet. Then
you can setup a tunnel for your VNC. I use this in 2 different ways.
- At work, ssh home, tunnel VNC into another box in my internal home network
- At home on my wifi segment (separated from my internal home network)
I ssh in from there and tunnel VNC for the same purpose
1. google putty and download putty.exe to your desktop (or wherever)
2. launch putty
3. enter in hostname or your home IP address, choose ssh and port 22
(presuming you are leaving ssh on port 22)
4. enter a saved sessions name and click save, the choice should
appear in the list
5. while those settings are still loaded, goto left menu, navigate to
Connection > SSH > Tunnels
(my presumption here is your VNC display is on display:1 or port 5901)
6. in Source port, enter 5901
7. in Destination, enter 192.168.1.5:5901 (fill in the internal IP of
your machine running VNC server)
8. click Add
9. go back and click the Session menu on the left menu
10. click Save
11. click Open (answer yes if first time to host like any ssh connection)
12. login
13. open vncviewer.exe on your WinXP desktop
14. in the Server field, enter localhost:1 (if your display was #1 on
port 5901)
15. enter your VNC password and enjoy VNC tunnelel through SSH
Now your only detectable session is from your WinXP box ssh'd to your
Debian box at home. There are tons of other things people in this
group tunnel through SSH, this just happens to be the one thing I do
and use all the time.
enjoy,
David McD
--
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
