Same problem under Win XP pro - nmapwin 1.3.1 - winpcap 3.0
alpha 4 (and also winpcap 2.3).
Nmapwin simply doesn't work. The message is "Remote hosts do
not respond and could be down" or something like that.
My pc is directly connected to the internet (no proxy or firewall)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
does the nmap command line version show the same result?
Try to run the command line version with the same
parameters, which are visible on the bottom of the screen.
Is the pcap correctly loaded. In case nmapwin is running is
should show running in the status field. See attached
screenshot for more infos.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i had this problem - i was using a previous version of winpcap
and one day my nmapwin decided to crap out on me. i think
it was after a bsod. i uninstalled winpcap, rebooted, installed
winpcap 3 alpha 4, installed nmapwin again, and it works like
a charm. i've been playing with the ftp bounce scan on a
class c subnet which has caused me a bsod 2x so i've
restorted to running nmapwin on a 2k server in a vmware
machine so that when i get a bsod my whole system doesn't
go down. try reinstalling pcap. worked for me.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried to perform very simple operations, like pinging a remote
host or scanning my subnet - the message is always the same.
Nmapwin waits for a while (about 1 minute) and than comes out
with the message "Remote hosts do not respond and could be
down". I tried to install/uninstall winpcap several times. Also the
command line version shows the same result.
Nmapwin doesn't like my WinXP.
Any idea?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-11-30
Logged In: YES
user_id=659462
what do you have in win32/interfaces?
mine looks like this:
Available interfaces:
Name Raw send Raw recieve IP
loopback0 SOCK_RAW SOCK_RAW 127.0.0.1
eth0 SOCK_RAW winpcap 0.0.0.0
eth1 SOCK_RAW winpcap 0.0.0.0
eth2 SOCK_RAW winpcap 192.168.1.113
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The same on W2k and XP Professional... Is the NPF driver in
running state when nmapwin is running? Are you sure
nmapwin takes interface eth2? Otherwise set the interface in
the device field of the scan page. Is the host pingable,
otherwise set the 'no ping' on the discover page.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure nmap is running under and PPP interface. Please
send a mail to nmap-dev@insecure.org. This seems to be a
general nmap problem, not a nmapwin problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
can you please explain your error a bit more detailed. What
dod you try to do???
Logged In: NO
Same problem under Win XP pro - nmapwin 1.3.1 - winpcap 3.0
alpha 4 (and also winpcap 2.3).
Nmapwin simply doesn't work. The message is "Remote hosts do
not respond and could be down" or something like that.
My pc is directly connected to the internet (no proxy or firewall)
Logged In: YES
user_id=545266
does the nmap command line version show the same result?
Try to run the command line version with the same
parameters, which are visible on the bottom of the screen.
Is the pcap correctly loaded. In case nmapwin is running is
should show running in the status field. See attached
screenshot for more infos.
NPF driver screenshot
Logged In: NO
i had this problem - i was using a previous version of winpcap
and one day my nmapwin decided to crap out on me. i think
it was after a bsod. i uninstalled winpcap, rebooted, installed
winpcap 3 alpha 4, installed nmapwin again, and it works like
a charm. i've been playing with the ftp bounce scan on a
class c subnet which has caused me a bsod 2x so i've
restorted to running nmapwin on a 2k server in a vmware
machine so that when i get a bsod my whole system doesn't
go down. try reinstalling pcap. worked for me.
Logged In: YES
user_id=545266
Does this mean I can clode the issue?
Logged In: YES
user_id=545266
Does this mean I can clode the issue?
Logged In: YES
user_id=659462
it works fine on my xp sp1 system but i don't know if the
original poster ever solved his/her problem
Logged In: NO
I tried to perform very simple operations, like pinging a remote
host or scanning my subnet - the message is always the same.
Nmapwin waits for a while (about 1 minute) and than comes out
with the message "Remote hosts do not respond and could be
down". I tried to install/uninstall winpcap several times. Also the
command line version shows the same result.
Nmapwin doesn't like my WinXP.
Any idea?
Logged In: YES
user_id=659462
what do you have in win32/interfaces?
mine looks like this:
Available interfaces:
Name Raw send Raw recieve IP
loopback0 SOCK_RAW SOCK_RAW 127.0.0.1
eth0 SOCK_RAW winpcap 0.0.0.0
eth1 SOCK_RAW winpcap 0.0.0.0
eth2 SOCK_RAW winpcap 192.168.1.113
Logged In: YES
user_id=545266
The same on W2k and XP Professional... Is the NPF driver in
running state when nmapwin is running? Are you sure
nmapwin takes interface eth2? Otherwise set the interface in
the device field of the scan page. Is the host pingable,
otherwise set the 'no ping' on the discover page.
Logged In: NO
NPF driver is running (as I can see in Microsoft System
Information) but my win32/interfaces in nmapwin looks different:
Available interfaces:
Name Raw send Raw recieve IP
loopback0 SOCK_RAW SOCK_RAW 127.0.0.1
ppp0 SOCK_RAW SOCK_RAW x.x.x.x
There's no winpcap under ppp0/Raw recieve.
The device field of the scan page is set to "ppp0".
Logged In: YES
user_id=545266
I'm not sure nmap is running under and PPP interface. Please
send a mail to nmap-dev@insecure.org. This seems to be a
general nmap problem, not a nmapwin problem.