On 03/04/2019 03.24, Patrick Shanahan wrote:
* Lew Wolfgang <> [04-02-19 19:22]:
from server/192.168.1.3
# nmap -F 192.168.1.3
So you are scanning your server, from your server.
Starting Nmap 6.47 ( http://nmap.org ) at 2019-04-02 21:09 EDT Nmap scan report for wahoo.wahoo.no-ip.org (192.168.1.3)
Something weird in the DNS. It is reporting an internet name for an internal IP.
Host is up (0.000015s latency). Not shown: 92 closed ports PORT STATE SERVICE 22/tcp open ssh 25/tcp open smtp 80/tcp open http 111/tcp open rpcbind 139/tcp open netbios-ssn 445/tcp open microsoft-ds 2049/tcp open nfs 3306/tcp open mysql
Nmap done: 1 IP address (1 host up) scanned in 1.55 seconds
# systemctl stop SuSEfirewall2
wahoo: ~ # nmap -F 192.168.1.3
Starting Nmap 6.47 ( http://nmap.org ) at 2019-04-02 21:09 EDT Nmap scan report for wahoo.wahoo.no-ip.org (192.168.1.3) Host is up (0.000020s latency). Not shown: 92 closed ports PORT STATE SERVICE 22/tcp open ssh 25/tcp open smtp 80/tcp open http 111/tcp open rpcbind 139/tcp open netbios-ssn 445/tcp open microsoft-ds 2049/tcp open nfs 3306/tcp open mysql
Nmap done: 1 IP address (1 host up) scanned in 1.55 seconds
# systemctl start SuSEfirewall2
from workstation/192.168.1.10
# nmap -F 192.168.1.10
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. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)