I have a specific IP address (xxx.xxx.xxx.120) that has been causing problems whenever the DHCP server tries to assign the IP to a device.
I have putz around with a few attempts at finding the device causing the issues, here is where I'm at...
I have a laptop that was assigned the .120 address by DHCP. Windows immediately complains about a conflicting IP. When I try
nbtstat -a 192.168.1.120
only the laptop shows up. When I disable the laptop's radio, and try nbtstat again, nothing shows up.
I cannot ping the IP when the laptop is not assigned, but that could mean the device creating the problem is simply firewalled/blocked, so I'm not sure that helps.
Using arp -a (regardless of whether or not the laptop is assigned the .120 address, the IP in question is listed, but the MAC address does not match the MAC of the laptop's hardware.
To further complicate things, when I look up the MAC address, it comes back as registered to DELL, which is the manufacturer of the laptop...
Another odd piece to this is when the laptop is connected, and receives the .120 IP, pinging the .120 address shows a TTL of 64 or 128, but it's seemingly random from one ping attempt to the next. Sometimes just the first hop is 64, sometimes all hops are 64. Wouldn't a Windows client always return a TTL of 128?
Is there anyway to track down this MAC address?
Any other ideas on how to troubleshoot this?
Edit: This happens regardless of the device that is assigned the .120 address, so it's not limited to this particular laptop.