Nmap Development mailing list archives
Re: FATAL Bad Memory Block.
From: Daniel Miller <bonsaiviking () gmail com>
Date: Mon, 30 Nov 2015 11:57:50 -0600
Mark, Thanks for this bug report. A quick web search shows this string in connection with WinPcap, though I can't find it in either their source or ours. This does not seem like an out-of-memory issue, and 2GB should be more than adequate. Can you post the output of this command, which will show the version of WinPcap linked along with extra debugging info? nmap -n -Pn -d2 -p 25 {IP} It would also be helpful to have information about whether Nmap seems to be accurate. The scan you showed has port 25 being filtered because of no response. Can you connect directly with a different program, or does nmap -sT show a different result? Dan On Wed, Nov 25, 2015 at 8:41 AM, Mark Huss <mark.huss () systemexperts com> wrote:
Since updating to v7 , whenever I run nmap on my laptop I get somewhere between ‘a couple of’ to ‘large streams’ of the error above, depending on the options on the command line. In between all the error messages nmap seems to be working ok and printing out the appropriate messages. I did a site search and found no mention of this particular error. Win7 x64 SP1 i7 2620M CPU 4G RAM(>2G available) Nmap 7 seems to work fine on my larger box (Win7 x64 SP1 16GB RAM). Is 2GB too little to run nmap in now? Examples: nmap -p 25 -Pn -v -v -v -Pn {IP} -- ( a couple of errors:) Starting Nmap 7.00 ( https://nmap.org ) at 2015-11-25 09:25 Eastern Standard Time Initiating Parallel DNS resolution of 1 host. at 09:25 Completed Parallel DNS resolution of 1 host. at 09:25, 0.02s elapsed DNS resolution of 1 IPs took 0.64s. Mode: Async [#: 5, OK: 1, NX: 0, DR: 0, SF:0, TR: 1, CN: 0] Initiating SYN Stealth Scan at 09:25 Scanning {host (IP)} [1 port] FATAL Bad Memory Block. FATAL Bad Memory Block. Completed SYN Stealth Scan at 09:25, 2.15s elapsed (1 total ports) Nmap scan report for {host (IP)} Host is up, received user-set. Scanned at 2015-11-25 09:25:42 Eastern Standard Time for 2s PORT STATE SERVICE REASON 25/tcp filtered smtp no-response Read data files from: C:\Program Files (x86)\Nmap Nmap done: 1 IP address (1 host up) scanned in 2.95 seconds Raw packets sent: 2 (88B) | Rcvd: 0 (0B) nmap -p 25 -T4 -A -v -v -v -Pn {IP} -- LOTS of errors: Starting Nmap 7.00 ( https://nmap.org ) at 2015-11-25 09:25 Eastern Standard Time […] Initiating OS detection (try #1) against { host (IP) } FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. Initiating Traceroute at 09:23 FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. FATAL Bad Memory Block. Completed Traceroute at 09:24, 9.14s elapsed […] Mark Huss | | mark.huss () systemexperts com SystemEXPERTS | Leadership in Security & Compliance _______________________________________________ Sent through the dev mailing list https://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
_______________________________________________ Sent through the dev mailing list https://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- FATAL Bad Memory Block. Mark Huss (Nov 30)
- Re: FATAL Bad Memory Block. Daniel Miller (Nov 30)
- RE: FATAL Bad Memory Block. Mark Huss (Nov 30)
- Re: FATAL Bad Memory Block. Daniel Miller (Nov 30)