1. Check that you have the most recent version of both Viewer and Host. This should be 18.104.22.168 as of this writing. There used to be issues with previous versions and Windows update, as described in this article.
2. If there is antivirus software on the Host computer, make sure you add the Host installation path to its exception list. This is recommended even if you don't have issues with this a/v software so far - you never know when they decide to block or restrict the software next time. A/V programs don't like remote controls much and often mark such programs as riskware.
Specifically about Symantec - there were couple of issues with them recently and each time we reported to Symantec. The last time they responded that the issue was fixed. But if you still have issues with Host settings erased or reset - and this is a sure sign of either a/v activity or Windows update activity - then let us know.
I will now convert this thread to a support ticket and we'll continue there. We may have a remote session and check if your Viewer is at all able to connect to any Hosts (e.g. our hosts here) and try to find the root cause.
Could you send your Internet-ID (NOT the password, just the ID) to me via forum private message or at email@example.com. I will check if your Host is accessible to verify that it's the issue on your Viewer side.
I am using a corporate server, but here's the thing: So it my friend who is able to connect to my Host. He and I are using the same connection, but for some reason, he is able to connect, while I am not.
This narrows down the issue to your specific Viewer workstation or connection properties. Make sure that you use correct Internet-ID number or better still - delete the connection entry in your Viewer, restart the Viewer and add a new connection from scratch. Also, you may refer to this list for solutions to potential issues with internet-ID connection:
so it seems to be either a problem with my Viewer or a problem with my outgoing signal.
Yes, if a third-party can connect successfully to your Host, then the problem is with most likely on the Viewer side.
One question before we proceed - are you using Viewer in a corporate network? I'm asking that because corporate network policies are often very strict and rather block any connections by default than allow them. The Viewer must be able to connect to our intermediary server , at least if you use Internet ID connection type and specify our default server as a relay (this is the default option).
Yes, the blank screen feature works very differently in Windows 8/10. In fact, there is no blank screen, it's just the monitor that is turned off. As you probably noticed, the Host offers you to install a special monitor driver which is required if you need to use the blank remote screen feature with Windows 8/10.
As such, the custom text/html/image option will be discontinued starting the very next update. We will remove the related controls from the Viewer interface in the upcoming update.
If screen blanking is turned off, the host user sees the screen as normal. I'm guessing this is a bug in the monitor lock driver for windows 10, but I could be wrong. Is there something I'm doing wrong?
Could you please elaborate on this? If screen blanking is off, the remote user should see the monitor, yes. Or did you mean something different?