IP Scanning

By the octets you list, I would assume you are talking about the netmask or subnet mask and not your actual IP.. These four sets of octets are used in network segmenting. They bassically tell what address are or are not part of your network segment. In the case you mention...no, a subnet of 222.222.222.0 will not mean you can scan for 222.222.222.0 till 255. A netmask of 255.255.255.0 would do this. As for the last part, I'm not sure what you mean or what you're asking.

If, in fact, you are talking about your IP itself, then the netmask would determine what's on your segment/subnet. The third octet being different on the "outside" is usually the case. The "outside" interface on the router is 223, where the "inside" address on your router is 222. This is quite common that the segmenting octet is one different (up or down) from the other segments adjacent to it.

[Message Edited]

ok. heres a simple example:
supose: my IP is 210.214.128.23
and i have an IP scanner.
and suppose ur IP is: 63.45.210.78

if i scan in my range: from 210.214.128.0 - 210.214.128.255, i can see the list of computers alive. but if i scan ur list:
63.45.210.0 - 63.45.210.255 or some other IP range, i cant see any computer alive!
why is this so?

my subnet mask is: 255.255.255.255

Probably because of a firewall protecting that network. If that's not it, then your netmask, default gateway, or a number of other things could be wrong. Personally, I've never seen your netmask used. That would me your IP is the only IP on that segment.

Word to the wise: I am confident I speak for all network admins when I say, you shouldn't scan what doesn't belong to you or, at the very least, what you're not responsible for. If your scanning something that's firewalled, your scan attempts are being watched...and logged.

I would suggest you check out the networking forums on HardOCP http://hardforum.com/forumdisplay.php?s=&forumid=19

[Message Edited]

I was just going to ask, why would you want to scan the ports of computers on a different network than yours? It's like walking in a parking lot and trying the door of every car to see if one is opened.  Doesn't appear like something very "nice".

Good analogy paxx...

hackers... hmmmmmm

oh boy...i dont like hacking...
anyway thanks for your advice i am learning all these

read up on bridges, routers, gateways, proxies, networks, subnets and demarc.

basically read up on network topologies and technologies, but don't stop there, read the rest of the Net+ manuals, takes the tests, pass them then do grunt work for a few years at least moving around from job to job because there isn't any vertical ladder anymore in the IT field unless you get with a smaller company that happens to accept the nurture and mature plan of building IT along with the business and keeping the teams together because the Business *is* the data....

Then pay the thousands of dollars on continuing education, or get it put into your perks package when hired..

Or, learn to crack but I wouldn't suggest being caught... Cracking is what people call Hacking today... You Crack a network, you Hack at code....
anyway...




oh, I would also be careful, you never know if you hit the wrong systems port just who you might tick off and exactly what they can do to your computer without you even knowing it is taking place until it is too late...

no I am not talking about one of these script kiddies who have less talent than a trained chimp...

And listen to IPlural.