Ti piace questa domanda nmap mostra IP sconosciuti da 192.168.2. * nella mia rete domestica che ha un intervallo IP di 192.168.1. *.
A differenza della domanda precedente, ogni singolo IP sembra essere completamente bloccato, incluso il blocco dei tentativi di ping. Per tutti gli IP (circa 70 tra 192.168.2.0 e 192.168.2.143), l'esecuzione di nmap -A -Pn risulta in:
PS C:\Users\Matthew> nmap -A -Pn 192.168.2.137
Starting Nmap 7.01 ( https://nmap.org ) at 2016-01-18 12:14 Central Standard Time
Nmap scan report for 192.168.2.137
Host is up (0.0021s latency).
All 1000 scanned ports on 192.168.2.137 are closed
Too many fingerprints match this host to give specific OS details
Network Distance: 1 hop
TRACEROUTE (using port 6788/tcp)
HOP RTT ADDRESS
1 16.00 ms 192.168.2.137
OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
In base al commento di AddisonWIlson di seguito ho eseguito quanto segue.
nmap -T4 -A -v -Pn
PS C:\Users\Matthew> nmap -T4 -A -v -Pn 192.168.2.137
Starting Nmap 7.01 ( https://nmap.org ) at 2016-01-18 13:18 Central Standard Time
NSE: Loaded 132 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 13:18
Completed NSE at 13:18, 0.00s elapsed
Initiating NSE at 13:18
Completed NSE at 13:18, 0.00s elapsed
Initiating Parallel DNS resolution of 1 host. at 13:18
Completed Parallel DNS resolution of 1 host. at 13:18, 0.01s elapsed
Initiating SYN Stealth Scan at 13:18
Scanning 192.168.2.137 [1000 ports]
SYN Stealth Scan Timing: About 29.55% done; ETC: 13:20 (0:01:14 remaining)
Increasing send delay for 192.168.2.137 from 0 to 5 due to 65 out of 162 dropped probes since last increase.
Completed SYN Stealth Scan at 13:19, 43.95s elapsed (1000 total ports)
Initiating Service scan at 13:19
Initiating OS detection (try #1) against 192.168.2.137
Initiating Traceroute at 13:19
Completed Traceroute at 13:19, 0.02s elapsed
Initiating Parallel DNS resolution of 1 host. at 13:19
Completed Parallel DNS resolution of 1 host. at 13:19, 5.52s elapsed
NSE: Script scanning 192.168.2.137.
Initiating NSE at 13:19
Completed NSE at 13:19, 0.00s elapsed
Initiating NSE at 13:19
Completed NSE at 13:19, 0.00s elapsed
Nmap scan report for 192.168.2.137
Host is up (0.000077s latency).
All 1000 scanned ports on 192.168.2.137 are closed
Too many fingerprints match this host to give specific OS details
Network Distance: 1 hop
TRACEROUTE (using port 4998/tcp)
HOP RTT ADDRESS
1 0.00 ms 192.168.2.137
NSE: Script Post-scanning.
Initiating NSE at 13:19
Completed NSE at 13:19, 0.00s elapsed
Initiating NSE at 13:19
Completed NSE at 13:19, 0.00s elapsed
Read data files from: C:\Program Files (x86)\Nmap
OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 54.65 seconds
Raw packets sent: 1828 (82.664KB) | Rcvd: 1010 (40.400KB)
Chiamato il mio ISP in base alla domanda collegata sopra, e hanno detto che non era la loro attrezzatura.
Sono nuovo per l'amministratore di rete, ma ho sviluppato software per 20 anni, quindi sono tecnicamente incline. Non sono sicuro se una delle seguenti cause potrebbe essere la causa.
- VMWare installato anni fa, ma mai realmente usato.
- MS HyperV con uno switch virtuale, ma tutto su quell'interruttore è 192.168.1. *
Qualcuno ha qualche idea?