Re: valid ip address for printer

Wait.
that an address ends with 255 doesnt mean anything. What you must check is
the subnetting. In this case you say you use 255.255.255 = /24 that means
that your IP range is 192.168.129.0 to 192.168.129.255 the first and the
last are reserved. That means that assigning .255 to a printer is wrong due
to it being the broadcast address.
But if you had, for example, a /16 subnet you would have several .255 in
your network (not the last one of course, but those in the middle)

Have a nice subnetting calculator:
http://www.aprendaredes.com/cgi-bin/ipcalc/ipcalc_cgi?host=192.168.129.0&mask1=24&mask2=

Best Regards,

Roberto


On Sat, Jul 19, 2014 at 1:31 PM, John Smith <smith5646@xxxxxxxxx> wrote:

I'm surprised that you can assign address .255. I was never able to
but never thought about why. I just googled "ping .255" and got some
very interesting information that I did not know. Apparently .255 is
a "broadcast" address that is similar to saying "Is anybody out
there?" You apparently are getting a response from "everyone" on the
subnet.

Very interesting reading if you do the same google search.

Thanks for teaching me something today. :)

John

On Jul 19, 2014, at 11:03, Jim Franz <franz9000@xxxxxxxxx> wrote:

We have a network printer (ipds) assigned address 192.168.127.255 (by our
network staff)
When I ping it from system I get unusual response message. It appears to
ping all the 192.168.127.x addresses.
Pardon my ignorance, is ".255" reservered or special?
btw, subnet on ethernet line is 255.255.255.0
Also, we recently moved operation, and new network not "settled".
Selection or command
===> ping '192.168.127.255'

PING reply 1 from 192.168.127.4 took 0 ms. 256 bytes. TTL 225.
PING reply 1 from 192.168.127.4 took 0 ms. 256 bytes. TTL 225.

(Duplicate)

PING reply 1 from 192.168.127.2 took 0 ms. 256 bytes. TTL 255.

(Duplicate)

PING reply 1 from 192.168.127.209 took 0 ms. 256 bytes. TTL 255.
Duplicate)
PING reply 1 from 192.168.127.247 took 0 ms. 256 bytes. TTL 255.
(Duplicate)
PING reply 1 from 192.168.127.215 took 0 ms. 256 bytes. TTL 254.
(Duplicate)
PING reply 1 from 192.168.127.37 took 0 ms. 256 bytes. TTL 255.
(Duplicate)
PING reply 1 from 192.168.127.218 took 1 ms. 256 bytes. TTL 255.
(Duplicate)
PING reply 1 from 192.168.127.25 took 1 ms. 256 bytes. TTL 255.
(Duplicate)
PING reply 1 from 192.168.127.216 took 1 ms. 256 bytes. TTL 255.
(Duplicate)
PING reply 1 from 192.168.127.29 took 1 ms. 256 bytes. TTL 255.
(Duplicate)
PING reply 1 from 192.168.127.12 took 1 ms. 256 bytes. TTL 255.
<more>

Jim
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.