Re: VNC question

From: "RoyB" <list@xxxxxxxx>
Date: Mon, 18 Sep 2006 15:31:57 +1000

sort of sounds like a TCP/IP problem rather than a VNC problem.
Can you ping the host that wll not connect?
Is the system that won't respond on the same subnet as the one that will
respond?

"news.la.sbcglobal.net" <cfk_remove_this_suffix@xxxxxxxxxxx> wrote in
message news:6MlPg.2397$vJ2.1189@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I have two *supposedly* the same computers. Both with a recent install of
Fedora Core 5.

Both are running vncserver, yet only one will do a vncviewer connect from
a
third computer.

In both cases, I did the following:

$ vncpasswd <set password>
$ vncviewer
$ ps -ef (Xvnc is running on both system).

What could cause one system to reply:

main: unable to connect to host: No route to host (113)

When running vncviewer?

Charles Krinke

References:
- VNC question
  - From: news.la.sbcglobal.net

Prev by Date: VNC question
Next by Date: old 486 DX2 comp and linux
Previous by thread: VNC question
Next by thread: old 486 DX2 comp and linux
Index(es):
- Date
- Thread

Relevant Pages

Re: f9 vino problem
... Check the network connectivity to the remote host ... Check again the vino preferences ... using vncviewer after enabling remote viewing with vino-preferences. ...
(Fedora)
f9 vino problem
... using vncviewer after enabling remote viewing with vino-preferences. ... client side I get a "unable to connect to host: ...
(Fedora)
VNC question
... I have two *supposedly* the same computers. ... Both are running vncserver, yet only one will do a vncviewer connect from a ... main: unable to connect to host: No route to host ...
(comp.os.linux)
Re: remote x terminal & suse 9.2
... I am using VNC right now to connect to KDE desktop. ... you run "vncserver" on the host and connect to it via vncviewer. ...
(alt.os.linux.suse)