![]() However, if I uses ctrl-alt-f12 and go to full screen I can see the remote system ans everything works. In reality connection is established, but no windows is displayed. Try to connect with UVNC Client 1.3.8.1 and 1.3.8.2 and it looks like connection has failed. For the most part everything seems to work fine except on connecting to some of the servers I don't get a screen. In fact it's showing the message if set to "always show" but only showing ID. But if the feature is dropped I am not sure why the text field is still in the viewer to enter a message and also the server properties still allowing me to configure when to show it. ![]() Currently I can't seem to get any notification message sent using Viewer 1.3.8.2 or Server 1.3.8.2 (or both versions equally at 1.3.8.2). So forgive me if my interpretation was wrong and the feature is basically dropped again now. You did mention some issues with the new notification feature, but I did not expect them not to work any more at all. Using version 1.3.8.2 on either server or client side does not work and message is ignored (=> viewer 1.3.8.2 does not send the message, server 1.3.8.2 does ignore the message if sent by viewer). Using version 1.3.8.1 on server and cliend side working fine. UltraVNC server 1.3.8.2 seems not to display the custom connect notification message (even when using viewer 1.3.8.1 which certainly is sending it as validated with 1.3.8.1 server)Īuthentication used: Local password (no mslogon).UltraVNC Viewer 1.3.8.2 seems not to send the send the notification text (using -InfoMsg or viewer security tab text field.I am having some regression issues with version 1.3.8.2:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |