TeamViewer Tensor cannot connect to TeamViewer Quick Support

sazabi75

Hi,

I am using TeamViewer Tensor Basic v15.2.2756 at work to connect to my client using the TeamViewer Quick Support tool (latest version) to provide remote support and it's been working fine. But since few days ago all of a sudden it no longer works. and it stopped working while I was remote supporting my client and the connection disconnected and no longer able to connect back.

Both TM (Tensor and Quick Support) shows the green circle with "Ready to connect secure connection) at the bottom, but as soon as I try to connect from Tensor to QR, Tensor says "No connect to partner! Partner did not connect to router. Error Code: WaitforConnectFailed". but my client computer is connected to the Internet and I also asked him to reboot his home computer and the router just in case.

Here is the log from my client's computer. I have verified and nothing was on port 37014 and 37114 on my client's computer. Anyone any idea ? Thanks.

2024/10/10 07:44:30.080 7220 8424 G1!! DriverConfiguration::GetPortNumber() RegOpenKey failed: 2
2024/10/10 07:44:30.080 7220 8424 G1!!!CAcceptServer::CreateAcceptServer(): 127.0.0.1:37014, Caught boost::system::system_error exception: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted [system:10048 at E:\c\c0\11082d\1\include\boost\asio\detail\win_iocp_socket_service.hpp:243:5 in function 'bind']
2024/10/10 07:44:30.080 7220 8424 G1! ClientWebAPI: failed to start accept server on port 37014: Accept server could not be started: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted [system:10048 at E:\c\c0\11082d\1\include\boost\asio\detail\win_iocp_socket_service.hpp:243:5 in function 'bind']
2024/10/10 07:44:30.080 7220 8424 G1!!!CAcceptServer::CreateAcceptServer(): 127.0.0.1:37114, Caught boost::system::system_error exception: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted [system:10048 at E:\c\c0\11082d\1\include\boost\asio\detail\win_iocp_socket_service.hpp:243:5 in function 'bind']
2024/10/10 07:44:30.080 7220 8424 G1! ClientWebAPI: failed to start accept server on port 37114: Accept server could not be started: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted [system:10048 at E:\c\c0\11082d\1\include\boost\asio\detail\win_iocp_socket_service.hpp:243:5 in function 'bind']
2024/10/10 07:44:30.080 7220 8424 G1 Activating Router Carrier
2024/10/10 07:44:30.080 7220 8424 G1 CommandHandlerRouting[4]::CreatePassiveSession(): incoming session via hk-hkg-anx-r004.router.teamviewer.com, protocol Tcp
2024/10/10 07:44:30.081 7220 8884 G1 CTcpConnectionBase[4]::HandleResolveSuccess(): Connecting to hk-hkg-anx-r004.router.teamviewer.com
2024/10/10 07:44:30.081 7220 8884 G1 TcpConnectorv4[4]::ConnectEndpoint(): Connecting to endpoint 188.172.201.135:5938
2024/10/10 07:44:35.084 7220 8884 G1 TcpConnectorv4[4]::HandleConnectTimeout(): Connect timed out
2024/10/10 07:44:35.084 7220 8884 G1! CTcpConnectionBase[4]::HandleConnect: Connect aborted to dest-ip hk-hkg-anx-r004.router.teamviewer.com:5938 with error system:995.
2024/10/10 07:44:35.084 7220 8904 G1!! CommandHandlerRouting[4]::HandleConnectPassive(): connect failed!
2024/10/10 07:44:35.084 7220 8904 G1!! CreateIncomingClassicSession::StartSession: router connection failed
2024/10/10 07:44:35.086 7220 15256 G1 IConnection[4]::~IConnection(): Count: 1

DarrynH

Hi There.
I had similar issue with your version and a newer one. I found that as from a certain version 15.30 i think it is, they no longer support connections to older ones.
Security and trying to push towards the newer 15.50+ setup.
I did read an article on this a couple of days ago.
I had to upgrade the 15.2 up to latest 15.50+ and then it fixed it.

DarrynH

Hi There.
I had similar issue with your version and a newer one. I found that as from a certain version 15.30 i think it is, they no longer support connections to older ones.
Security and trying to push towards the newer 15.50+ setup.
I did read an article on this a couple of days ago.
I had to upgrade the 15.2 up to latest 15.50+ and then it fixed it.

sazabi75

Perfect. Thanks DarrynH. :)