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:
> Andrew Medico wrote:
> 
>> 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.
> 
> 
> % telnet 10.1.16.4 5902
> Trying 10.1.16.4...
> telnet: connect to address 10.1.16.4: No route to host
> telnet: Unable to connect to remote host: No route to host
> 
> 
> % telnet 10.1.16.4 22
> Trying 10.1.16.4...
> Connected to ebony.ovpn.zuken.com (10.1.16.4).
> Escape character is '^]'.
> SSH-2.0-OpenSSH_4.2
> 
> That's with iptables disabled on the remote host.

How about disabling iptables on the local host?  It could be (although
admittedly unlikely) that you have redirection rules on your local
machine for that particular destination port that are interfering.

--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