Hello,
Since the 2.1 update, I've noticed that some machines suddenly switch from "Reachable" status ("OK") to "DISCONNECTED" even though they are online (ping is successful).
I've identified the cause: it happens when a laptop user takes their computer out of its dock to go to a meeting (for example), and therefore switches from one IP address to another (because they switch from the Ethernet card to the Wi-Fi card). I can see both IP addresses in the "IP Addresses" column, but it seems that only the first one is recognized by the WAPT console as reachable or not.
Is this a bug in version 2.1 of the console, or am I the only one experiencing this problem?
Thanks.
[BUG 2.1 ??] Machines seen as DISCONNECTED since update 2.1
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
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
-
Christophe0110
- Messages: 53
- Registration: June 11, 2019 - 12:04
-
Christophe0110
- Messages: 53
- Registration: June 11, 2019 - 12:04
-
Christophe0110
- Messages: 53
- Registration: June 11, 2019 - 12:04
Do you think this problem will be resolved quickly?
It's quite frustrating not being able to deploy my updates to all the workstations simply because they aren't showing as reachable...
I checked on one of the affected workstations, and restarting the WAPT service resolved the issue.
It's quite frustrating not being able to deploy my updates to all the workstations simply because they aren't showing as reachable...
I checked on one of the affected workstations, and restarting the WAPT service resolved the issue.
-
Christophe0110
- Messages: 53
- Registration: June 11, 2019 - 12:04
Hello,
I'd like to reiterate my question and ask again when this bug will be fixed?
It's becoming quite a nuisance to have to restart the WAPT services on several machines every time I deploy a package update...
I'm not sure that reverting to version 2.0 is safe (and I don't really see how to do it)...
I'm surprised that I'm the only one talking about this problem. I'm starting to wonder if it's really a bug or if it's just a problem affecting me?
Christophe.
I'd like to reiterate my question and ask again when this bug will be fixed?
It's becoming quite a nuisance to have to restart the WAPT services on several machines every time I deploy a package update...
I'm not sure that reverting to version 2.0 is safe (and I don't really see how to do it)...
I'm surprised that I'm the only one talking about this problem. I'm starting to wonder if it's really a bug or if it's just a problem affecting me?
Christophe.
