Nmap 3.50 "?"

Folks,

I'm here for your help. I need to understand what the out come of
this command should be verses what it actually produced and what if
anything this is telling me. We are setting up a couple of simulated
corporate networks to be used as training nets for hacking into.
Don't worry nothing dangerous about this only used as an educational
tool for degree oriented folks to get some experience.

The cmd:
nmap -sW -PT -v -n -O --randomize_hosts -T5 10.0.10.0/24

got mostly this:
<snip>

Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-07-19
14:50 EDT
Host 10.0.30.34 appears to be up ... good.
Initiating Window Scan against 10.0.30.34 at 14:50
The Window Scan took 3 seconds to scan 1659 ports.
Warning: OS detection will be MUCH less reliable because we did not
find at least 1 open and 1 closed TCP port
Interesting ports on 10.0.30.34:
(The 1658 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
420/tcp filtered smpte
Device type: general purpose
Running: Apple Mac OS X 10.0.X|10.1.X, HP HP-UX 11.X, Novell Netware
3.X|4.X|5.X, OpenBSD 2.X, SCO UnixWare, Sun Solaris 2.X|7
OS details: Apple Mac OS X Server 1.0-1.0-1 (Rhapsody 5.3 - 5.4),
Apple Mac OS X 10.1 - 10.1.4, HP-UX B11.00 U 9000/839, Novell NetWare
3.12 - 5.00, OpenBSD 2.9-beta through release (X86), SCO UnixWare
7.0.0 or OpenServer 5.0.4-5.0.6, Sun Solaris 2.6 - 7 (SPARC)

Nmap run completed -- 1 IP address (1 host up) scanned in 7.095
seconds
<snip>

Thanks for your help in this matter.

I will check back frequently

Eutaw

"eutaw_uass" <eutaw_uass@yahoo.com> wrote in message
news:ed21f364.0407191125.817d06a@posting.google.co m

> We are setting up a couple of simulated
> corporate networks to be used as training nets for hacking into.

How are these networks "simulated"?

--
use hotmail for email replies

On 2004-07-19, eutaw_uass <eutaw_uass@yahoo.com> wrote:
> Folks,

> The cmd:
> nmap -sW -PT -v -n -O --randomize_hosts -T5 10.0.10.0/24
>
> got mostly this:
><snip>
>
> Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-07-19
> 14:50 EDT
> Host 10.0.30.34 appears to be up ... good.
> Initiating Window Scan against 10.0.30.34 at 14:50
> The Window Scan took 3 seconds to scan 1659 ports.
> Warning: OS detection will be MUCH less reliable because we did not
> find at least 1 open and 1 closed TCP port
> Interesting ports on 10.0.30.34:
> (The 1658 ports scanned but not shown below are in state: closed)


That's an odd scan type (check the man page), you sure a -sS or -sX
won't work better?


--
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++