chk out wrote:
I am using a 64bit Windows 10 OS and I am constantly getting disconnected as well.
I am seeing online this is a common problem with your application, and has been for quite awhile, is there any plans for fix this, or to help use determine what needs to be done to stop these disconnects? I really like your product, however, I would not even entertain the idea of purchasing it when the time comes that I get over 10 clients. Unfortunately, I would have to go with "the other guy"
Hello,
We received the log, thank you. However, the log shows connection attempts to our public server (id.remoteutilities.com) rather than any self-hosted server address. This discussion is about self-hosted server.
Still, even if you use the public server I can see that the Host has issues connecting to the server. There is socket error #11004. Here is from Microsoft site:
WSANO_DATA
11004
Valid name, no data record of requested type.
The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable.
https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx
Please, check that the dns name of the server is resolved properly on the Host computer. I recommend flushing the dns cache and also check your network settings, e.g. set Google DNS servers instead of your ISPs in your TCP/IP properties.
Hope that helps.