• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How do I return a machine name from a ping or tracert in Windows?

Or should I post this in Operating Systems?

~~edit for more info.

My firewall is returning all these error messages of dropped Broadcast Packets from inside the Lan. It seems all the machines occasionally want to talk to machine 10.0.0.255 and those packets get dropped...
 


<< 10.0.0.255 >>



How many systems are on this network? Are you sure that isn't a broadcast address?

Russ, NCNE
 
Are you using the 10.x.x.x private ip segment on your lan? If so, that sounds like the bcast like Russ said...
 
Apparently, although I have my NCNE also, you must be NCNE+ 'cause you lost me. 😀

What do you mena broadcast address?

There are definately not 255 machines on the network and it does not show up in the DHCP tables however it is a valid address to ping and does reply.
 


<< Apparently, although I have my NCNE also, you must be NCNE+ 'cause you lost me. 😀

>>


LOL
 
If you're using a class C subnet (255.255.255.0), that address is the broadcast address for the subnet.

If you're not using a class C subnet, then this is a valid IP address on the private network. However, you're asking for a reverse lookup, which isn't always possible.

If the IP address is question is a machine running NetBIOS over TCPIP, try the following command from your machine:

nbtstat -A 10.0.0.255

This should return the name table of the machine with that IP address. Note you need a capital "A" as the parameter.

-Noggin
 
djheater,

Broadcast is an address that forwards traffic. I guess the easiest analogy would be "traffic cop".



<< If you're using a class C subnet (255.255.255.0), that address is the broadcast address for the subnet. >>



NogginBoink,

Obviously, he's on a Class A network. A 10.x.x.x address is not going to be a broadcast address for a Class C subnet.

Russ, NCNE

 


<< djheater,

Broadcast is an address that forwards traffic. I guess the easiest analogy would be "traffic cop".

>>



That being the case any reason why the hardware Firewall (a sonicwall device) would be showing in it's log that these packets are being dropped? Is it just network noise?
 
djheater,

That I don't know, unless it's programmed to filter packets based on whether or not they contain a specific header - IE: This packet really has information and should go out to the workstations, or this one is just a ping and is wasting my time.

Did you run nbtstat -A on the address to see what comes back? If there really is a machine at that address?

Russ, NCNE
 
That means there is, indeed, no machine at that address and that you are definitely on a Class A subnet (your address 10.0.0.129).

Russ, NCNE

 
Thanks for all your help everybody.

So what I'm looking at is an address called the Broadcast address that serves packets back and forth aroung the network. The Firewall, having restrictions as to what traffic is allowed, drops packets that have no purpose it understands. I would therefore have to allow all internal traffic in order to stop the log from filling with dropped packet errors.

Right?
 
djheater,

Not being familar with that firewall, I'll just say, okay that sounds right. I can tell you, though, that 10.0.0.255 is definitely the broadcast address. Just verified the range 10.0.0.1 to 10.0.0.129 and it does come up with that address for broadcast.

Russ, NCNE
 
> Obviously, he's on a Class A network. A 10.x.x.x address is not going to be a broadcast address for a Class C subnet.

Russ, this I don't understand. Being nonroutable, it's very common to setup the 10.x.x.x networks into individual class c's. That would indeed by the broadcast address in that case.

Confused,
Bill
 


<< it's very common to setup the 10.x.x.x networks into individual class c's. >>



How do you divide Class A network addresses (1-127) in to class C network addresses (192-223)?

Russ, NCNE
 
> How do you divide Class A network addresses (1-127) in to class C network addresses (192-223)?

Your using a strict definition of the network classes, (which is generally appropriate, but falls down a bit when dealing with nonrouteable addresses). My point was that subdividing the 10 network into individual subnets of 254 hosts it quiet common. NogginBoink refered to the netmask used in such a scenario as a 'class c' mask. Most IT people would know exactly what he was talking about. And, he remains correct that a 255.255.255.0 mask applied to the 10.0.0.0 range would give a subnet of 254 hosts with the 10.0.0.255 address being the broadcast address.

I can't tell from your answers if you weren't clear on the 10.0.0.x network usage, or just questioning NogginBoinks (and now my) use of the term 'Class C'.

Bill
 
bsobel,

Dividing a Class A subnet in to multiple hosts does not make it a Class C subnet. In any event, I probably should have assumed "mask" when he said "If you're using a class C subnet (255.255.255.0)". In that case, it is correct.

Russ, NCNE
 
Back
Top