Nmap Development mailing list archives
Possible WinPcap problems
From: AgentSmith15 <agentsmith15 () gmail com>
Date: Tue, 2 May 2006 00:13:49 -0500
When I do a nmap scan no matter the host it reports all the ports it scans as open. I don't have a firewall running or anything like that except a router but I doubt it would affect a Nmap scan. I am running Windows XP SP2 fully patched. I really don't know what the problem is but I suspect it is a problem with WinPcap. I have unistalled WinPcap and reinstalled it but it still gives me the same problems. Does anyone have some suggestions on how to fix this problem? Here is a example... nmap -v -F scanme.nmap.org Starting Nmap 4.03 ( http://www.insecure.org/nmap ) at 2006-05-02 00:10 Central Daylight Time DNS resolution of 1 IPs took 0.16s. Mode: Async [#: 2, OK: 1, NX: 0, DR: 0, SF: 0, TR: 1, CN: 1] Initiating SYN Stealth Scan against scanme.nmap.org (205.217.153.62) [1233 ports] at 00:10 Discovered open port 256/tcp on 205.217.153.62 Discovered open port 443/tcp on 205.217.153.62 Discovered open port 25/tcp on 205.217.153.62 Discovered open port 23/tcp on 205.217.153.62 Discovered open port 554/tcp on 205.217.153.62 Discovered open port 21/tcp on 205.217.153.62 Discovered open port 389/tcp on 205.217.153.62 Discovered open port 22/tcp on 205.217.153.62 Discovered open port 53/tcp on 205.217.153.62 Discovered open port 80/tcp on 205.217.153.62 Discovered open port 113/tcp on 205.217.153.62 Discovered open port 636/tcp on 205.217.153.62 Discovered open port 3389/tcp on 205.217.153.62 Discovered open port 86/tcp on 205.217.153.62 Discovered open port 258/tcp on 205.217.153.62 Discovered open port 754/tcp on 205.217.153.62 Discovered open port 262/tcp on 205.217.153.62 Discovered open port 7000/tcp on 205.217.153.62 Discovered open port 410/tcp on 205.217.153.62 Discovered open port 259/tcp on 205.217.153.62 Discovered open port 3000/tcp on 205.217.153.62 Discovered open port 156/tcp on 205.217.153.62 Discovered open port 504/tcp on 205.217.153.62 Discovered open port 451/tcp on 205.217.153.62 Discovered open port 1935/tcp on 205.217.153.62 Discovered open port 1388/tcp on 205.217.153.62 Discovered open port 5405/tcp on 205.217.153.62 Discovered open port 126/tcp on 205.217.153.62 Discovered open port 384/tcp on 205.217.153.62 Discovered open port 500/tcp on 205.217.153.62 Discovered open port 9152/tcp on 205.217.153.62 Discovered open port 5302/tcp on 205.217.153.62 Discovered open port 32775/tcp on 205.217.153.62 Discovered open port 769/tcp on 205.217.153.62 Discovered open port 2030/tcp on 205.217.153.62 Discovered open port 422/tcp on 205.217.153.62 Discovered open port 1525/tcp on 205.217.153.62 Discovered open port 753/tcp on 205.217.153.62 Discovered open port 62/tcp on 205.217.153.62 Discovered open port 465/tcp on 205.217.153.62 Discovered open port 1664/tcp on 205.217.153.62 Discovered open port 54/tcp on 205.217.153.62 ===I cut the rest out because it is very long list and woudn't help=== _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev
Current thread:
- Possible WinPcap problems AgentSmith15 (May 01)
- Re: Possible WinPcap problems Fyodor (May 02)
- Message not available
- Re: Possible WinPcap problems AgentSmith15 (May 02)
- Message not available
- Re: Possible WinPcap problems AgentSmith15 (May 02)
- Re: Possible WinPcap problems John Crichton (May 02)
- Re: Possible WinPcap problems 王敬 (May 02)
- Message not available
- Re: Possible WinPcap problems AgentSmith15 (May 04)
- Message not available
- Message not available
- Re: Possible WinPcap problems John Crichton (May 05)
- Re: Possible WinPcap problems Fyodor (May 02)
- Message not available
- Message not available
- Message not available
- Re: Possible WinPcap problems Jamie Gavahan (May 06)