I don't know the difference between "mini chat" and "full chat" (they look rather same to me), but for the sake of clarity, I right-clicked the connection and called "chat" mode, then minimized the chat window.
I am sorry for not making it clear. The mini-chat is just an extension to the regular chat mode that you ran. Mini-chat looks like a panel at the right hand side of the Full Control window. It allows you to chat during a remote session without switching to the dedicated chat window. Here is more about the mini chat.
EAV'd again in most generic of all circumstances. Simple attempt to connect to a remote system, auth is from the same domain the remote is a member of. No other domain controllers online.
I think that it is time that we suggest having a remote session and helping you out directly. Unfortunately, there are no other ideas why this might be happening and we need to see your setup with our own eyes.
If this is an option for you, please let us know at firstname.lastname@example.org and we will discuss the details.
1. Add the Host installer to your antivirus software exceptions list. Specifically, add two folders to the exceptions: the folder where you downloaded the installer (I also recommend that you re-download the file) and the target folder "C:\Program Files (x86)\Remote Utilities - Host". The latter may not be created yet, just add it manually to your a/v exceptions.
3. You may also check the Microsoft Fixit tool in case you cannot get rid of your previous installation.
Once you complete the steps above, restart your computer and try installing again. Make sure that the Windows account has full administrative privileges because they are required when installing the Host (it runs as a system service after the installation).
I have a feeling that there's a suppressed crash on closing the main application with a chat window open. The notable "blip" could be heard and the notification icon stays in tray area until you hover it.
"This connection mode is disabled" - which "this" ? There's no mention of the attempted connection mode in the notification balloon or in the message dialog. Change the title to something like "Access denied - <mode>", please.
It makes sense, thanks. I will add your suggestion to our wish list.
Wish I could connect to a new host. It says the access is denied/chosen connection mode disabled on host, no matter what I try. Thank God I managed to enable RDP before starting these experiments.
The access is enabled for local Administrators group. The user I attempt to connect with is both a direct member of it and the member of Domain Admins group, which is also a member of it.
I assume that you are referring to using "Windows security" as your authentication method.
The user I attempt to connect with
That is, the user whose credentials you enter in the authorization prompt, correct?
Could you send me a screenshot of your Host settings, namely the window where you set permissions for the account that you then use to authorize on the remote Host. You can send the screenshot to email@example.com.
2. Locate the file config_4.xml in the Remote Utilities Viewer %appdata% folder.
3. Remove the file from that folder. Send the file to us for examination at firstname.lastname@example.org . This file doesn't contain any sensitive data, just your license information and Viewer settings. We want to check if it was corrupted somehow.
4. Start the Viewer. It should re-create the file again, you will need to re-enter your license key.
5. Start the File Transfer mode, resize its window to your liking, then close the Viewer and again open it and start the File Transfer mode. The program must remember the size that you set the last time.