On 03/04/2019 05.19, Patrick Shanahan wrote:
* Carlos E. R. <> [04-02-19 22:16]: [...]
So you are scanning your client, from your client. I don't think this gives any information.
Assuming that it is the server which blocks the connection, you have to scan the server from two client locations.
Or scan in both directions, client to server, then server to client. Using one working client and one faulty client.
server to workstation that fails (192.168.1.3 -> 192.168.1.10)
I translated all that to a calc sheet. Attached as csv (";" as separator). Don't complain, it is just 1K ;-) It seems to me that the fault is at the 192.168.1.3 firewall. From the 192.168.1.2 -> 192.168.1.3 case, some closed ports disappear when stopping the "3" firewall, and others appear as open. This is normal. I would look at the firewall definition files from any occurrence of 192.168.1.10, and /etc/hosts.deny (as Otto Rodusek i6 says). Another test is a traceroute: compare 192.168.1.2 -> 192.168.1.3 with 192.168.1.10 -> 192.168.1.3, with the server firewall down and up. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)