I have a similar setup, but cannot get it to work either. VNC server is running on a SUSE93 system. router directs SSH-22 to an OpenBSD system. I'd like to tunnel from an outside system (Win98/WinXP) through the BSD system to the SUSE93 system. SSH from remote Win98 through router via PuTTY to OpenBSD works; VNC from a windows machine local to SUSE93 system works; but I can't seem to figure out the SSH tunneling/forwarding part. The webpage mentioned ny Sandeep refers to an old/obsolete version of PuTTY; perhaps this is part of the problem? Is there a more current page out there somewhere? The webpage is also not clear on which system one actually invokes vncviewer. Which is correct: 1) PuTTY into OpenBSD system, run vncviewer pointing to SUSE93 system 2) PuTTY into OpenBSD, ssh over to SUSE93; run vncviewer pointing to localhost. Frank At 12:15 PM 3/17/06, Sandeep Narasimha Murthy wrote:
Hi,
My Setup:
Home - Windows XP Office - 1 Solaris Box and 1 linux box
I connect to my office LAN via SSH (Solaris box). I need to reach the Linux box on my office network which has VNC server running on it.
My VNC Server in my linux box accepts requests on port 5901. I use PUTTY for SSH connection to the solaris box. I configured PUTTY according to the instructions in http://home.highertech.net/~john/Putty-Tunnel/putty-tunnel.html.
Next, launch VNC Viewer and try to do localhost:1, localhost:5901 etc.. but nothing happens..
Any suggestions ?
Thanks in adv,
Sg
-----Original Message----- From: vnc-tight-list-admin@lists.sourceforge.net [mailto:vnc-tight-list-admin@lists.sourceforge.net] On Behalf Of vnc-tight-list-request@lists.sourceforge.net Sent: sábado, 11 de Março de 2006 4:10 To: vnc-tight-list@lists.sourceforge.net Subject: VNC-Tight-list digest, Vol 1 #1648 - 7 msgs
Send VNC-Tight-list mailing list submissions to vnc-tight-list@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list or, via email, send a message with subject or body 'help' to vnc-tight-list-request@lists.sourceforge.net
You can reach the person managing the list at vnc-tight-list-admin@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific than "Re: Contents of VNC-Tight-list digest..."
Today's Topics:
1. RE: VNC-Tight-list digest, Vol 1 #1647 - 3 msgs (Sandeep Narasimha Murthy) 2. RE: VNC-Tight-list digest, Vol 1 #1647 - 3 msgs (John Aldrich) 3. Win 98 (nono) 4. RE: Win 98 (James Weatherall) 5. Connection options (David Russo) 6. RE: Connection options (John Aldrich) 7. RE: Connection options (Van Sickler, Jim)
--__--__--
Message: 1 Subject: RE: VNC-Tight-list digest, Vol 1 #1647 - 3 msgs Date: Fri, 10 Mar 2006 10:06:16 -0000 From: "Sandeep Narasimha Murthy"
To: Cc: Hi guys,
I am trying to do exactly what Ron is suggesting but having some = problems. The local machine is a WinXP machine and I connect to the = remote Server X using PUTTY.
How exactly do I configure Port forwarding in Putty ? and do I need to = run an additional X Server on my local machine ??
Thanks a lot,
Sandeep Murthy
-----Original Message----- From: vnc-tight-list-admin@lists.sourceforge.net = [mailto:vnc-tight-list-admin@lists.sourceforge.net] On Behalf Of = vnc-tight-list-request@lists.sourceforge.net Sent: sexta-feira, 10 de Mar=E7o de 2006 4:14 To: vnc-tight-list@lists.sourceforge.net Subject: VNC-Tight-list digest, Vol 1 #1647 - 3 msgs
Send VNC-Tight-list mailing list submissions to vnc-tight-list@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list or, via email, send a message with subject or body 'help' to vnc-tight-list-request@lists.sourceforge.net
You can reach the person managing the list at vnc-tight-list-admin@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific than "Re: Contents of VNC-Tight-list digest..."
Today's Topics:
1. Unix to Windows via VNC (Sandeep Narasimha Murthy) 2. Re: Unix to Windows via VNC (R) 3. Re: Unix to Windows via VNC (Ron Joffe)
-- __--__--
Message: 1 Subject: Unix to Windows via VNC Date: Thu, 9 Mar 2006 09:59:30 -0000 From: "Sandeep Narasimha Murthy"
To: This is a multi-part message in MIME format.
------_=3D_NextPart_001_01C64360.29425D13 Content-Type: text/plain; charset=3D"us-ascii" Content-Transfer-Encoding: quoted-printable
Hi,
=3D20
I am connecting to a remote Solaris server X via SSH and from server X have telnet and ftp access to all other machines on the network where the server X resides.
=3D20
My question is whether I can use tightVNC to connect to a windows machine from this Server X ?? i.e. launch a VNC session from the server ..
=3D20
Appreciate some suggestions,
=3D20
TIA,
=3D20
Sandeep
------_=3D_NextPart_001_01C64360.29425D13 Content-Type: text/html; charset=3D"us-ascii" Content-Transfer-Encoding: quoted-printable
xmlns:w=3D3D"urn:schemas-microsoft-com:office:word" =3D xmlns=3D3D"http://www.w3.org/TR/REC-html40">
Hi,
I am connecting to a remote Solaris server X = =3D via SSH and from server X have telnet and ftp access to all other machines on = =3D the network where the server X resides.
My question is whether I can use tightVNC to = =3D connect to a windows machine from this Server X ?? i.e. launch a VNC =3D session from the server ..
Appreciate some =3D suggestions,
TIA,
Sandeep
------_=3D_NextPart_001_01C64360.29425D13--
-- __--__--
Message: 2 Date: Thu, 9 Mar 2006 13:57:40 +0000 From: R
To: vnc-tight-list@lists.sourceforge.net Subject: Re: Unix to Windows via VNC On Thu, Mar 09, 2006 at 09:59:30AM -0000, Sandeep Narasimha Murthy = wrote:
Hi, =20 I am connecting to a remote Solaris server X via SSH and from server X have telnet and ftp access to all other machines on the network where the server X resides. =20 My question is whether I can use tightVNC to connect to a windows machine from this Server X ?? i.e. launch a VNC session from the = server ..
Since tightvnc is a graphical interface not a command line one, the simple answer is No, Having said that, if you can get the display that would be displayed on server X tunnlled back to your initial machine then yo could do this. It may be possible that you can do this by using the X11 Forwarding feature of SSH, and running a local X server, but this is a lot of hassle. Why not just run your tightvnc viewer on your local machine and tunnel that down to the other machines you want to acccess?
This is what I do here when I'm at work.
I SSH back to my home and login to a machine running OpenBSD which acts as my firewall etc. I port forward, using SSH tunneling, several local ports on my work PC to remote machines on the internal LAN of the remote OpenBSD machine.
I then run tightvnc locally, connect to localhost port 5901, and this gets forwarded to remote machine 192.168.1.x. If I connect to localhost port 5902 it gets forwarded to 192.168.1.y on my remote LAN etc etc. Works fine.
HTH
R. --=20 Today is the tomorrow you were worrying about yesterday. But tomorrow, today will be yesterday and you will be wondering why you were worrying about it in the first place.
-- __--__--
Message: 3 From: Ron Joffe
To: vnc-tight-list@lists.sourceforge.net Subject: Re: Unix to Windows via VNC Date: Thu, 9 Mar 2006 10:59:38 -0500 On Thursday 09 March 2006 04:59, Sandeep Narasimha Murthy wrote:
I am connecting to a remote Solaris server X via SSH and from server X have telnet and ftp access to all other machines on the network where the server X resides.
Sandeep,
Is this the scenario you have?
1. You want to connect to a vnc server residing on a windows machine = (port=3D =3D20 5900 of ip 1.2.3.4).=3D20
2. The windows machine is accessible to the solaris server (ip = 6.7.8.9).=3D20
3. You access the solaris server via ssh.
If so, a bit of port redirection in in order.
=3D46rom you local machine (I am assuming unix flavor, but it can be the = same=3D via=3D20 putty on windows):
ssh -C -g -L 5910:1.2.3.4:5900 login@6.7.8.9
This will set up an ssh tunnel from your local machine to the solaris = serve=3D r.=3D20 Then it will add a port tunnel between the windows vnc server (port 5900 = of=3D =3D20 1.2.3.4) and port 5910 of your local machine.
Next:
vncviewer localhost:10
Try that out and let me know.
Ron
-- __--__--
___________________________________________________________ TightVNC mailing list, VNC-Tight-list@lists.sourceforge.net To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
End of VNC-Tight-list Digest
--__--__--
Message: 2 From: John Aldrich
To: 'Sandeep Narasimha Murthy' Cc: "VNC List (E-mail)" Subject: RE: VNC-Tight-list digest, Vol 1 #1647 - 3 msgs Date: Fri, 10 Mar 2006 09:08:48 -0500 vnc-tight-list-admin@lists.sourceforge.net wrote on :
Hi guys,
I am trying to do exactly what Ron is suggesting but having some problems. The local machine is a WinXP machine and I connect to the remote Server X using PUTTY.
How exactly do I configure Port forwarding in Putty ? and do I need to run an additional X Server on my local machine ??
Sandeep: See http://faq.gotomyvnc.com/fom-serve/cache/30.html There's a couple step-by-step how-to documents listed there.
--__--__--
Message: 3 From: "nono"
To: Subject: Win 98 Date: Fri, 10 Mar 2006 12:43:33 -0300 This is a multi-part message in MIME format.
------=_NextPart_000_0033_01C64440.3E0DB800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
First, sorry but my english is too bad.
My question is...
I install the VNC on W98se and make that start in service mode.... When the PC Starts showme the configuration windows. Why?
Thanks !
------=_NextPart_000_0033_01C64440.3E0DB800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> First, sorry but my english is too=20 bad.
My question is...
I install the VNC on W98se and make = that=20 start in service mode.... When the PC Starts showme the = configuration=20 windows. Why?
Thanks !
------=_NextPart_000_0033_01C64440.3E0DB800--
--__--__--
Message: 4 From: "James Weatherall"
To: "'nono'" , Subject: RE: Win 98 Date: Fri, 10 Mar 2006 17:29:34 -0000 Organization: RealVNC Ltd. Nono,
You're seeing this behaviour because you're running a VNC 3.3-based server and haven't configured it for service-mode. You can either configure the service-mode settings, or you may find it simpler to upgrade to VNC Server 4 (http://www.realvnc.com/download.html).
Cheers,
Wez @ RealVNC Ltd.
-----Original Message----- From: vnc-tight-list-admin@lists.sourceforge.net [mailto:vnc-tight-list-admin@lists.sourceforge.net] On Behalf Of nono Sent: 10 March 2006 15:44 To: vnc-tight-list@lists.sourceforge.net Subject: Win 98
First, sorry but my english is too bad.
My question is...
I install the VNC on W98se and make that start in service mode.... When the PC Starts showme the configuration windows. Why?
Thanks !
--__--__--
Message: 5 Date: Fri, 10 Mar 2006 13:12:58 -0500 From: "David Russo"
To: Subject: Connection options --=__Part46631EBA.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit
How do I save changes to the Viewer connection options so that I don't have to set them each time?
How do I remove IP addresses from the drop down list in viewer connections?
Thanks.
--=__Part46631EBA.0__= Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Description: HTML
How do I save changes to the Viewer connection options so that I = don't have to set them each time?
How do I remove IP addresses from the drop down list in viewer = connections?
Thanks.
--=__Part46631EBA.0__=--
--__--__--
Message: 6 From: John Aldrich
To: 'David Russo' , vnc-tight-list@lists.sourceforge.net Subject: RE: Connection options Date: Fri, 10 Mar 2006 13:18:25 -0500 David Russo wrote on Friday, March 10, 2006 1:13 PM:
How do I save changes to the Viewer connection options so that I don't have to set them each time?
How do I remove IP addresses from the drop down list in viewer connections?
Thanks.
the first part is simple. Open a connection somewhere and then make the changes you want. Then hit your "F8" key and select "options" then click on the "load/save" tab and then in the "defaults" section, click "save" and that becomes your new default settings. Not sure how to clear the IP address from the drop-down box, unless you do it through Windows.
--__--__--
Message: 7 Date: Fri, 10 Mar 2006 16:59:36 -0500 From: "Van Sickler, Jim"
Subject: RE: Connection options To: "Vnc-T-l (E-mail)" -----Original Message----- From: Van Sickler, Jim Sent: Friday, March 10, 2006 11:37 AM To: 'John Aldrich' Subject: RE: Connection options
-----Original Message----- From: vnc-tight-list-admin@lists.sourceforge.net [mailto:vnc-tight-list-admin@lists.sourceforge.net] Sent: Friday, March 10, 2006 11:18 AM To: 'David Russo'; vnc-tight-list@lists.sourceforge.net Subject: RE: Connection options
David Russo wrote on Friday, March 10, 2006 1:13 PM:
How do I save changes to the Viewer connection options so that I don't have to set them each time?
How do I remove IP addresses from the drop down list in viewer connections?
Thanks.
the first part is simple. Open a connection somewhere and then make the changes you want. Then hit your "F8" key and select "options" then click on the "load/save" tab and then in the "defaults" section, click "save" and that becomes your new default settings. Not sure how to clear the IP address from the drop-down box, unless you do it through Windows.
To remove the previous sessions, open up the vncviewer, ("New TightVNC Connection" at the top) click on Options, then the Globals tab, and click on the "Clear the list of saved connections" button.
Jim
--__--__--
___________________________________________________________ TightVNC mailing list, VNC-Tight-list@lists.sourceforge.net To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
End of VNC-Tight-list Digest
------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmdk&kid0944&bid$1720&dat1642 ___________________________________________________________ TightVNC mailing list, VNC-Tight-list@lists.sourceforge.net To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
At 02:20 PM 3/23/06, Frank Bax wrote:
I have a similar setup, but cannot get it to work either. VNC server is running on a SUSE93 system. router directs SSH-22 to an OpenBSD system. I'd like to tunnel from an outside system (Win98/WinXP) through the BSD system to the SUSE93 system. SSH from remote Win98 through router via PuTTY to OpenBSD works; VNC from a windows machine local to SUSE93 system works; but I can't seem to figure out the SSH tunneling/forwarding part.
Sorry for the noise - I made two mistakes - posted to wrong list - and forgot to trim OP's message. OUCH. Frank
----- Original Message -----
From: "Frank Bax"
At 02:20 PM 3/23/06, Frank Bax wrote:
I have a similar setup, but cannot get it to work either. VNC server is running on a SUSE93 system. router directs SSH-22 to an OpenBSD system. I'd like to tunnel from an outside system (Win98/WinXP) through the BSD system to the SUSE93 system. SSH from remote Win98 through router via PuTTY to OpenBSD works; VNC from a windows machine local to SUSE93 system works; but I can't seem to figure out the SSH tunneling/forwarding part.
Sorry for the noise - I made two mistakes - posted to wrong list - and forgot to trim OP's message. OUCH.
Frank
<-- from old post of 7/19 or 7/20/05, I think this may help --> Mates, I hadn't played with tightVNC until now, opting to do all remote administration via ssh. After going through the learning process, I got to say "it's pretty cool." Now mind you, I still prefer ssh and the CLI from a speed standpoint, but if you want your whole desktop in front of you, VNC is the way to go. It's really not that bad on speed either. Now for what it is worth here is the lowdown: First, I wanted to get my local Suse 9.0 headless server's kde display up on my Win XP laptop. My server is named 'skyline'. Didn't seem like a tough thing to do. And it really wasn't. The steps were: (1) make sure you have vncserver installed; then start the server for the first time to set passwords and create initial config files (2) skyline:~> vncserver -geometry 1024x768 -depth 16 :1 (this creates the initial ~/.vnc/xstartup file and sets the password) kill the server and set the default display manager to kde or your preferred manager (3) vncserver -kill :1 (4) the default display manager is twm, so you need to edit ~/.vnc/xstartup and replace 'twm' with 'startkde'. Interestingly on mandriva, you get kde as default. now just restart the server (5) skyline:~> vncserver -geometry 1024x768 -depth 16 :1 next, go get a windows based vnc viewer (Realvnc or tightvnc will both work) (6) start realvnc, enter 'host:display' or 'host::port' in the box ( 'skyline:1' in my case), you will be prompted for the password, and you are done! If your not prompted for a password, revisit 1-5 above, try killing vncserver, and check with ps ax for any stray X process, kill them, restart vncserver again and try again. Now for the fun. At home I had basically a direct connection to the vnc connection. I wanted to try and tunnel this over ssh to the 3 linux boxes at work and get their displays up as well. At work, the router forwards ssh to 'nemesis' an old mdk 7.2 box (no X) from which I can then get to 'bonza' a mandriva 2005LE box and 'rankin-xp' a Suse 9.3 box. Getting there required a little thought and a few tricks from ssh, but is all works. With my basic set up at home, display 1 was already running, so port 5901 was in use in 'skyline'. To get around this problem ssh allows you to forward a remote port to a different local port - say 5902 which allowed a second vnc connection to display 2 on 'skyline' that was actually a local forward of display 1 on 'bonza' or 'rankin-xp' at work. The trick to get ssh to do this was to ssh into 'skyline' and then create a tunnel to 'nemesis' and tell 'nemesis' for forward port 5901 from either 'bonza' or 'rankin-xp' back to 'skyline' on port 5902 over ssh so it could be viewed as 'skyline:2' (display 2) on my XP laptop. After setting up vncserver on 'bonza' and 'rankin-xp' it actually worked. All it took was an ssh session via putty to skyline from windows. Then from skyline: skyline:~> ssh -g -L 5902:bonza:5901 nemesis and then in XP simply start another realvnc session and point it to skyline:2, and your there. For grins, and in theory, you can set another display at 5903 and have 3 active vnc connections and 3 linux desktops on your XP box at the same time. (Now that's a great use of windows.....) So for what it is worth, I thought I would share the information in hopes that it helps some other poor soul -- before I forgot what it was I did to get it working! Useful links were: http://www.uk.research.att.com/archive/vnc/sshvnc.html http://www.uk.research.att.com/archive/vnc/sshwin.html http://www.uk.research.att.com/archive/vnc/xvnc.html -- David C. Rankin, J.D., P.E. RANKIN LAW FIRM, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com --
david rankin wrote:
----- Original Message ----- From: "Frank Bax"
At 02:20 PM 3/23/06, Frank Bax wrote:
I have a similar setup, but cannot get it to work either. VNC server is running on a SUSE93 system. router directs SSH-22 to an OpenBSD system. I'd like to tunnel from an outside system (Win98/WinXP) through the BSD system to the SUSE93 system. SSH from remote Win98 through router via PuTTY to OpenBSD works; VNC from a windows machine local to SUSE93 system works; but I can't seem to figure out the SSH tunneling/forwarding part.
Sorry for the noise - I made two mistakes - posted to wrong list - and forgot to trim OP's message. OUCH.
Frank
<-- from old post of 7/19 or 7/20/05, I think this may help -->
Mates,
I hadn't played with tightVNC until now, opting to do all remote administration via ssh. After going through the learning process, I got to say "it's pretty cool." Now mind you, I still prefer ssh and the CLI from a speed standpoint, but if you want your whole desktop in front of you, VNC is the way to go. It's really not that bad on speed either.
Now for what it is worth here is the lowdown:
First, I wanted to get my local Suse 9.0 headless server's kde display up on my Win XP laptop. My server is named 'skyline'. Didn't seem like a tough thing to do. And it really wasn't. The steps were:
(1) make sure you have vncserver installed;
then start the server for the first time to set passwords and create initial config files
(2) skyline:~> vncserver -geometry 1024x768 -depth 16 :1 (this creates the initial ~/.vnc/xstartup file and sets the password)
kill the server and set the default display manager to kde or your preferred manager
(3) vncserver -kill :1 (4) the default display manager is twm, so you need to edit ~/.vnc/xstartup and replace 'twm' with 'startkde'. Interestingly on mandriva, you get kde as default.
now just restart the server
(5) skyline:~> vncserver -geometry 1024x768 -depth 16 :1
next, go get a windows based vnc viewer (Realvnc or tightvnc will both work)
(6) start realvnc, enter 'host:display' or 'host::port' in the box ( 'skyline:1' in my case), you will be prompted for the password, and you are done! If your not prompted for a password, revisit 1-5 above, try killing vncserver, and check with ps ax for any stray X process, kill them, restart vncserver again and try again.
Now for the fun. At home I had basically a direct connection to the vnc connection. I wanted to try and tunnel this over ssh to the 3 linux boxes at work and get their displays up as well. At work, the router forwards ssh to 'nemesis' an old mdk 7.2 box (no X) from which I can then get to 'bonza' a mandriva 2005LE box and 'rankin-xp' a Suse 9.3 box. Getting there required a little thought and a few tricks from ssh, but is all works.
With my basic set up at home, display 1 was already running, so port 5901 was in use in 'skyline'. To get around this problem ssh allows you to forward a remote port to a different local port - say 5902 which allowed a second vnc connection to display 2 on 'skyline' that was actually a local forward of display 1 on 'bonza' or 'rankin-xp' at work. The trick to get ssh to do this was to ssh into 'skyline' and then create a tunnel to 'nemesis' and tell 'nemesis' for forward port 5901 from either 'bonza' or 'rankin-xp' back to 'skyline' on port 5902 over ssh so it could be viewed as 'skyline:2' (display 2) on my XP laptop. After setting up vncserver on 'bonza' and 'rankin-xp' it actually worked. All it took was an ssh session via putty to skyline from windows. Then from skyline:
skyline:~> ssh -g -L 5902:bonza:5901 nemesis
and then in XP simply start another realvnc session and point it to skyline:2, and your there. For grins, and in theory, you can set another display at 5903 and have 3 active vnc connections and 3 linux desktops on your XP box at the same time. (Now that's a great use of windows.....)
So for what it is worth, I thought I would share the information in hopes that it helps some other poor soul -- before I forgot what it was I did to get it working!
Useful links were:
http://www.uk.research.att.com/archive/vnc/sshvnc.html http://www.uk.research.att.com/archive/vnc/sshwin.html http://www.uk.research.att.com/archive/vnc/xvnc.html
-- David C. Rankin, J.D., P.E. Thanks David. Very informative. I will safe keep this post as it might come handy sometime soon.
Prakash
At 10:47 AM 3/24/06, david rankin wrote:
With my basic set up at home, display 1 was already running, so port 5901 was in use in 'skyline'. To get around this problem ssh allows you to forward a remote port to a different local port - say 5902 which allowed a second vnc connection to display 2 on 'skyline' that was actually a local forward of display 1 on 'bonza' or 'rankin-xp' at work. The trick to get ssh to do this was to ssh into 'skyline' and then create a tunnel to 'nemesis' and tell 'nemesis' for forward port 5901 from either 'bonza' or 'rankin-xp' back to 'skyline' on port 5902 over ssh so it could be viewed as 'skyline:2' (display 2) on my XP laptop. After setting up vncserver on 'bonza' and 'rankin-xp' it actually worked. All it took was an ssh session via putty to skyline from windows. Then from skyline:
skyline:~> ssh -g -L 5902:bonza:5901 nemesis
There is no need to involve 'skyline' in this scenario (I learned this week). PuTTY itself can make the tunnel. Start PuTTY, then LOAD (not OPEN) your nemesis connection. Access the Connection-SSH-Tunnel dialog. source port: 5901 dest port: bonza:5901 Click "Add". source port: 5902 dest port: rankin-xp:5901 Click "Add". Under "Category", click "Session", then on right side, click "Save". Now whenever you want to access bonza or rankin-xp; you start PuTTY and connect to nemesis; then start vncviewer; specify "localhost:5901" for bonza or "localhost:5902" for rankin-xp. As in your scenario, you can make connections to both at the same time. http://sourceforge.net/mailarchive/forum.php?thread_id=10024787&forum_id=7154 Frank
----- Original Message -----
From: "Frank Bax"
There is no need to involve 'skyline' in this scenario (I learned this week). PuTTY itself can make the tunnel. Start PuTTY, then LOAD (not OPEN) your nemesis connection. Access the Connection-SSH-Tunnel dialog. source port: 5901 dest port: bonza:5901 Click "Add". source port: 5902 dest port: rankin-xp:5901 Click "Add". Under "Category", click "Session", then on right side, click "Save".
Now whenever you want to access bonza or rankin-xp; you start PuTTY and connect to nemesis; then start vncviewer; specify "localhost:5901" for bonza or "localhost:5902" for rankin-xp. As in your scenario, you can
make
connections to both at the same time.
http://sourceforge.net/mailarchive/forum.php?thread_id=10024787&forum_id=7154
Frank
Yes Frank I use PuTTY that way as well, but not knowing what the original requestor was using, I just sent the long version :-) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 www.rankinlawfirm.com -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.2/294 - Release Date: 3/27/06
participants (4)
-
david rankin
-
David Rankin
-
Frank Bax
-
Prakash Velayutham