![]() |
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 |
Sounds like an iptables firewall blocking the VNC port. -derek Quoting John Abreau <jabr at blu.org>: > 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? > > VNC Viewer Free Edition 4.1.1 for X - built Aug 4 2005 06:43:41 > > > -- > 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 > -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord at MIT.EDU PGP key available
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |