Brighter Posted July 24, 2019 Report Share Posted July 24, 2019 Hello we are currently having some problems with remote display computer access with version 6.4.1 We have 4x 4k displays connected to the server and when going to remote access we get the message " can't establish remote access connection". We then see the display computer exit out to the windows desktop. When we send the request again it works as the display computer is already there waiting. If we drop down to 1x 4k display it works perfectly every time. We have come to the conclusion that the software is not waiting long enough for the display computer to exit to desktop when 4x 4k outputs are being used. Any Help would be appreciated ! Thanks 0 Quote Link to comment Share on other sites More sharing options...
joakim Posted July 25, 2019 Report Share Posted July 25, 2019 Hi Brighter, Your conclusion that the software is not waiting long enough for the display computer to enter desktop mode is correct. This is not a problem that is exclusive to WATCHOUT 6.4.1 but rather something that is present in the software used for remote desktop access. We are looking into the problem but as of now the workaround is to wait until WATCHOUT has gone into desktop mode and then try to establish the connection, or to continuously try to establish a remote desktop connnection until it works. Best, Joakim 0 Quote Link to comment Share on other sites More sharing options...
Brighter Posted July 25, 2019 Author Report Share Posted July 25, 2019 HI Joakin Thanks for your reply. Thats fine we will do that till a solution can be found. Many Thanks 0 Quote Link to comment Share on other sites More sharing options...
Michaelmax Posted September 25, 2019 Report Share Posted September 25, 2019 I have two Identical display computers both connected to 1 1080 monitor and only one of them will allow a remote in maybe 50% of the time... the other wont allow me at all... I even tried upgrading the vlc to 4.1.3, no good... 0 Quote Link to comment Share on other sites More sharing options...
Michaelmax Posted September 26, 2019 Report Share Posted September 26, 2019 It seems that during the last round of windows defender updates, some firewall permissions were "updated". Have a look a the vnc permissions for both private and public networks in your firewall and make sure they are both checked to go through. Hope this helps. Max 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.