Conrad Sallian's community posts

Hello Pepa,

Thank you for your message.

Could you try to disable/delete the first connection and see if the second connection will start working immediately. I'm not sure this is the case. That is - the problem is not that one connection is getting in the way of another, the problem is most likely that there are some other connectivity (network) issues.

Hello Vasile,

The "View only" mode is currently not supported in mobile version. We will add support for this mode in subsequent updates.

Thanks, Brian. Noted.

Hello Alejandro,

Remote camera feature per se has been discontinued. It will no longer be available in subsequent updates of the program.

There is no way to disable this banner because doing so would violate remote user privacy. Sorry for that.

Hello Jonathan,

Just wanted to clarify a few terms. The connection name is actually just a descriptive name for the entry in the address book. Whereas the actual value used as a remote computer address (this can be a hostname/DNS, an IP address or Internet-ID) is stored in either the "Direct connection" or "Internet-ID connection" field. I assume that it is one of these fields that you mean when you mention the connection name.

but is there anyway to prompt the host to check the device name and update its entry in the address book.

This problem does not exist if Internet-ID connection is used because the Internet-ID code stays the same on the host regardless of computer name. If you explicitly use direct connection though, there is no way for the Host to communicate back to the Viewer in case its hostname has changed. The Viewer will simply show the Host as offline in its address book.

You can try the following solution - switch to using Internet-ID connection. While this connection type uses an intermediary server the program still tries to find and use direct route between Viewer and Host, if possible. For this to work you should still keep the incoming TCP port 5650 on the Host open though, just as with the regular direct connection.  

If you don't want the program to connect to our public ID servers feel free to install and use the self-hosted server, it's free.

Hope that helps.

Hello Jonathan,

Thank you for your question. Do you use Active Directory sync capabilities available in the Viewer?

Hi Michael,

It's not exactly incompatibility. As with previous versions you can connect from 6.9.0.1 Viewer to 6.8.0.1 Host and update it if necessary (only now in beta the Simple update doesn't work yet, this is intentional - it will work in the final release).

Besides, there is another consideration - we just wanted to let as many customers as possible to upgrade for free. Given that this version has very important changes, namely new encryption algo and authorization scheme, we need as broad user base as possible to receive more feedback.

Hi Anousch,

Ok, but can i have a list like of all my servers who's in my adress book of my custom RU ?

Do you mean if you can separate in your address book which hosts connect through which server (public or self-hosted)?

Not in Android/iOS version yet, sorry. We are working on adding a full fledged address book to the mobile client though.

As for the desktop Viewer you should just switch to the Details view an look/sort using the Connection type column.

Hello Brian,

Thank you for your post.

I didn't have this problem with the product that rhymes with Beam Screwer.

:)

The Host was Current version: 6.8.0.1 whereas the Viewer was Version 6.9.1.0 Beta 1. As soon as I updated the Host to the most recent Beta version, it has stopped disconnecting me.

Yes, you should avoid version mismatch between Viewer and Host if possible. This is especially true about the latest beta - there have been a lot of improvements and a whole new authorization system implemented in it.

Still, we will see how we can better inform the user about version mismatch right in the program.

Hello Anna,

Thank you for your message. Unfortunately, that is no surprise. ESET has never even bothered answering our false positive reports.

In version 6.9.0.1 (currently in beta as of Sep 8, 2018) we implemented some measures that should eliminate such false detections, we'll see.