Hello, I really want to move fr om my current remote solution to RemoteUtilities, but I seem to be having issue after issue.
Here are a couple examples: I am trying to connect to a host in my own network, using the Internet-ID connection, and all I get is a blank screen. I've searched the community and have seen everything from "use legacy settings", which results in the host denying the connection and doing a countdown loop, so reboot the host. FYI.. if this host weren't in my own network wh ere I could RDP into it, how would I actually reboot the host if the viewer cannot connect? Here is the kicker... the small icon in the viewer shows the host with the lock screen. But when I try to connect, it attempts to connect, then flickers, then goes blank.
Another issue is the time it takes for the viewer to notice the screen has been locked or the user logged out. In that "other" remote software, it is instantaneous to see the locked screen. In Viewer, it takes the better part of 20-30 seconds.
I am running all current software: viewer, host and RU server.
20-30 seconds is too much even for the worst possible Internet connection like 3G or gprs, not to say a regular broadband connection. The reason for the problem is not in connectivity, but most likely in hardware/software/drivers on the target (Host) computer.
What graphics card do you use on the remote Host? What is the operating system? Also, please check if the graphics card driver is updated to the most recent version.
Hi Conrad, I agree that 20-30 seconds for the locked screen is a long time. Regarding the blank screen, I just updated the graphics driver to the newest release. I have an AMD Radeon RX 580 and upgraded to Adrenalin 2019 Edition 19.9.2 Recommended (WHQL). When I connect, it will quickly flash two shadow borders and then they disappear and the screen stays black. It's as if the rendering isn't happening.
Update: I tried to get a screen grab using the recording tools and the video is just dark so that wasn't working. I was able to snap a screenshot as the connection was occurring. See attached.