BIOS UUID bug

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
infotc
Messages: 13
Registered: July 11, 2017 - 11:24

September 26, 2017 - 10:00

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... :o
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

September 26, 2017 - 4:53 PM

Hmm, that looks like an address conflict to me.

Or perhaps the positions have been changed and are appearing twice in the console?
High
infotc
Messages: 13
Registered: July 11, 2017 - 11:24

September 27, 2017 - 2:11 PM

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.
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

October 3, 2017 - 10:09 PM

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?
High
Locked

Return to "WAPT Server"


  • To go further with WAPT