Having recently migrated to the 2.5 branch, I have two machines that have decided to rebel. I should mention that they've always been more or less like that, with the host package update either not launching at all, or I have to do it manually from the command prompt on the PC using `wapt-get update /upgrade`... And even then, it's not exactly a success.
The difference compared to version 2.4 is that I now have errors in the server logs for both of these machines:
Code: Select all
Feb 09 12:20:44 xxxx waptserver[7412]: 2024-02-09 12:20:44,799 [waptauth ] WARNING Failed auth for None from 192.168.x.1 path /add_host
Feb 09 12:20:46 xxxx waptserver[7412]: 2024-02-09 12:20:46,308 [waptauth ] WARNING Failed auth for None from 192.168.x.2 path /add_hostThese are PCs running Windows 7 with all updates still available. One is a physical PC, the other is a VirtualBox VM (accessible from the rest of the network and not configured with NAT).
---- Additional test from both PCs ----
Code: Select all
C:\Program Files (x86)\wapt>wapt-get update-status
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
2024-02-09 12:36:56,131 WARNING Host on the server is not known or not known under this FQDN name (known as pc1.MON.DOM). Trying to register the computer...
...---- Test from the wapt server ---
Code: Select all
nslookup pc1 --> renvoie bien l'ip
nslookup ip de pc --> renvoie bien le nom dns pc1.mon.dom
nsloolup pc1.mon.dom --> renvoie bien l'ip de pc1I have other PCs with similar specs and I don't have any problems. Do you have any other ideas?
Configuration:
-- Server: Debian 11.8, updated yesterday
-- PC: Windows 7 64-bit, up to date, firewall disabled.
Thanks in advance.
Philippe.
