Tranquil IT Forum

Hello,
just so you know, I encountered this problem in two computer labs where the workstations hadn't been turned on for a few weeks.
Wake-on-LAN works fine for turning the workstations back on, but about a quarter of them report an inability to connect due to an incorrect UUID.
Restarting the affected workstations makes some accessible again, while others remain unavailable.
However, as soon as I launch Waptray on the remaining problematic workstations, the connection is immediate and there are no further issues.
There has been no UUID regeneration, nor are there any duplicate UUIDs on the network.
If one of the developers could explain this phenomenon...

Hmm, that looks like an address conflict to me.

Or perhaps the positions have been changed and are appearing twice in the console?

Hello,
to clarify, the workstations already had a DHCP lease, and there were no duplicate addresses.
The workstations did not appear twice in the console.
However, the building's network cabling is old and contains a mix of high-voltage and low-voltage wiring.

Can you search using the IP address of the problematic machine in the console?

If not, can you run `wapt-get register` on the problematic machine?