Hello
On 05/03/2014 02:10 AM, Patrick Dupre wrote:
Hello,
I am lost again!!!
I cannot open the port:
5900/tcp closed vnc
5901/tcp closed vnc-1
5902/tcp closed vnc-2
5903/tcp closed vnc-3
or
from localhost:
5900/tcp closed vnc
5901/tcp filtered vnc-1
5902/tcp closed vnc-2
5903/tcp closed vnc-3
while
Using firewall-config, I check vncserver bot permanent and runtime,
Do I need to do something else?
With "firewall-cmd --get-default-zone", you will get the default zone.
With "firewall-cmd --get-active-zones" you can see which zones are used
at the moment.
1) If you are using the default zone (if you have not assigned anther
zone for the connection)
firewall-config: Enable vnc-server for the highlighted zone in
runtime and permanent configuration.
With firewall-cmd: firewall-cmd --add-service=vnc-server &&
firewall-cmd --add-service=vnc-server --permanent
2) If you are using not the default zone:
firewall-config: Enable vnc-server for the used zone in runtime and
permanent configuration.
With firewall-cmd: firewall-cmd --zone=<zone>
--add-service=vnc-server && firewall-cmd --zone=<zone>
--add-service=vnc-server --permanent
This will then allow access to the ports for the vnc servers on ports
5900-5903.
You can also enable a port number directly in a zone:
With firewall-config, see the Ports tab on the right side with the
proper zone selected on the left side.
firewall-cmd [--zone=<zone>] --add-port=5901/tcp
and
firewall-cmd [--zone=<zone>] --add-port=5901/tcp --permanent
systemctl status vncserver
vncserver.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
systemctl start vncserver
Failed to issue method call: Unit vncserver.service failed to load: No such file or directory.
one the server, I did vncserver and open :1
Both machines are on the same network
vncviewer fails error 111 (unable to connect to socket)
remmina-vnc fails too (it ass the ssh password and sleep!)
It looks like to that I am not able to reopen this port, while it has works!!!!!
I am missing one point:
Both dbus.service and .socket are active without error
Sorry for my incompetence!
On 05/03/14 02:42, Patrick Dupre wrote:
Hello,
When I reun system-config-services, I get
ERROR:dbus.proxies:Introspect error on :1.980:/org/fedoraproject/Config/Services/ServiceHerders/XinetdServiceHerder: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
I checked:
systemctl status dbus.service
systemctl status dbus.socket
But there are active.
What is wrong?
Well, you checked them....they are "active" .... but there are errors...
systemctl status dbus.service
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Thu 2014-05-01 18:30:32 CEST; 6h ago
Main PID: 965 (dbus-daemon)
CGroup: /system.slice/dbus.service
├─ 965 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
├─4753 /usr/bin/python /usr/share/system-config-services/system-config-services-mechanism.py
└─4755 /usr/libexec/gam_server
May 02 01:24:44 Homere dbus-daemon[965]: follow_name_owner_changes=follow_name_owner_changes)
May 02 01:24:44 Homere dbus-daemon[965]: File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 248, in __init__
May 02 01:24:44 Homere dbus-daemon[965]: self._named_service = conn.activate_name_owner(bus_name)
May 02 01:24:44 Homere dbus-daemon[965]: File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 175, in activate_..._owner
May 02 01:24:44 Homere dbus-daemon[965]: return self.get_name_owner(bus_name)
May 02 01:24:44 Homere dbus-daemon[965]: File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 361, in get_name_owner
May 02 01:24:44 Homere dbus-daemon[965]: 's', (bus_name,), **keywords)
May 02 01:24:44 Homere dbus-daemon[965]: File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in ca...ocking
May 02 01:24:44 Homere dbus-daemon[965]: message, timeout)
May 02 01:24:44 Homere dbus-daemon[965]: DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply....roken.
Hint: Some lines were ellipsized, use -l to show in full.
You'll need to investigate that....
--
Do not condemn the judgment of another because it differs from your own. You may both be wrong. -- Dandemis
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
===========================================================================
Patrick DUPRÉ | | email: pdupre@xxxxxxx
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
===========================================================================
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
