Re: Why?

[Daniel Miller <bonsaiviking () gmail com>]

Ken,

Thanks for reporting this to us. Windows support is a big concern for Nmap,
so we are glad to hear that it works well on Windows 10. Regarding the
problems in Windows 8.1, please provide us with some further information so
we can help:

1. Please use the command-line version of Nmap for these diagnostics. If
you installed Nmap with "Register Nmap path" option, you can do this from
any command window (cmd.exe or powershell). Otherwise, you'll have to
change directory into the Nmap installation directory (e.g. cd "\Program
Files (x86)\Nmap\")

2. What is the version of Nmap that you have installed? There is a
stability fix for Windows in 6.49BETA5 that may address your problem, so
it's important that you use the latest version. Show output of: nmap
--version

3. Run your command with the -d option and provide the output. E.g. nmap -d
192.168.1.*

4. Describe what you expect to happen and how it is different from what
actually happened.

Thanks for being an Nmap user!

Dan

On Sat, Sep 26, 2015 at 9:37 AM, Ken Wood <kentek3141 () hotmail com> wrote:

> Guys,
>
> I’m not a programmer or big time network analyst, just a fairly OK
> computer user.
>
>
>
> I’ve been running the last 2 versions of the Beta Zenmap 6.49 on two PCs:
> Win 8.1 Enterprise and a Trial version of Win 10.
>
>
>
> One of my basic tests has always been to see what is on my network. To do
> this I run 192.168.1.* as a regular scan.  It never works on the Win 8.1
> but always works on Windows 10.  All I get on the Win 8.1 is a working
> window with no data.
>
> Pre-Beta 6.49 worked everywhere.
>
>
>
> Regards,
>
>
>
> *Ken Wood*
>
> *Camarillo, CA*
>
>
>
> _______________________________________________
> 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/