"Connection not established, Authentication canceled"

paul-2018

Have teamviewer host installed on a server and since yesterday that's the message I'm getting, the server is of course online as I can access the network resources located on it, it's just teamviewer that stopped working.

What could possible cause that? It's a pain to have to plug a monitor to the server every time this happens just to restart the teamviewer windows service to get it back working again.

Log Preview ([link removed by moderator]):

2018/04/19 15:15:25.727  4388  4604 S0!! TerminalServer: No SessionInfo for 2 (SendStatusInfo)
2018/04/19 15:15:41.979  4388  4604 S0   SERVICE_CONTROL_STOP
2018/04/19 15:15:41.979  4388  3176 S0   CAcceptServer[:::5938]::HandleAccept(): Accept canceled
2018/04/19 15:15:41.979  4388  1584 S0   CAcceptServer[0.0.0.0:5938]::HandleAccept(): Accept canceled
2018/04/19 15:15:41.979  4388 14328 S0   TeamViewer is going offline!
2018/04/19 15:15:41.979  9600  9376 G1   Received Control_TerminateProcess
2018/04/19 15:15:41.979  4388 14328 S0   RemoteSessionManager::ClearAllRemoteSessions(): RemoteSession

Find more posts tagged with

Comments

Idolitorus

Thank you for the patch. I away in France and needed to re-start Outlook on a remote computer. Your fix worked immediately. Thanks.

LuizCataldo

Remove IPV6 protocolo in Windows

owanneke

I have the same issue on my Mac version, is there a fix for that too?

Joker88

While I didn't try the regedit, your post led me to view DNS settings on a machine I was having this issue with. After making minor changes to DNS, The "Authentication Canceled" appears to have immediately stopped without having to restart the TV service. I hope the code worked for you and others

ArneDeryckere

thanks for this update, testing this now

paul-2018

The teamviewer support has shared with me a possible solution with me, I'm currently trying it out and we'll see it if will prevent further "authentication cancelled" issues that require restarting teamviewer.

We believe the application may be having issues resolving DNS.

Could you please add the following registry key to your system.

key - DWORD 32
name - AllowExternalHooks
value - decimal 1
location- HKLM\Software\Wow6432node\TeamViewer if 64bit machine
HKLM\Software\TeamViewer if 32bit machine

Once the key is added please restart the TeamViewer service.

If you are feeling too lazy to edit the registry I have created a .reg that will insert it for you, feel free to right click and check the contents:

32-bit Registry Patch

64-bit Registry Patch

ITjake

same here, we recently switched from **Third Party Product** to tv for our remote support needs and on top of the cost or rollout though a bunch of clients now we keep on getting bugs like this all over the place. talk about buyers remorse...

ArneDeryckere

Following this issue as we have it a lot as well.
Would really like to see this solved as the purpose of teamviewer is to take over when needed. Now we need to ask our customers to restart the hosts which is not intended purpose