[RESOLVED] PMAD VNC

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
Vvarfendel
Messages: 10
Registration: December 5, 2017 - 2:03 PM

July 17, 2018 - 08:38

Hello everyone,

I'm having trouble remotely accessing my workstations via VNC (see attached image).

It worked perfectly in version 1.3, but not in 1.5. I'm deploying my applications correctly, firewalls and antivirus are disabled (for testing on the server and workstations), pings are successful in both directions, and the workstations are reachable in the console with a specified IP address.

If anyone has any ideas... I'd appreciate it. ;)

Regards,

Picture

- Installed WAPT version (1.5)
- Server OS (Linux) and version (CentOS 7)
- Administration/package creation machine OS (Windows 7)
Last edited by Vvarfendel on July 17, 2018 - 4:05 PM, edited 1 time.
High
Vvarfendel
Messages: 10
Registration: December 5, 2017 - 2:03 PM

July 17, 2018 - 09:48

# traceroute 192.168.60.115
traceroute to 192.168.60.115 (192.168.60.115), 30 hops max, 60 byte packets
1 gateway (192.168.1.28) 1.357 ms 1.301 ms 1.246 ms
2 192.168.60.115 (192.168.60.115) 2.177 ms * *
# traceroute PC524
traceroute to PC524 (192.168.60.115), 30 hops max, 60 byte packets
1 gateway (192.168.1.28) 1.138 ms 1.088 ms 1.037 ms
2 192.168.60.115 (192.168.60.115) 1.438 ms * *
#
High
Vvarfendel
Messages: 10
Registration: December 5, 2017 - 2:03 PM

July 17, 2018 - 3:27 PM

Even when we're on the same network, it doesn't work! Grrr
High
Vvarfendel
Messages: 10
Registration: December 5, 2017 - 2:03 PM

July 17, 2018 - 4:04 PM

Who knows why, but it works...
High
Vvarfendel
Messages: 10
Registration: December 5, 2017 - 2:03 PM

July 19, 2018 - 08:43

For those who are looking, I recreated a 32-bit/64-bit TightVNC package, installed it on the machines, and everything is OK
High
Locked

Return to "WAPT usage (Console, Agent) / WAPT usage (Console, Agent)"


  • To go further with WAPT