![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
nmeyers at javalinux.net wrote: > On Mon, Nov 28, 2005 at 11:19:33AM -0500, John Abreau wrote: > >>I'm having a problem with VNC that I've been unable to figure out. I've >>got a number of remote machines connecting to my LAN over OpenVPN. I can >>ping them and ssh to them successfully, but when I try to connect with >>vncviewer, I get an error >> >> main: unable to connect to host: No route to host (113) >> >>The routes look fine, and if they really were broken then ssh wouldn't >>be working. What else could cause vnc to fail with that error? > > > A firewall blocking VNC, maybe? As an alternate route, you might try > tunnelling VNC over one of your ssh connections. > > Nathan I get the same problem when I try to connect to a remoet Windows machine, which I need to do for the users in the field that I support. I can't ssh into their XP laptops, so ssh tunnels won't solve the problem. -- John Abreau / Executive Director, Boston Linux & Unix ICQ 28611923 / AIM abreauj / JABBER jabr at jabber.org / YAHOO abreauj Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 -------------- next part -------------- A non-text attachment was scrubbed... Name: jabr.vcf Type: text/x-vcard Size: 175 bytes Desc: not available URL: <http://lists.blu.org/pipermail/discuss/attachments/20051128/d303d9d3/attachment.vcf>
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |