Posted by Go-Train
Henagon

authentication error when connecting to linux server with "Reason 4"

Has anyone got an ideas about this? 

Im trying to connect to a linux server running Zentyal 4.2 (its basically Ubuntu 14.10 with a small business server GUI running on it) in one of our locations.  I have teamviewer host running on the server, but when I try to connect to it, I get an "Authentication Error".

I looked in the logs on the server and the connection seems to be talking between the two computers up until a point when this error appears...

CInterProcessNetwork: Received DisconnectIPC from processID 12016 (ProcessType: 4 in Session 0) with reason 4

so, what is reason 4?  anyone?   Ive got this working in many other locations but this is the first time ive seen this error.  Ill post the full log for the session below...

2017/05/25 10:45:16.455 11737 140158229784320 S   Activating Router carrier
2017/05/25 10:45:16.455 11737 140158229784320 S   CommandHandlerRouting[8]::CreatePassiveSession(): incoming session via server10003.teamviewer.com, protocol Tcp
2017/05/25 10:45:16.495 11737 140158238177024 S   StartProcessesAsync: Session ready after 0s
2017/05/25 10:45:16.495 11737 140158238177024 S   GetUserForProcessLaunch: technical (1000)
2017/05/25 10:45:16.495 11737 140158238177024 S   StartDesktopInSession: XSession: 0 [SysSession 0 [type=1 tty=7 pseudotty=0 info=1 id=c1 user=technical state=user active=1 reliable=1]]
2017/05/25 10:45:16.495 11737 140158238177024 S   GetUserForProcessLaunch: technical (1000)
2017/05/25 10:45:16.496 11737 140158238177024 S   SessionIsReady: Console 1 1 Valid 1 1 1 ready 1
2017/05/25 10:45:16.496 11737 140158238177024 S   GetPathToDesktopBinary: binary is /opt/teamviewer/tv_bin/TeamViewer_Desktop
2017/05/25 10:45:16.496 11737 140158238177024 S   Starting process "/opt/teamviewer/tv_bin/TeamViewer_Desktop" as user technical (1000)
2017/05/25 10:45:16.496 11737 140158238177024 S   Started process "/opt/teamviewer/tv_bin/TeamViewer_Desktop" (pid = 12016) as user technical (1000)
2017/05/25 10:45:16.496 11737 140158238177024 S   StartDesktopInSession: 0, pid 12016
2017/05/25 10:45:16.497 11737 140158238177024 S   ConnectionGuard: incoming remote control in sessions: 0(1)
2017/05/25 10:45:16.616 11737 140158229784320 S   CAcceptServer::HandleAccept: new connection from 127.0.0.1:49502
2017/05/25 10:45:16.653 11737 140158238177024 S   TerminalServer: ProcessConnected PID 12016 user session 0 process type 4
2017/05/25 10:45:16.653 11737 140158238177024 S   Updated sessions: [ 0 C  technical ]  [ 20    technical ]
2017/05/25 10:45:16.653 11737 140158238177024 S   UpdateOnlineState newOnlineValue 1
2017/05/25 10:45:16.702 11737 140158229784320 S   CInterProcessNetwork::SetDyngateIDforSession() id=xxxxxxxxx session=0 ptype=2
2017/05/25 10:45:16.702 11737 140158229784320 S   CInterProcessNetwork::SetDyngateIDforSession() id=xxxxxxxxx session=0 ptype=4
2017/05/25 10:45:16.749 11737 140158238177024 S   LegacyDataCmdSender[8]::SendAllData(): encryption not ready!
2017/05/25 10:45:16.793 11737 140158229784320 S   Negotiating session encryption: client hello received from xxxxxxxxx, RSA key length = 2048
2017/05/25 10:45:16.793 11737 140158229784320 S   Negotiating session encryption: client hello received from xxxxxxxxx, RSA key length = 2048
2017/05/25 10:45:16.798 11737 140158238177024 S   Negotiating session encryption: server hello sent
2017/05/25 10:45:16.922 11737 140158229784320 S   Negotiating session encryption: client handshake received
2017/05/25 10:45:16.922 11737 140158229784320 S   Negotiating session encryption: client handshake received
2017/05/25 10:45:16.930 11737 140158238177024 S   Negotiating session encryption: server handshake sent, encryption established with AES key length 256
2017/05/25 10:45:23.323 11737 140158238177024 S   ConnectionGuard: no restrictions
2017/05/25 10:45:23.323 11737 140158238177024 S   CGatewaySession[8]::EndSession(): Session to 0 ended. Estimated capacity=902kBit/s, Latency=0ms
2017/05/25 10:45:23.361 11737 140158229784320 S   CInterProcessNetwork: Received DisconnectIPC from processID 12016 (ProcessType: 4 in Session 0) with reason 4
2017/05/25 10:45:23.361 11737 140158229784320 S   Process 12016 in session 0 has terminated
2017/05/25 10:45:23.361 11737 140158229784320 S   TerminalServer::ProcessTerminated_Finalize: process 12016 terminated
2017/05/25 10:45:23.361 11737 140158238177024 S   CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=12016)
2017/05/25 10:45:23.361 11737 140158238177024 S   CTcpProcessConnector::CloseConnection(): PID=12016
2017/05/25 10:45:23.362 11737 140158238177024 S   CInterProcessNetwork::NewInterProcessDataAvailable(): ConnectionClosed session=0 ptype=4
2017/05/25 10:45:23.362 11737 140158238177024 S   UpdateOnlineState newOnlineValue 1
2017/05/25 10:45:23.362 11737 140158238177024 S   CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 107: Transport endpoint is not connected
2017/05/25 10:45:23.365 11737 140158238177024 S   Child cleanly exited pid=12016, s=0
1 Reply
Posted by TeamViewer Staff
TeamViewer Staff

Re: authentication error when connecting to linux server with "Reason 4"

Dear Go-Train,

Thank you for your post.

The disconnect reason 4 for means Terminated by Network.

At some point due to network issues, the connection ended the remote connection.

Do you still have the issue?

We are looking forward to your comments.

 

Best regards,

Christian

Did my reply answer your question? Accept it as a solution to help others, Thanks.