Connection not established - Authentication Cancelled (unless I use the ID to connect)

Derren · 2022-02-22T09:52:20+00:00

There was an error rendering this rich post.

In our TV host, we save our client servers and PCs in the list for easy access. Recently, we've been having trouble connecting to the machines. 8 times out of 10 it's been failing.

We then plug in the ID in the adhoc 'ID box' at the top and it always works. When picking the machine from the list, the error we get is as follows:

Connection not established - Authentication Cancelled

Teamviewer is working both ends. It's just when we try to connect to the machine by right clicking Remote control (with password)

I'm on TV version 15.26.4

The remote machines can be anything from 13-15 but they are using our custom TV host which we get from get.teamviewer.com/ourcompanyhost. It used to work fine. That host is now on version 15 but there there are older version dotted around that also experience this problem. Has anyone experienced this and know a fix? Thanks.

Find more posts tagged with

Accepted answers

All comments

Derren

No one? So many companies using it and we're the only ones with this issue? Very strange.

JoshP

Hello @Derren,

Thanks for your post.

I cannot say that this is a common issue, or at least one that is mentioned here often. However, we can attempt to uncover the cause!

The first thing I notice is you mention entering the ID manually works, but if you connect from your Computers & Contacts list you get the error. The first thing I would want to know is - does the error appear every time you attempt to connect from the list, or do some connections actually go through when using the Remote Control using password option?

Could you please also confirm if you simply double-click the device or if you select Remote Control using password option from the device information?

For troubleshooting, I would first suggest to verify the ID in the properties of the devices in the list are correct and identical to the ones you enter manually when you are able to successfully connect. For general connectivity issues like this, this step is a good place to start, to ensure the attempts to connect are to the same device.

I hope this helps to get the path to a solution started! Thanks in advance for any additional info.

ChazGee

We've been experiencing this steadily for the past 2 months. We are using 15.32.3.

James_Pedersen

I have same error 15.35.5

Harryhales

i have also facing same issue same error is appearing

Derren

For us, this problem has gone away. Think after a month or two since I brought it up.

mlv555

I too just started having this issue about 2 weeks ago. Any fix? I restarted, logged out and back in. Thanks!