0 x00: problems
to learn the use of the system nmap, run a simple command :
nmap -sC -p1- www.landgrey.cn
error: “dnet: Failed to open device eth1”
has not reported such a mistake before, I checked the data, found that it is likely to be related to winpcap drive .
0x01: resolution
and then downloaded
Win10Pcap 10.2.5002 Windows 32bit and 64bit Installer
after the installation, found the scanning process reported another error……
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.
is installing two winpcap incompatible?Uninstall the old version of winpcap, and then uninstall after what seems to remind, also did not pay attention to, it automatically ignored ~
and then run again, found that I did not install winpcap, it seems that this Win10Pcap not ah, and then uninstall Win10Pcap, there is a reminder when uninstall, this time just think of carefully look, found is not found when uninstall
C:\Windows\SysWOW64\Packet.dll
find Packet. DLL changed to Packet. DLL. Bak… Nima, also do not know is the ghost that anti-virus software makes, after restoring original name, hint did not find
again
C:\Windows\SysWOW64\wpcap.dll
a check found that the name is also changed to wpcap.dll. Bak. After the recovery, the normal uninstall.
then go to the official website to download the latest version of wincap
After the
installation, run the original command and find that the problem has been resolved.
nmap – sT 192.168.0.184
Stats: 0:00:03 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 4.85% done; ETC: 16:22 (0:00:39 remaining)
Nmap scan report for 192.168.0.184
Host is up (0.00071s latency).
Not shown: 991 filtered ports
PORT STATE SERVICE
25/tcp open smtp
110/tcp open pop3
119/tcp open nntp
143/tcp open imap
465/tcp open smtps
563/tcp open snews
587/tcp open submission
993/tcp open imaps
995/tcp open pop3s
0 x02: postscript
must not ignore some important tips to solve the problem in the process of solving the problem because of haste.
also do not know how DLL file into DLL. Bak file, fortunately did not give me delete ×_×
nmap -sC -p1- www.landgrey.cnhas not reported such a mistake before, I checked the data, found that it is likely to be related to winpcap drive .
Win10Pcap 10.2.5002 Windows 32bit and 64bit Installer
after the installation, found the scanning process reported another error……
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.and then run again, found that I did not install winpcap, it seems that this Win10Pcap not ah, and then uninstall Win10Pcap, there is a reminder when uninstall, this time just think of carefully look, found is not found when uninstall
C:\Windows\SysWOW64\Packet.dllC:\Windows\SysWOW64\wpcap.dllthen go to the official website to download the latest version of wincap
Stats: 0:00:03 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 4.85% done; ETC: 16:22 (0:00:39 remaining)
Nmap scan report for 192.168.0.184
Host is up (0.00071s latency).
Not shown: 991 filtered ports
PORT STATE SERVICE
25/tcp open smtp
110/tcp open pop3
119/tcp open nntp
143/tcp open imap
465/tcp open smtps
563/tcp open snews
587/tcp open submission
993/tcp open imaps
995/tcp open pop3s must not ignore some important tips to solve the problem in the process of solving the problem because of haste.
also do not know how DLL file into DLL. Bak file, fortunately did not give me delete ×_×