Re: rare animal: Nmap on Windows 2003 x64

["Gianluca Varenni" <gianluca.varenni () gmail com>]

Dirk,

can you please try windump and see if it works on the x64 machine?

For example, try to list the adapters with "windump -D" (capital D).

Then, try to list the adapters with the attached app, taken from the winpcap 
developer's pack (rename the .zap file to .zip). It should list the adapters 
with their IP addresses, check that they are correct.

Have a nice day
GV


----- Original Message ----- 
From: "Spam" <spam () drwetter org>
To: "Gianluca Varenni" <gianluca.varenni () gmail com>
Cc: <nmap-dev () insecure org>
Sent: Tuesday, April 11, 2006 3:45 AM
Subject: Re: rare animal: Nmap on Windows 2003 x64


> Hi Gianluca,
>
> both :-) Of course the rules of the firewall(s) had to be tested from
> the inside as well and also for that nmap is a way better choice than
> using what I ended up to use. Sorry if I wasn't so clear about that.
>
> I didn't and still don't know whether it is a Winpcap issue or one from
> nmap, wish I could provide more input. As I said I used the regular 32
> bit binary of nmap (4.01) plus WinPcap 3.2a1 and encountered this problem.
>
> Has nobody a comparable config?
>
>
> Cheers,
> Dirk
>
>
>
> Gianluca Varenni wrote:
> > Spam, Max,
> >
> > it's not clear to me if you want to use nmap *on* a x64 machine, or as 
> > the
> > target of a scan.
> > If it's the former, nmap (32bit executable) should work well on a x64
> > machine, provided that you install WinPcap 3.2a1.
> >
> > If it doesn't work, it would be important for us (WinPcap Team) to
> > understand if it's a WinPcap issue or a nmap one.
> >
> > Have a nice day
> > Gianluca Varenni
> > WinPcap Team
> >
> > ----- Original Message ----- 
> > From: "Max" <Reply.to.list () acme com>
> > Cc: <nmap-dev () insecure org>
> > Sent: Wednesday, April 05, 2006 11:45 PM
> > Subject: Re: rare animal: Nmap on Windows 2003 x64
> >
> >
> > > If you need *to* pentest a 64bit machine, you should run your scan
> > > *from* another machine. Use a 32bit machine *for* the test and you
> > > should have no problems with nmap.
>
> M@x, I am really tempted to reply to this with the same attitude, but I
> guess it's better to spare myself a comment ;-)
>
>
> > > M@x
> > >
> > >
> > > Spam wrote:
> > > > Hi there,
> > > >
> > > > a couple of days ago I needed to pentest a 64Bit Windows 2003 box.
> > > > I know that the question might sound silly since because I don't really
> > > > have the output (neither do I have access to the system) anymore, but
> > > > does nmap run at all on this machine?
> > > >
> > > > Specifically (I was using the winpcap 3.2 alpha1, 3.1 didn't fly).
> > > > upon using nmap it kept on telling me that it couldn't found the 
> > > > default
> > > > interface. nmap --iflist showed the same complaint. (Needless
> > > > to say that there was one). The system was with its patches pretty up 
> > > > to
> > > > date, I didn't tweak the registry (like AppCompatFlags), a comparable
> > > > 32Bit system worked.
> > > >
> > > > Sorry if this was discussed before but I couldn't find anything.
> > > >
> > > >
> > > > Cheers,
> > > >
> > > > Dirk
> > > >
> > > >
> > > > PS: I ended up writing a (cough) BAT script using netcat. :-/
> > >
> > > _______________________________________________
> > > Sent through the nmap-dev mailing list
> > > http://cgi.insecure.org/mailman/listinfo/nmap-dev
> >
> >
> >
> > _______________________________________________
> > Sent through the nmap-dev mailing list
> > http://cgi.insecure.org/mailman/listinfo/nmap-dev
>
>
>
>
> --
> Dirk Wetter, Dr. Wetter IT-Consulting
> IT-Security + Open Source                        http://drwetter.org
> Key fingerprint = 2AD6 BE0F 9863 C82D 21B3  64E5 C967 34D8 11B7 C62F


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev