Originally posted by fE¨·.·¨Er
As you already know, the IPv4 ranges from 0.0.0.0 to 255.255.255.255 which is the hexadecimal representation of FF.FF.FF.FF
It means that you have * 00 00 00 00(hex) possibilities that is equivalent to the decimal number 4 2*4 *67 2*6. (you can double check by using the windows calculator converting Hex to Dec)

When you (correctly) scan one single IP you need to scan all ports from 0 to 655*5 (which is 655*6 total ports!)

Now, let us assume that with your current connection speed and under normal Internet network congestion conditions, you can scan * single IP within * minute (all ports from 0 to 655*5)

You will need 4 2*4 *67 2*6 minutes to scan all IPs (although some Internal IPs are useless to scan (*0.0.x.x / **2.*68.x.x).
Anyways, 4 2*4 *67 2*6 minutes = 7* 582 788 hours =
2 *82 6*6 days = 8 *7* years

As you can see, it is not * month , it is rather 8 *7* years that you need to run a (correct) scan for IPs ranging from 0.0.0.0 to 255.255.255.255.

till then....
[url=http://fever.resourcez.com]fE¨·.·¨Er[/url]
Oh boy, I see someone who is not a lamer. At last! You do actually know a few things about IP addressing (private networks and such).
Still I have further clarifications:
*. No need to scan addresses higher than 224.0.0.0 - for obvious reasons.
2. There are a lot of unused public addresses (networks not used to the limit, you know)
*. Some devices may just happen to be offline when you deside to try them.