> On Wed, Jun 4, 2008 at 5:14 AM, Nicolae Ghimbovschi <xfreebird@xxxxxxxxx>
> wrote:
>> 2008/6/4 David L <idht4n@xxxxxxxxx>:
>> I'm unable to get a vncviewer to connect to my f9 gnome desktop
>> using vncviewer after enabling remote viewing with vino-preferences.
>> I think I'm doing the same thing that worked in f8, but now on the
>> client side I get a "unable to connect to host: no route to host"
>> error. Any ideas?On Wed, Jun 4, 2008 at 8:33 AM, Nicolae Ghimbovschi <xfreebird@xxxxxxxxx> wrote:
Let your machine be A and the remote machine be B.
Most likely you have firewall running on the machine A and is blocking
port 5901.
Test it by disabling firewall on machine A.
If that works then open port 5901.Both ends have disabled firewalls:
more /etc/sysconfig/system-config-firewall
# Configuration file for system-config-firewall
--disabled
--port=22:tcp
OK... so it appears that having the firewall disabled is not
behaving the same as in f8 and before. It seems that I
have to enable specific ports even though the firewall
is disabled. In f9, vino seems to work only if port 5900
is enabled in the firewall configuration irrespective of
whether the firewall is enabled. This firewall configuration
works:
--disabled
--port=22:tcp
--port=5900:tcp
Is this a bug in the firewall? It seems to me that if the
firewall is disabled, the firewall ports that are allowed
shouldn't matter.
Thanks,
David
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
