ErnestGoesToGitmo

Yeah, it takes a while to get the first batch of results. We don't have enough devices to warrant those results. It's possible we have something misconfigured, and finding what could be a real pain. I used the proper command, though, didn't I?

Running a fresh scan to get a recent result to trace to, but when I tried pinging some of these results from a command prompt, they would not respond. Another piece of pertinent info... ;)

nmap -sn 10.71.0.0/16

Yeah, sorry, pertinent info... I'm a Net Tech for a college, and I'm trying to find an empty range. My reference to home routers was a professor or someone bring in a linksys or such, plugging into the uplink port and throwing out his own IPs inadvertently. If I scan 172.16.0.0/16, it should come up empty, or maybe just a few oddballs, but instead I get upwards of 3000 hosts as up, when we don't distribute anything in that range currently. Baffling to me. I figure I'm doing something wrong in NMAP, or we could have some weird, out of the way setting on some out of the way switch or something that is making the whole thing go stupid. I appreciate your reply.

I've been trying to find an empty range for a Sysadmin to use, but every range I scan comes up with IPs that should not be responding. I scanned a class B, and I'm not sure if it even finished, but it showed 3000 hosts as up, when all there should be is the oddball home router on a 172, if that. I tried scanning X.X.0.0/16 (not literal X) using nmap -sn. Anybody have any idea of something I'm doing wrong (related to this issue :P)? Thanks!