----- Original Message ----- From: Ed Greshko Sent: 05/02/14 01:28 AM To: Community support for Fedora users Subject: Re: iptable
On 05/02/14 07:24, Patrick Dupre wrote:
Thank,
Now it better, ACCEPT tcp -- anywhere anywhere tcp dpts:rfb:5903 ctstate NEW ACCEPT tcp -- anywhere anywhere tcp dpt:5901 ctstate NEW
but the port are still closed.
Ports will show as "closed" if there is no process listening on the port.
--
PORT STATE SERVICE 5900/tcp filtered vnc 5901/tcp filtered vnc-1 5902/tcp filtered vnc-2 5903/tcp filtered vnc-3
But then,
TigerVNC Viewer 64-bit v1.3.0 (20140319) Built on Mar 19 2014 at 17:09:18 Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC.
Fri May 2 01:34:25 2014 CConn: unable connect to socket: No route to host (113)
firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) Active: active (running) since Fri 2014-05-02 01:28:44 CEST; 8min ago Main PID: 25521 (firewalld) CGroup: /system.slice/firewalld.service └─25521 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid
May 02 01:28:44 Homere systemd[1]: Starting firewalld - dynamic firewall daemon... May 02 01:28:44 Homere systemd[1]: Started firewalld - dynamic firewall daemon.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
On 05/02/14 07:37, Patrick Dupre wrote:
PORT STATE SERVICE 5900/tcp filtered vnc 5901/tcp filtered vnc-1 5902/tcp filtered vnc-2 5903/tcp filtered vnc-3
But then,
TigerVNC Viewer 64-bit v1.3.0 (20140319) Built on Mar 19 2014 at 17:09:18 Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC.
Fri May 2 01:34:25 2014 CConn: unable connect to socket: No route to host (113)
Where is the system running vncviewer/nmap in relation to the system running vncserver?
The above shows "filtered" which means the port is being blocked/filtered by a firewall. Back in February, the configuration you were working with had a firewall/router between two systems over which you had not control.