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



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?
> 
> VNC Viewer Free Edition 4.1.1 for X - built Aug  4 2005 06:43:41

Are you using the same level of DNS qualification for both the VNC
connection and ping commands (ie foo vs. foo.mycompany.com)?  If somehow
the DNS for VNC resolves to a different IP than the ping command gets,
then potentially your connection is not going through the VPN like it
should.

Have you tried using raw IP addrs for both the ping and VNC commands?

--Matt




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