On 2/16/20 2:08 AM, Ed Greshko wrote:
On 2020-02-16 17:33, Samuel Sieb wrote:
On 2/16/20 1:20 AM, Patrick Dupre wrote:
nmap -v -n -Pn -p5900-5906 localhost PORT STATE SERVICE 5900/tcp closed vnc 5901/tcp open vnc-1 5902/tcp closed vnc-2 5903/tcp closed vnc-3 5904/tcp closed unknown 5905/tcp closed unknown 5906/tcp closed unknown
Now you have it running, so the next step is to figure out how to ask firewalld to allow connections to that port. I recommend the graphical interface. In any case be aware of the difference between the running config and the saved config.
He does seem to have it running on the "localhost". But the status of "closed" makes me suspicious That there is another device/firewall between the client and server. Notice his client is connecting to 193.52.235.60.
I say this since it has been my experience if a firewalld rule is blocking a connection it will show up as "filtered".
I've never seen someone firewall localhost, not sure if that's even possible. So any port that isn't open will be closed, not filtered.