Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Network routing mystery; ssh works, vncviewer doesnt



On 11/28/05, John Abreau <jabr at blu.org> 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

What happens when you try "telnet <host> 5900" (for display numbers
other than 0, add the display number to 5900)? If that gives you "no
route to host" too, you've got a network problem and not an
application problem.

--
Andrew Medico <a.medico at gmail.com>




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org