Conrad Sallian's community posts

Hello,

Im sorry to inform that i have triple check the ports and they do match , im using the default ports 5655. Windows Firewall is turn OFF for all profiles, and theres no other firewall running in the machine.

Do you also have both Remote Utilities and RU Server updated to the most recent version? It's 6.8.0.1 and 2.6.0.6 respectively. You can download the latest versions from here.

If you do and if nothing else helps please let me know and I'll create a ticket from this thread. We may have a remote session because I cannot come up with any other reasons why the Viewer may not be connecting.

Also be sure to check under Server Configuration-Access and administration-Allow named pipes connection (local connection). Make sure it's checked...

Hi Benny,

Thanks for contributing. However, this is not about "administration connection" but rather about a regular Viewer signing in on the server.

Hello,

Thank you for your post.

what I can't do is to connect the viewer to self hosted server. I just cant login. even with a viewer inside the same network using the local ip address of the server, it just dont connect. I enter the user name and password created in the Self Hosted and the viewer just says signing on to "192.168.3.99" and then goes away and nothing, thats all i get.

Make sure that the port specified in Viewer's server manage (Manage tab -> Server manager -> your server's properties) is the same as the communication port specified in the configuration dialog on the server side. See the attached screenshots.

Also, make sure that this port is allowed on the server machine in the firewall settings (inbound TCP port).

Hope that helps.

Hello,

Thank you for your message.

You probably have an outdated version of Remote Utilities. This issue used to be up until version 6.5, whereas the current version is 6.8.0.1. So it is recommend that you update your Hosts (and Viewer for that matter).

Hope that helps.

Hello Donovan,

Thank you for the suggestion! Actually, the mobile version will be seriously revamped very soon and a full-fledged address book (compatible with the desktop book) will be added.

Don't hesitate to ask me if you have other questions.

Hello Donovan,

Do you receive any error message?

Hello Alan,

Does this imply that the Viewer will be out this year (2017). Not long left of this year if that's the case so you must have a date pencilled in for its release?

That is most likely. At least this is something we are currently working on most of the time. I.e. it is no longer just "planned", it's already in the works.

Thanks.

Hi Lou,

Thank you for your message.

Yes, this is a known problem. A fix requires some extensive revamp of the File Transfer mode and we have this on our roadmap. We will do our best to implement this as fast as we can, perhaps even this year.

Hello Ron,

I also recommend that you add the Host installation path to Bitdefender exceptions, just in case. Even if BD falsely detects RU in the future your Host files will be safe from deletion.

Thanks.

Hi Ron,

The connection problem might not be necessarily caused by antivirus software. Perhaps this is something else. Only the Host log can tell.  

Is there any chance you can get this log?

Hello Ron,

Thank you for your post.

It's weeks from now, but not too many. Initially, we planned to release version 6.9 much earlier. In fact it would have already been available at the moment. Then we decided to add quite a few important fixes and features - namely two-factor authentication. So it will take a while.

I had a total of about 8 machines that Windows Defender and Security Essentials had quarantined.

That might be the case, although Microsoft was very fast to fix the issue. We haven't been reported issues with Windows Defender since then.

We continue to send reports and communicate with a/v software vendors regarding false positive classifications. The problem is that nowadays almost all a/v software vendors heavily rely on machine learning algorithms which are very inaccurate. Alas, they don't care much about their customers who have to restore their lost data or installations after another erroneous detection.