Community

took · ‎09 Apr 2017,

I see the following in the log:

2017/04/09 19:54:16.304 3480 4740 S0 CProcessCommandHandlerMasterConnect[98]::CreateMasterConnect(): master3.teamviewer.com:5938, Connection 98, proxy=''
2017/04/09 19:54:21.307 3480 4748 S0 CTcpConnectionBase[98]::HandleConnectTimeout(). Connect timed out to master3.teamviewer.com:5938
2017/04/09 19:54:21.307 3480 4740 S0! CProcessCommandHandlerMasterConnect[98]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/04/09 19:54:21.313 3480 4740 S0!!!Connect to Master master3.teamviewer.com / 185.188.32.3 failed!
2017/04/09 19:54:21.336 3480 4740 S0!! CMasterConnectorAsio::HandleMasterResponseLogin(): MasterConnect failed. ErrorCode=10

Esther · ‎21 Apr 2017,

Hi there,

We have just received information that the ISP has taken care of the underlying issue.

Can you please test your connection and confirm whether your TeamViewer is working again?

Thank you in advance, Esther

Community Manager

Did my reply answer your question? Accept it as a solution to help others.
Find this helpful? Say thanks by clicking on the Thumbs Up button. Find more information here: Knowledge Base | Community Blog | How to get started

View solution in original post

Thiersee · ‎09 Apr 2017,

The server has been moved to another location on 8-9 April!

took · ‎09 Apr 2017,

I am aware of that. But right now the server status page shows that every service is operational, yet my Teamviewer client still cannot connect.

took · ‎09 Apr 2017,

Btw, I have no problem pinging master3.teamviewer.com, so I guess the network itself works fine.

mthiel · ‎09 Apr 2017,

Is this the Andriod App you are having issues with? On my mobile device, the Teamviewer Android App cannot connect to the Teamviewer server (although I can connect through Wi-Fi just fine).

Frank88 · ‎09 Apr 2017,

Me too, and I can ping pass master1/2/3.teamviewer.com, but also can't connect to TV server since yesterday.

DomLan · ‎09 Apr 2017,

Hi,

as indicated by @Thiersee, IPs are changed last night.

Try first to flush your DNS cache: (Windows) Start -> cmd -> ipconfig /flushdns

(Android) settings -> applications -> Network Location -> Clear data.

Regards

Domenico Langone
MCSD: App Builder

MykhayloSh · ‎09 Apr 2017,

Also can't connect to teamviewer servers. These are recent logs.

Using latest update of teamviewer 12, on Windows Server, on Windows 8.1, on Ubuntu 16.04 LTS (not working on any machine of those)

2017/04/09 20:31:26.005  1660 4126276416 S   CInterProcessNetwork: Received DisconnectIPC from processID 12542 (ProcessType: 2 in Session 0) with reason 1
2017/04/09 20:31:26.005  1660 4126276416 S   Process 12542 in session 0 has terminated
2017/04/09 20:31:26.005  1660 4126276416 S   TerminalServer::ProcessTerminated_Finalize: process 12542 terminated
2017/04/09 20:31:26.005  1660 4126276416 S   SysSessionInfoManager: updating session information for session 0 from GUI
2017/04/09 20:31:26.006  1660 4134669120 S   CTcpProcessConnector::HandleRead(): Socket gracefully closed (PID=12542)
2017/04/09 20:31:26.006  1660 4134669120 S   CTcpProcessConnector::CloseConnection(): PID=12542
2017/04/09 20:31:26.006  1660 4134669120 S   CInterProcessNetwork::NewInterProcessDataAvailable(): ConnectionClosed session=0 ptype=2
2017/04/09 20:31:26.006  1660 4134669120 S   UpdateOnlineState m_ManualStop
2017/04/09 20:31:26.006  1660 4134669120 S   CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 107: Transport endpoint is not connected
2017/04/09 20:31:30.512  1660 4134669120 S   CAcceptServer::HandleAccept: new connection from 127.0.0.1:37581
2017/04/09 20:31:30.551  1660 4134669120 S   Updated sessions: [ 0 C  leo ]  [ 1000000  L root ]  
2017/04/09 20:31:30.551  1660 4134669120 S   UpdateOnlineState m_ManualStop
2017/04/09 20:31:30.551  1660 4134669120 S   TerminalServer: ProcessConnected type 2 PID 12740
2017/04/09 20:31:30.551  1660 4134669120 S   SysSessionInfoManager: updating session information for session 0 from GUI
2017/04/09 20:31:30.553  1660 4134669120 S   Updated sessions: [ 0 C  leo ]  [ 1000000  L root ]  
2017/04/09 20:31:30.553  1660 4134669120 S   UpdateOnlineState m_ManualStop
2017/04/09 20:31:30.611  1660 4126276416 S   UpdateOnlineState newOnlineValue 1

Frank88 · ‎10 Apr 2017,

Updted DNS, but didn't work. The PC can ping master1.teamviewer.com passed. There are logs following: 2017/04/10 09:02:31.593 2792 2872 S0 CTcpConnectionBase[10]::HandleConnectTimeout(). Connect timed out to master1.teamviewer.com:5938 2017/04/10 09:02:31.593 2792 2864 S0! CProcessCommandHandlerMasterConnect[10]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed 2017/04/10 09:02:31.593 2792 2864 S0!!!Connect to Master master1.teamviewer.com / 185.188.32.1 failed! 2017/04/10 09:02:31.593 2792 2864 S0!! CMasterConnectorAsio::HandleMasterResponseRegister(): MasterConnect failed. ErrorCode=10

Eve · ‎10 Apr 2017,

did you solve it ?

i have the same problem.............

took · ‎10 Apr 2017,

I flushed DNS as instructed by @DomLan, but the IP address of master3.teamviewer.com remains the same, so it didn't fix the problem.

I have the same problem on Windows and Android.

Ahrimans · ‎10 Apr 2017,

I have the same problem.............

mthiel · ‎10 Apr 2017,

I found a workaround for the "Teamviewer Android App not working on mobile" issue:

1. Turn on the hotspot on the phone that I am having the issue.

2. On another Android device, connect to the hotspot using Wi-fi.

3. Use Teamviewer on the Android device from step #2.

This means that you need to use the Hotspot data on your phone, and have a second Android device on hand.

Lian · ‎10 Apr 2017,

I have the same problem.............

sim · ‎10 Apr 2017,

@DomLan wrote:
Hi,
as indicated by @Thiersee, IPs are changed last night.
Try first to flush your DNS cache: (Windows) Start -> cmd -> ipconfig /flushdns
(Android) settings -> applications -> Network Location -> Clear data.
Regards

Hi, DomLan,

I got the same situation here, my latest version of Teamviewer kept showing 'Not ready. Please check your connection' since yesterday, then I read about the migration but the issue remains as of now, the log file showing the same:

2017/04/10 13:21:19.034  9912  9452 G1   Activating Router carrier
2017/04/10 13:21:19.382  9912  9416 G1   CKeepAliveClientClient::HandlePing(): success
2017/04/10 13:21:19.382  9912  9416 G1   Resource-Language: en
2017/04/10 13:21:19.382  9912  9416 G1   Activating Router carrier
2017/04/10 13:21:19.382  9912  9416 G1   CProcessCommandHandlerMasterConnect[192]::CreateMasterConnect(): master1.teamviewer.com:5938, Connection 192, proxy=''
2017/04/10 13:21:24.388  9912  9452 G1   CTcpConnectionBase[192]::HandleConnectTimeout(). Connect timed out to master1.teamviewer.com:5938
2017/04/10 13:21:24.388  9912  9932 G1!  CProcessCommandHandlerMasterConnect[192]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/04/10 13:21:24.388  9912  9932 G1!!!Connect to Master master1.teamviewer.com / 185.188.32.1 failed!
2017/04/10 13:21:24.388  9912  9932 G1!! CMasterConnectorAsio::HandleMasterResponseLogin(): MasterConnect failed. ErrorCode=10

I've tried the flushdns since yesterday, I am sure that I got the correct IPs and successful ping results, but it's not helping. (Besides, according to the ping service at <https://asm.ca.com/en/ping.php>, those IPs are the same worldwide.)

I am in Shanghai China, I've triple checked my network settings and none of them changed. My friends are also having the same issue right now.

Attach DNS results:

master1.teamviewer.com 185.188.32.1
master2.teamviewer.com 185.188.32.2
master3.teamviewer.com 185.188.32.3
master4.teamviewer.com 185.188.32.4
master5.teamviewer.com 185.188.32.5
master6.teamviewer.com 185.188.32.6
master7.teamviewer.com 185.188.32.1
master8.teamviewer.com 185.188.32.2
master9.teamviewer.com 185.188.32.3
master10.teamviewer.com 185.188.32.4
master11.teamviewer.com 185.188.32.5
master12.teamviewer.com 185.188.32.6
master13.teamviewer.com 185.188.32.3
master14.teamviewer.com 185.188.32.4
master15.teamviewer.com 185.188.32.5
master16.teamviewer.com 185.188.32.6

DomLan · ‎10 Apr 2017,

Hi,

could you try to stop and start the service TeamViewer: (Windows) Run -> Services.

(Linux):

sudo teamviewer daemon restart

Let me know the result, from the log.

Thanks

Regards

Domenico Langone
MCSD: App Builder

salonzhao · ‎10 Apr 2017,

me too. and I restart service , and reboot and reset DNS server, and use VPN. But this problem is still existed.

AditsoFredrik · ‎10 Apr 2017,

Same for me, attached a bit of log

@salonzhao wrote:
me too. and I restart service , and reboot and reset DNS server, and use VPN. But this problem is still existed.

Update: Solved my problem by setting proxy option to None, instead of the standard setting Auto

sim · ‎10 Apr 2017,

@DomLan wrote:

Hi,

could you try to stop and start the service TeamViewer: (Windows) Run -> Services.

(Linux):
sudo teamviewer daemon restart
Let me know the result, from the log.

Thanks

Regards

Hi, DomLan,

Thank you for your reply.

I am unning Teamviewer on Windows 10 Enterprise platform, both of them are latest version.

Followed your reply, I tried stop & start the corresponding service, and still not working, I made a fresh Teamviewer setup on a updated Windows 10 PC, and here is the log file:

2017/04/10 16:03:38.830 3452 1712 0 Logger started.
2017/04/10 16:03:39.221 3452 1712 0! AsioSettings::FindExternalIP: found 0 external IPs instead of 1!
2017/04/10 16:03:39.237 3452 1712 0 UpdateOnlineState newOnlineValue 1
2017/04/10 16:03:39.237 3452 1712 0! AsioSettings::FindExternalIP: found 0 external IPs instead of 1!
2017/04/10 16:03:39.268 3452 1712 0 Generating new RSA private/public key pair
2017/04/10 16:03:39.346 3452 1712 0 QueryVPNRegKey: Subkey 'SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\Configuration' (5) has no 'MatchingDeviceID' entry. Continuing...
2017/04/10 16:03:39.455 3452 1712 0 QueryVPNRegKey: Subkey 'SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\Properties' (6) has no 'MatchingDeviceID' entry. Continuing...
2017/04/10 16:03:39.565 3452 1712 S0 DesiredServices: waiting for service winmgmt



Start: 2017/04/10 16:03:40.721 (UTC+8:00)
Version: 12.0.75813 
ID: 0
Loglevel: Info (100)
License: 0
Server: master14.teamviewer.com
IC: -1737449283
CPU: Intel64 Family 6 Model 158 Stepping 9, GenuineIntel
CPU extensions: p8
OS: Win_10.0.14393_W (64-bit)
IP: [IP removed]
MID: 0x00155d010926_1d1df27e74c3f38_3027028728
MIDv: 0
Proxy-Settings: Type=1 IP= User=
IE: 11.321.14393.0
AppPath: C:\Program Files (x86)\TeamViewer\TeamViewer_Service.exe
UserAccount: SYSTEM

2017/04/10 16:03:40.830 3452 636 S0 NetWatchdog: Internet is now connected
2017/04/10 16:03:40.830 3452 1640 S0 CKeepAliveClientClient::HandleStartKeepAlive: doing nothing, online state = 0
2017/04/10 16:03:40.830 3452 1712 S0 RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE
2017/04/10 16:03:40.830 3452 2448 S0 RemoteSettingsStore: Cleanup all policies.
2017/04/10 16:03:40.830 3452 1712 S0 RemoteSettingsStoreListener: Establish connection.
2017/04/10 16:03:40.830 3452 2448 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_TVClientSetting_Policy empty
2017/04/10 16:03:40.830 3452 2448 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_Antivirus_Policy empty
2017/04/10 16:03:40.830 3452 2448 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_Backup_Policy empty
2017/04/10 16:03:40.830 3452 2448 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_RemoteManagement_Policy empty
2017/04/10 16:03:40.830 3452 2448 S0 RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE
2017/04/10 16:03:40.830 3452 1712 S0 Using IPC-Port 5939
2017/04/10 16:03:40.830 3452 1712 S0 SHMR: Initializing shared memory.
2017/04/10 16:03:40.877 3452 1712 S0 UpdateOnlineState newOnlineValue 1
2017/04/10 16:03:40.877 3452 928 S0 TeamViewer is going online!
2017/04/10 16:03:40.877 3452 1640 S0 CKeepAliveClientClient::DoReconnectInternal: doing nothing, state = 0
2017/04/10 16:03:40.877 3452 928 S0 CAntiMalwareController::IsManagedDeviceChanged(): Machine is not a managed device anymore
2017/04/10 16:03:40.877 3452 928 S0 CBackupController::IsManagedDeviceChanged(): Machine is not a managed device anymore
2017/04/10 16:03:40.877 3452 1640 S0 Activating Router carrier
2017/04/10 16:03:41.190 3452 1712 S0 Force Autostart GUI for session ID 1
2017/04/10 16:03:41.362 3452 1712 S0 CTerminalServer::getPathToApplicationExe(): Choosing standard filename.
2017/04/10 16:03:41.362 3452 1712 S0 CTerminalServer::StartGUIProcess() Filename for GUI process is C:\Program Files (x86)\TeamViewer\TeamViewer.exe
2017/04/10 16:03:41.424 3452 1712 S0 CTerminalServer::StartGUIProcess() GUI process 3300 started for user desktop-8g5g9uj\young in session 1
2017/04/10 16:03:41.424 3452 1712 S0 CTerminalServer::StartGUIProcess() Event 5 sent to GUI.
2017/04/10 16:03:41.440 3452 1712 S0 ApiServer::IsApiInstalled: The API is not registered with Windows.
2017/04/10 16:03:41.502 3452 1640 S0 NetWatchdog: Ping successful! Port: 5938
2017/04/10 16:03:41.502 3452 1640 S0 CKeepAliveClientClient::HandlePing(): success
2017/04/10 16:03:41.502 3452 1640 S0 Activating Router carrier
2017/04/10 16:03:41.502 3452 1640 S0 CProcessCommandHandlerMasterConnect[2]::CreateMasterConnect(): master14.teamviewer.com:5938, Connection 2, proxy=''
2017/04/10 16:03:43.393 3452 1264 S0 CAcceptServer::HandleAccept: new connection from 127.0.0.1:1698
2017/04/10 16:03:43.393 3452 1640 S0 TerminalServer: ProcessConnected PID 3300 user session 1 process type 2
2017/04/10 16:03:43.408 3452 1640 S0 CInterProcessNetwork::SetDyngateIDforSession() id=0 session=1 ptype=2
2017/04/10 16:03:43.424 3452 1640 S0 UpdateOnlineState newOnlineValue 1
2017/04/10 16:03:41.455 3300 3276 G1 Logger started.
2017/04/10 16:03:41.486 3300 3276 G1 StringCompare locale: English_United States.1252
2017/04/10 16:03:42.612 3300 3276 G1 Monitors: RDPUDD Chained DD, \\.\DISPLAY1, 1920x1080 (0,0), flags=83886085, dpi=96
2017/04/10 16:03:42.861 3300 3276 G1 CMain::LoadResourceDLLs(): No custom resource dll found
2017/04/10 16:03:42.861 3300 3276 G1 InterProcessBase::SecureNetwork created
2017/04/10 16:03:42.893 3300 3276 G1 AutoLogin::Login: enabled: 1
2017/04/10 16:03:42.893 3300 3276 G1 tvshared::WindowsSessionStateManager::WindowsSessionStateManager(05CB8C08) state 0
2017/04/10 16:03:42.893 3300 3276 G1 VoIP: VoIPCentral: Set capturing-device = "INVALID_DEVICE", rendering-device = "INVALID_DEVICE"
2017/04/10 16:03:43.393 3300 3276 G1 InterProcessBase::StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector
2017/04/10 16:03:43.393 3300 3276 G1 Opening local TCP connection to 127.0.0.1:5939
2017/04/10 16:03:43.393 3300 3276 G1 Local TCP connection established
2017/04/10 16:03:43.424 3300 3276 G1 SettingsIPCReception receive a SYNCHRONISE Settings command : UserSettings
2017/04/10 16:03:43.424 3300 3276 G1 Received Control_InitIPC_Response processtype=1
2017/04/10 16:03:43.424 3300 3276 G1 Received Control_InitIPC_Response runningProcesses=3
2017/04/10 16:03:43.424 3300 3276 G1 Control_InitIPC_Response: all processes 3 completely initialized
2017/04/10 16:03:43.424 3300 3276 G1 TAF::Handler::ctor: TAF initialized. MM=40
2017/04/10 16:03:44.002 3452 3588 S0 EnumComputers.0
2017/04/10 16:03:45.565 3300 3276 G1 MsHtmlVersionInfo: 11.0.14393.321
2017/04/10 16:03:45.565 3300 3276 G1 ManagerHolderStateMachine: Switching from None to NotReady
2017/04/10 16:03:45.580 3300 3276 G1 PredefinedSessionPassword (reset) ForceId(1) CurrentId(1) ConsoleId(3)
2017/04/10 16:03:45.580 3300 5100 G1 ChatManager::ChatManager: created
2017/04/10 16:03:45.580 3300 5100 G1 ChatManager::Factory: ChatManager created
2017/04/10 16:03:45.580 3300 5100 G1 IncomingBetterChatCommandHandler::IncomingBetterChatCommandHandler: created
2017/04/10 16:03:45.580 3300 5100 G1 IncomingChatCommandRegistration::Start: registering for ready state properties
2017/04/10 16:03:46.518 3452 1264 S0 CTcpConnectionBase[2]::HandleConnectTimeout(). Connect timed out to master14.teamviewer.com:5938
2017/04/10 16:03:46.518 3452 1640 S0! CProcessCommandHandlerMasterConnect[2]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/04/10 16:03:46.518 3452 1640 S0!!!Connect to Master master14.teamviewer.com / 185.188.32.4 failed!
2017/04/10 16:03:46.565 3452 1640 S0!! CMasterConnectorAsio::HandleMasterResponseRegister(): MasterConnect failed. ErrorCode=10
2017/04/10 16:03:48.440 3300 3276 G1 UpdateBase::StartUpdate(): Start minor update... (UpdateType=4) (TargetModule=1
2017/04/10 16:03:48.440 3300 3276 G1 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2017/04/10 16:03:48.440 3300 3276 G1 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2017/04/10 16:03:48.440 3300 3276 G1 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2017/04/10 16:03:48.440 3300 3276 G1 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2017/04/10 16:03:48.440 3300 3276 G1 IncomingChatCommandRegistration::IsTeamViewerOnlineObserver: TeamViewer-Onlinestate changed to offline
2017/04/10 16:03:48.440 3300 3276 G1 IncomingChatCommandRegistration::IsTeamViewerOnlineObserver: TeamViewer-Onlinestate changed to offline
2017/04/10 16:03:48.440 3300 3276 G1 IncomingChatCommandRegistration::IsTeamViewerOnlineObserver: TeamViewer-Onlinestate changed to offline
2017/04/10 16:03:48.440 3300 3276 G1 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2017/04/10 16:03:48.440 3300 3276 G1 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2017/04/10 16:03:48.440 3300 3276 G1 DynamicPasswordUIModel::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2017/04/10 16:03:48.627 3300 3276 G1 MachineHooks: Initialized Shm
2017/04/10 16:03:48.627 3300 3276 G1 MachineHooks: refcount = 1
2017/04/10 16:03:48.627 3300 3276 G1 MachineHooks: x64 Machine detected
2017/04/10 16:03:48.627 3300 3276 G1 MachineHooks: w32 Loader is starting
2017/04/10 16:03:48.627 3300 3276 G1 MachineHooks: x64 Loader is starting
2017/04/10 16:03:48.643 3452 1264 S0 CToken::GetSystemToken() set session 1
2017/04/10 16:03:48.643 3452 1264 S0 InterProcessNetwork: Loader process started, pid = 5204
2017/04/10 16:03:48.658 3452 1640 S0 CToken::GetSystemToken() set session 1
2017/04/10 16:03:48.658 3452 1640 S0 InterProcessNetwork: Loader process started, pid = 5220
2017/04/10 16:03:48.674 5220 5224 L64 Loader started with: "C:\Program Files (x86)\TeamViewer\tv_x64.exe" --action hooks --log C:\Program Files (x86)\TeamViewer\TeamViewer12_Logfile.log 
2017/04/10 16:03:48.705 3300 4232 G1 ProxySearch: no PAC script detected via WPAD
2017/04/10 16:03:48.705 3300 4232 G1 ProxySearch: no PAC script detected via WPAD
2017/04/10 16:03:48.705 5204 5208 L32 Loader started with: "C:\Program Files (x86)\TeamViewer\tv_w32.exe" --action hooks --log C:\Program Files (x86)\TeamViewer\TeamViewer12_Logfile.log 
2017/04/10 16:03:48.940 5220 5224 L64 Starting Loader
2017/04/10 16:03:49.580 3452 1264 S0 Activating Router carrier
2017/04/10 16:03:49.736 5204 5208 L32 Starting Loader
2017/04/10 16:03:48.627 3300 3276 H32 Loader: SharedMem Connected (seg = 0x71e0000, refcnt = 1)
2017/04/10 16:03:48.627 3300 3276 H32 teamviewer.exe: SharedMem Connected (seg = 0x71e0000, refcnt = 2)
2017/04/10 16:03:49.346 5220 5224 H64 Loader: SharedMem Connected (seg = 0x79560000, refcnt = 1)
2017/04/10 16:03:49.346 5220 5224 H64 tv_x64.exe: SharedMem Connected (seg = 0x79560000, refcnt = 2)
2017/04/10 16:03:49.752 5204 5208 H32 Loader: SharedMem Connected (seg = 0xe00000, refcnt = 1)
2017/04/10 16:03:49.752 5204 5208 H32 tv_w32.exe: SharedMem Connected (seg = 0xe00000, refcnt = 2)
2017/04/10 16:03:49.971 3452 1264 S0 CKeepAliveClientClient::HandlePing(): success
2017/04/10 16:03:49.971 3452 1264 S0 Activating Router carrier
2017/04/10 16:03:49.971 3452 1264 S0 CProcessCommandHandlerMasterConnect[4]::CreateMasterConnect(): master11.teamviewer.com:5938, Connection 4, proxy=''
2017/04/10 16:03:50.971 3300 3276 H32 teamviewer.exe: SharedMem_SetLogLevel: 0 -> 200
2017/04/10 16:03:51.565 3300 3276 G1 ITbrainWizardController::Init(): Initialisation started
2017/04/10 16:03:51.596 3300 3276 G1 Tray created!
2017/04/10 16:03:51.611 3300 3276 G1 CMainWindow::ShouldShowDynamicPassword(): dynPw=1 allowIncoming=1 id=0 ka=0 lanAllowed=0 lanOnly=0 networkState=1 showDynPwd=0
2017/04/10 16:03:51.611 3300 5100 G1 UpdateBase::StartVersionFileDownload(): Start download of version file...(Version : 3.0, Channel: 1 )
2017/04/10 16:03:51.658 3300 5364 G1 ChangeThreadDesktop(): SetThreadDesktop to default successful
2017/04/10 16:03:51.690 3300 3276 G1 CMainWindow::SetVisibleDependingOnWindowState(): P_FORCE_WINSTATE_ONCE = WinState::Maximized
2017/04/10 16:03:51.846 3300 3276 G1 ApiServer::IsApiInstalled: The API is not registered with Windows.
2017/04/10 16:03:52.111 3300 5396 G1 LateBindingDirectSound: Initializing Direct Sound 8
2017/04/10 16:03:52.283 3300 5400 G1 AudioDriver: Thread Running
2017/04/10 16:03:52.283 3300 5396 G1 AudioDriver: Direct Sound Initialized
2017/04/10 16:03:52.799 3300 5396 G1 AudioDriver: using rec dev 'Primary Sound Capture Driver', '' (prim), id -1
2017/04/10 16:03:52.799 3300 5396 G1 AudioDriver: using play dev 'Primary Sound Driver', '' (prim), id -1
2017/04/10 16:03:52.815 3300 5396 G1! CAudioManager request audio mute state failed
2017/04/10 16:03:54.033 3300 5364 G1 UpdateBase::OnDownloadFinishedVersionFile() Version file successfully downloaded.
2017/04/10 16:03:54.033 3300 5364 G1 VersionFileHandler::CheckVersionFile(): Found version "12.0.75813"
2017/04/10 16:03:54.033 3300 5364 G1 VersionFileHandler::CheckVersionFile(): Found version "4mh9pM+Z19/Hsvgau1Z0lA=="
2017/04/10 16:03:54.033 3300 5364 G1 VersionFileHandler::OnDownloadFinishedVersionFile() major='' minor='12.0.75813'
2017/04/10 16:03:54.987 3452 1264 S0 CTcpConnectionBase[4]::HandleConnectTimeout(). Connect timed out to master11.teamviewer.com:5938
2017/04/10 16:03:54.987 3452 1640 S0! CProcessCommandHandlerMasterConnect[4]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/04/10 16:03:54.987 3452 1640 S0!!!Connect to Master master11.teamviewer.com / 185.188.32.5 failed!
2017/04/10 16:03:54.987 3452 1640 S0!! CMasterConnectorAsio::HandleMasterResponseRegister(): MasterConnect failed. ErrorCode=10
2017/04/10 16:03:57.987 3452 1264 S0 Activating Router carrier
2017/04/10 16:03:58.408 3452 1264 S0 CKeepAliveClientClient::HandlePing(): success
2017/04/10 16:03:58.408 3452 1264 S0 Activating Router carrier
2017/04/10 16:03:58.408 3452 1264 S0 CProcessCommandHandlerMasterConnect[6]::CreateMasterConnect(): master12.teamviewer.com:5938, Connection 6, proxy=''
2017/04/10 16:04:03.424 3452 1640 S0 CTcpConnectionBase[6]::HandleConnectTimeout(). Connect timed out to master12.teamviewer.com:5938
2017/04/10 16:04:03.424 3452 1640 S0! CProcessCommandHandlerMasterConnect[6]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/04/10 16:04:03.424 3452 1640 S0!!!Connect to Master master12.teamviewer.com / 185.188.32.6 failed!
2017/04/10 16:04:03.424 3452 1640 S0!! CMasterConnectorAsio::HandleMasterResponseRegister(): MasterConnect failed. ErrorCode=10
2017/04/10 16:04:06.440 3452 1264 S0 Activating Router carrier
2017/04/10 16:04:06.830 3452 1264 S0 CKeepAliveClientClient::HandlePing(): success
2017/04/10 16:04:06.830 3452 1264 S0 Activating Router carrier
2017/04/10 16:04:06.830 3452 1264 S0 CProcessCommandHandlerMasterConnect[8]::CreateMasterConnect(): master7.teamviewer.com:5938, Connection 8, proxy=''
2017/04/10 16:04:11.846 3452 1264 S0 CTcpConnectionBase[8]::HandleConnectTimeout(). Connect timed out to master7.teamviewer.com:5938
2017/04/10 16:04:11.846 3452 1640 S0! CProcessCommandHandlerMasterConnect[8]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/04/10 16:04:11.846 3452 1640 S0!!!Connect to Master master7.teamviewer.com / 185.188.32.1 failed!
2017/04/10 16:04:11.846 3452 1640 S0!! CMasterConnectorAsio::HandleMasterResponseRegister(): MasterConnect failed. ErrorCode=10

I've tried different procedures as following and got the same results:

a. Making a fresh setup on a updated windows 10 PC.

b. Running Teamviewer with 'Run only' option.

c. Running Teamviewer Portable version.

c. Download and run Teamviewer app version form Microsoft Store.

Frankx · ‎10 Apr 2017,

Hi,

Same here. Several Windows machines with latest version of TeamViewer, unable to connect to server. No Proxy selection did not work. One machine at same location does work, but don't see any difference.

Messi82 · ‎10 Apr 2017,

Same issues here (Israel)..

2017/04/10 14:49:34.109 2380 3100 S0 CProcessCommandHandlerMasterConnect[74]::CreateMasterConnect(): master14.teamviewer.com:5938, Connection 74, proxy=''
2017/04/10 14:49:39.111 2380 3112 S0 CTcpConnectionBase[74]::HandleConnectTimeout(). Connect timed out to master14.teamviewer.com:5938
2017/04/10 14:49:39.111 2380 3104 S0! CProcessCommandHandlerMasterConnect[74]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/04/10 14:49:39.111 2380 3104 S0!!!Connect to Master master14.teamviewer.com / 185.188.32.4 failed!
2017/04/10 14:49:39.111 2380 3104 S0!! CMasterConnectorAsio::HandleMasterResponseRegister(): MasterConnect failed. ErrorCode=10
2017/04/10 14:49:42.125 2380 3092 S0 Activating Router carrier
2017/04/10 14:49:42.288 2380 3112 S0 CKeepAliveClientClient::HandlePing(): success
2017/04/10 14:49:42.288 2380 3112 S0 Activating Router carrier
2017/04/10 14:49:42.288 2380 3112 S0 CProcessCommandHandlerMasterConnect[76]::CreateMasterConnect(): master11.teamviewer.com:5938, Connection 76, proxy=''
2017/04/10 14:49:47.298 2380 3100 S0 CTcpConnectionBase[76]::HandleConnectTimeout(). Connect timed out to master11.teamviewer.com:5938
2017/04/10 14:49:47.298 2380 3092 S0! CProcessCommandHandlerMasterConnect[76]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/04/10 14:49:47.298 2380 3092 S0!!!Connect to Master master11.teamviewer.com / 185.188.32.5 failed!
2017/04/10 14:49:47.298 2380 3092 S0!! CMasterConnectorAsio::HandleMasterResponseRegister(): MasterConnect failed. ErrorCode=10
2017/04/10 14:49:50.306 2380 3092 S0 Activating Router carrier
2017/04/10 14:49:50.466 2380 3116 S0 CKeepAliveClientClient::HandlePing(): success
2017/04/10 14:49:50.466 2380 3116 S0 Activating Router carrier
2017/04/10 14:49:50.466 2380 3116 S0 CProcessCommandHandlerMasterConnect[78]::CreateMasterConnect(): master5.teamviewer.com:5938, Connection 78, proxy=''
2017/04/10 14:49:55.572 2380 3116 S0 CTcpConnectionBase[78]::HandleConnectTimeout(). Connect timed out to master5.teamviewer.com:5938
2017/04/10 14:49:55.572 2380 3092 S0! CProcessCommandHandlerMasterConnect[78]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/04/10 14:49:55.668 2380 3092 S0!!!Connect to Master master5.teamviewer.com / 185.188.32.5 failed!
2017/04/10 14:49:56.273 2380 3092 S0!! CMasterConnectorAsio::HandleMasterResponseRegister(): MasterConnect failed. ErrorCode=10
2017/04/10 14:49:59.283 2380 3092 S0 Activating Router carrier
2017/04/10 14:49:59.453 2380 3112 S0 CKeepAliveClientClient::HandlePing(): success
2017/04/10 14:49:59.454 2380 3112 S0 Activating Router carrier
2017/04/10 14:49:59.454 2380 3112 S0 CProcessCommandHandlerMasterConnect[80]::CreateMasterConnect(): master10.teamviewer.com:5938, Connection 80, proxy=''
2017/04/10 14:50:01.136 2380 3092 S0 CKeepAliveClientClient::DoReconnectInternal: doing nothing, state = 1
2017/04/10 14:50:04.553 2380 3104 S0 CTcpConnectionBase[80]::HandleConnectTimeout(). Connect timed out to master10.teamviewer.com:5938
2017/04/10 14:50:04.553 2380 3092 S0! CProcessCommandHandlerMasterConnect[80]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/04/10 14:50:04.554 2380 3092 S0!!!Connect to Master master10.teamviewer.com / 185.188.32.4 failed!
2017/04/10 14:50:04.554 2380 3092 S0!! CMasterConnectorAsio::HandleMasterResponseRegister(): MasterConnect failed. ErrorCode=10

Frank88 · ‎10 Apr 2017,

Hi DomLan, Look forward to your reply. As your instruction, TV produced the log file as following: 2017/04/10 20:39:08.254 2784 1828 S0 NetWatchdog: Internet is now connected 2017/04/10 20:39:08.254 2784 3644 S0 CKeepAliveClientClient::HandleStartKeepAlive: doing nothing, online state = 0 2017/04/10 20:39:08.270 2784 5584 S0 RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE 2017/04/10 20:39:08.270 2784 4180 S0 RemoteSettingsStore: Cleanup all policies. 2017/04/10 20:39:08.270 2784 5584 S0 RemoteSettingsStoreListener: Establish connection. 2017/04/10 20:39:08.270 2784 4180 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_TVClientSetting_Policy empty 2017/04/10 20:39:08.270 2784 4180 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_Antivirus_Policy empty 2017/04/10 20:39:08.270 2784 4180 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_Backup_Policy empty 2017/04/10 20:39:08.270 2784 4180 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_RemoteManagement_Policy empty 2017/04/10 20:39:08.270 2784 4180 S0 RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE 2017/04/10 20:39:08.270 2784 5584 S0 Using IPC-Port 5939 2017/04/10 20:39:08.270 2784 5584 S0 SHMR: Initializing shared memory. 2017/04/10 20:39:08.270 2784 5584 S0 UpdateOnlineState newOnlineValue 0 2017/04/10 20:39:08.270 2784 5584 S0 CTerminalServer::RepeatedlyCheckForUserLogin() Don't start GUI for session 1 2017/04/10 20:39:08.270 2784 5584 S0 ApiServer::StartThread: Starting API server thread. 2017/04/10 20:39:08.270 2784 5584 S0 ApiServer::StartThread: Waiting for init event... 2017/04/10 20:39:08.270 2784 6964 S0 ApiServer::ApiMain: API thread started. 2017/04/10 20:39:08.270 2784 5584 S0 ApiServer::StartThread: ...init event was triggered. 2017/04/10 20:39:19.096 2784 4636 S0 SERVICE_CONTROL_STOP 2017/04/10 20:39:19.096 2784 6964 S0 ApiServer::ApiMain: API thread stopped. 2017/04/10 20:39:19.206 2784 5584 S0 SHMR: Destroying shared memory 2017/04/10 20:39:19.206 2784 5608 S0 CAcceptServer::HandleAccept: socket closed 2017/04/10 20:39:19.206 2784 5584 S0 Service ended 2017/04/10 20:39:20.489 2184 6508 0 Logger started. 2017/04/10 20:39:20.598 2184 6508 0! AsioSettings::FindExternalIP: found 0 external IPs instead of 1! 2017/04/10 20:39:20.598 2184 6508 0 UpdateOnlineState newOnlineValue 0 2017/04/10 20:39:20.598 2184 6508 0! AsioSettings::FindExternalIP: found 0 external IPs instead of 1! 2017/04/10 20:39:20.613 2184 6508 0 QueryVPNRegKey: Subkey 'SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\Properties' (23) has no 'MatchingDeviceID' entry. Continuing... 2017/04/10 20:39:20.723 2184 6508 S0 DesiredServices: waiting for service winmgmt 2017/04/10 20:39:20.816 2184 880 S0 NetWatchdog: Internet is now connected 2017/04/10 20:39:20.816 2184 2724 S0 CKeepAliveClientClient::HandleStartKeepAlive: doing nothing, online state = 0 2017/04/10 20:39:20.816 2184 6508 S0 RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE 2017/04/10 20:39:20.816 2184 932 S0 RemoteSettingsStore: Cleanup all policies. 2017/04/10 20:39:20.816 2184 6508 S0 RemoteSettingsStoreListener: Establish connection. 2017/04/10 20:39:20.816 2184 932 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_TVClientSetting_Policy empty 2017/04/10 20:39:20.816 2184 932 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_Antivirus_Policy empty 2017/04/10 20:39:20.816 2184 932 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_Backup_Policy empty 2017/04/10 20:39:20.816 2184 932 S0 RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_RemoteManagement_Policy empty 2017/04/10 20:39:20.816 2184 932 S0 RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE 2017/04/10 20:39:20.816 2184 6508 S0 Using IPC-Port 5939 2017/04/10 20:39:20.816 2184 6508 S0 SHMR: Initializing shared memory. 2017/04/10 20:39:20.816 2184 6508 S0 UpdateOnlineState newOnlineValue 0 2017/04/10 20:39:20.832 2184 6508 S0 CTerminalServer::RepeatedlyCheckForUserLogin() Don't start GUI for session 1 2017/04/10 20:39:20.832 2184 6508 S0 ApiServer::StartThread: Starting API server thread. 2017/04/10 20:39:20.832 2184 6508 S0 ApiServer::StartThread: Waiting for init event... 2017/04/10 20:39:20.832 2184 6544 S0 ApiServer::ApiMain: API thread started. 2017/04/10 20:39:20.832 2184 6508 S0 ApiServer::StartThread: ...init event was triggered.

Ahrimans · ‎10 Apr 2017,

Microsoft Windows [版本 10.0.14393] (c) 2016 Microsoft Corporation。保留所有权利。 C:\Windows\system32>ping master1.teamviewer.com 正在 Ping master1.teamviewer.com [185.188.32.1] 具有 32 字节的数据: 来自 185.188.32.1 的回复: 字节=32 时间=218ms TTL=106 来自 185.188.32.1 的回复: 字节=32 时间=217ms TTL=106 来自 185.188.32.1 的回复: 字节=32 时间=216ms TTL=106 来自 185.188.32.1 的回复: 字节=32 时间=217ms TTL=106 185.188.32.1 的 Ping 统计信息: 数据包: 已发送 = 4，已接收 = 4，丢失 = 0 (0% 丢失)，往返行程的估计时间(以毫秒为单位): 最短 = 216ms，最长 = 218ms，平均 = 217ms C:\Windows\system32>telnet master1.teamviewer.com 5938 正在连接master1.teamviewer.com...无法打开到主机的连接。在端口 5938: 连接失败 C:\Windows\system32>

ufotech · ‎10 Apr 2017,

The same here on Android 6.0.1
Removing the app and re-installing helps. Then I can login once - and never again! This is reproducable.
Any fix for this would be highly apreciated.

Esther · ‎10 Apr 2017,

Hi there,

It looks like your TeamViewer cannot make a connection from your network to our master servers.

Could you please try making a Telnet connection to one of our servers?

To do this, press "Windows + R" and enter "cmd". After you have confirmed this, a new Command Prompt window will appear.

Please enter the following command into the Command Prompt window (note: the function "telnet" must already be installed -> https://technet.microsoft.com/en-us/library/cc771275.aspx):

telnet master1.teamviewer.com 5938

telnet master1.teamviewer.com 80

telnet master1.teamviewer.com 443

Do you get a completely blank screen with a blinking cursor? That means, everything is alright on your side and we (TeamViewer) need to further investigate what could be causing this.

Or do you get an error message of some kind? If so, what does it say exactly? Please send a screenshot into this thread.

Thank you in advance and please excuse the inconvenience.

Best, Esther

Community Manager

Did my reply answer your question? Accept it as a solution to help others.
Find this helpful? Say thanks by clicking on the Thumbs Up button. Find more information here: Knowledge Base | Community Blog | How to get started

Henrywong · ‎10 Apr 2017,

你好 sim，我在深圳，也是一样的问题，但另一台电脑和其它同事的都没问题，我相信是由于迁移数据库导致的，但为何偏偏是我？

Frank88 · ‎10 Apr 2017,

Hi Esther, Under your instructions, only port 80 can be connected with your server. As to ports 5938 and 443, it reports "can't open the connection to the host at the port 443(/5938), fail to connect."

took · ‎10 Apr 2017,

For all the three ports, I got the error:

Could not open connection to the host, on port XXX : Connect failed.

Esther · ‎10 Apr 2017,

Hi there,

Could you please check whether the FQDN (fully qualified domain name) entries on your firewall are already up to date?

It could be that - for example - the IP address behind the DNS name master1.teamviewer.com is still the old address (the old one is beginning with 178.XXX.XXX.XXX).

Normally the IP addresses should be updated on your firewall after a certain time automatically.

Best, Esther

Community Manager

Did my reply answer your question? Accept it as a solution to help others.
Find this helpful? Say thanks by clicking on the Thumbs Up button. Find more information here: Knowledge Base | Community Blog | How to get started

Frank88 · ‎10 Apr 2017,

Hi Esther, the DNS has updated and the IP of master1.teamviewer.com is 185.188.32.1. It can ping passed.

ufotech · ‎10 Apr 2017,

Hi Esther

On Android I can perfectly telnet all the three ports.
Still the login fails with the messages below.

Again: After re-install all works ONCE! And then never again.

What the heck..... ?

2017/04/10 19:20:23.931 14598-14616 E/TeamViewer CTcpConnectionBase[74]::HandleReadError(): Error occured. ClientID: 0 IP: 185.188.32.1 Category: system, Error: 104 (Connection reset by peer)
2017/04/10 19:20:23.933 14598-14616 E/TeamViewer CMasterConnectorAsio::HandleMasterResponseLogin(): MasterConnect failed. ErrorCode=11

ufotech · ‎10 Apr 2017,

.. it might be interesting for you to see what it does when it for the one, single time. Quite a few errors here which could prevent every further login?

2017/04/10 19:36:06.242 28303-28303 E/NATIVE CRASH HANDLER cannot load libcorkscrew.so

2017/04/10 19:36:06.287 28303-28303 W/TeamViewer AsioSettings::FindExternalIP: found 0 external IPs instead of 1!
2017/04/10 19:36:06.287 28303-28303 E/TeamViewer ParseTextfile: Unknown header in '/data/user/0/com.teamviewer.teamviewer.market.mobile/files/global.conf': ''
2017/04/10 19:36:06.288 28303-28303 W/TeamViewer AsioSettings::FindExternalIP: found 0 external IPs instead of 1!
2017/04/10 19:36:06.290 28303-28303 I/TeamViewer Generating new RSA private/public key pair
2017/04/10 19:36:06.480 28303-28303 I/TeamViewer Starting intra process connection
2017/04/10 19:36:06.487 28303-28318 W/TeamViewer TerminalServer.GUIProcessStartedByService: no GUI process in session 10358

TeamViewer start: 2017/04/10 19:36:06.518
Version: 12.1.6675 CL(6675)
ID: 0
License: 10000
OS: And6.0.1
Arch: armv7l
Abis: armeabi-v7a armeabi

Device:
Model: SM-G900F
Release: 6.0.1
Board: MSM8974
Brand: samsung
Device: klte
Display: MMB29M.G900FXXS1CQC8
Fingerprint:samsung/kltexx/klte:6.0.1/MMB29M/G900FXXS1CQC8:user/release-keys
Host: SWDG9712
ID: MMB29M
Product: kltexx
Tags: release-keys
Time: 2017/03/16 07:46:02.000
Type: user2017/04/10 19:36:06.617 28303-28303 E/Connectivity - Networktype: MOBILE
2017/04/10 19:36:06.617 28303-28303 E/Connectivity - Networkstate: CONNECTED
2017/04/10 19:36:06.617 28303-28303 E/Connectivity -
2017/04/10 19:36:06.617 28303-28303 E/Connectivity - Prefered Network:-1
2017/04/10 19:36:06.617 28303-28303 E/Connectivity ------------------- Initial connection info -------------------

2017/04/10 19:36:37.029 28303-28320 E/TeamViewer SecureNetworkHandshake::ReceiveAckCallback: [remote ID: 31, connection ID: 1598639503] errorcode: Timeout(1)
2017/04/10 19:36:37.030 28303-28320 E/TeamViewer SecureNetworkConnectionMap: UpdateConnection: Update non existing ID in map

Carltone · ‎10 Apr 2017,

I have TMobile for Android and can't connect to remote PC via TeamViewer mobile.. it works just fine if I'm connected via WiFi but NOT over 4g cell service. What is the work around? I've tried clearing network connections in Android. I've tried DNS flush on PC. I've tried Uninstalling reinstalling on both Android AND remote PC. How do I get this working again ?

sim · ‎10 Apr 2017,

Alright... just get out of a meeting...

Hi Esther,

Thank you for your reply. I actually came to know your migration post through reddit yesterday.

Well, each port(5938/80/443) telnet attempting failed, it said:

Could not open connection to the host, on port xxxx: Connect failed

However, I managed to make it back to 'Ready to connect (secure connection)' after connecting a VPN through Taiwan/Hongkong/USA.

So let's trace it, here is the log:

Start with normal trace:

master1.teamviewer.com

Tracing route to master1.teamviewer.com [185.188.32.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  [IP removed]
  2     3 ms     3 ms     3 ms  [IP removed]
  3     3 ms     3 ms     2 ms  [IP removed]
  4     3 ms     3 ms     3 ms  124.74.209.201
  5    32 ms    29 ms     3 ms  101.95.88.49
  6     3 ms     3 ms     2 ms  59.43.116.230
  7     4 ms     4 ms     3 ms  59.43.18.30
  8    66 ms     3 ms     3 ms  59.43.246.254
  9    32 ms    32 ms    32 ms  59.43.248.110
 10    31 ms    30 ms    30 ms  203.131.250.85
 11    32 ms    44 ms    34 ms  ae-2.r22.tkokhk01.hk.bb.gin.ntt.net [129.250.6.218]
 12    69 ms    67 ms    67 ms  ae-7.r20.sngpsi05.sg.bb.gin.ntt.net [129.250.6.46]
 13   264 ms   262 ms   262 ms  ae-3.r24.frnkge08.de.bb.gin.ntt.net [129.250.7.10]
 14   282 ms   282 ms   282 ms  ae-2.r00.frnkge06.de.bb.gin.ntt.net [129.250.3.72]
 15   281 ms   280 ms   281 ms  83.231.214.146
 16   215 ms   215 ms   215 ms  master1.teamviewer.com [185.188.32.1]
 17   217 ms   217 ms   216 ms  master1.teamviewer.com [185.188.32.1]
Trace complete.

Then trace specified ports:

master1.teamviewer.com:80

Tracing route to 185.188.32.1 [master1.teamviewer.com] on port 80
Over a maximum of 20 hops.
1       2 ms    2 ms    2 ms    [IP removed]
2       6 ms    6 ms    4 ms    [IP removed]
3       2 ms    4 ms    6 ms    [IP removed]
4       8 ms    *       *       124.74.209.201
5       6 ms    58 ms   2 ms    101.95.88.53
6       5 ms    6 ms    6 ms    59.43.116.230
7       *       *       *       Request timed out.
8       36 ms   10 ms   6 ms    59.43.246.254
9       32 ms   33 ms   33 ms   59.43.183.82
10      32 ms   31 ms   33 ms   203.131.250.85
11      33 ms   33 ms   32 ms   129.250.6.218   [ae-2.r22.tkokhk01.hk.bb.gin.ntt.net]
12      71 ms   69 ms   68 ms   129.250.6.46    [ae-7.r20.sngpsi05.sg.bb.gin.ntt.net]
13      267 ms  263 ms  264 ms  129.250.7.10    [ae-3.r24.frnkge08.de.bb.gin.ntt.net]
14      285 ms  285 ms  285 ms  129.250.3.72    [ae-2.r00.frnkge06.de.bb.gin.ntt.net]
15      281 ms  283 ms  283 ms  83.231.214.146
16      *       *       *       Request timed out.
17      *       *       *       Request timed out.
18      *       *       *       Request timed out.
19      *       *       *       Request timed out.
20      *       *       *       Request timed out.
Trace Complete.

master1.teamviewer.com:443

Tracing route to 185.188.32.1 [master1.teamviewer.com] on port 443
Over a maximum of 20 hops.
1       2 ms    2 ms    2 ms    [IP removed]
2       6 ms    4 ms    6 ms    [IP removed]
3       6 ms    4 ms    6 ms    [IP removed]
4       *       *       *       Request timed out.
5       6 ms    6 ms    4 ms    59.43.77.145
6       6 ms    6 ms    4 ms    59.43.116.230
7       *       *       *       Request timed out.
8       21 ms   4 ms    6 ms    59.43.247.62
9       32 ms   33 ms   33 ms   59.43.183.82
10      35 ms   31 ms   33 ms   203.131.250.85
11      33 ms   43 ms   33 ms   129.250.6.218   [ae-2.r22.tkokhk01.hk.bb.gin.ntt.net]
12      66 ms   69 ms   67 ms   129.250.6.46    [ae-7.r20.sngpsi05.sg.bb.gin.ntt.net]
13      260 ms  262 ms  262 ms  129.250.7.10    [ae-3.r24.frnkge08.de.bb.gin.ntt.net]
14      288 ms  285 ms  284 ms  129.250.3.72    [ae-2.r00.frnkge06.de.bb.gin.ntt.net]
15      282 ms  280 ms  281 ms  83.231.214.146
16      *       *       *       Request timed out.
17      *       *       *       Request timed out.
18      *       *       *       Request timed out.
19      *       *       *       Request timed out.
20      *       *       *       Request timed out.
Trace Complete.

master1.teamviewer.com:5938

Tracing route to 185.188.32.1 [master1.teamviewer.com] on port 5938
Over a maximum of 20 hops.
1       2 ms    2 ms    2 ms    [IP removed]
2       6 ms    6 ms    4 ms    [IP removed]
3       6 ms    4 ms    5 ms    [IP removed]
4       6 ms    *       *       124.74.209.201
5       4 ms    4 ms    4 ms    59.43.77.145
6       4 ms    12 ms   4 ms    59.43.116.230
7       *       *       *       Request timed out.
8       6 ms    4 ms    6 ms    59.43.246.254
9       33 ms   33 ms   33 ms   59.43.183.82
10      31 ms   31 ms   33 ms   203.131.250.85
11      31 ms   31 ms   31 ms   129.250.6.218   [ae-2.r22.tkokhk01.hk.bb.gin.ntt.net]
12      68 ms   70 ms   68 ms   129.250.6.46    [ae-7.r20.sngpsi05.sg.bb.gin.ntt.net]
13      262 ms  262 ms  262 ms  129.250.7.10    [ae-3.r24.frnkge08.de.bb.gin.ntt.net]
14      283 ms  281 ms  287 ms  129.250.3.72    [ae-2.r00.frnkge06.de.bb.gin.ntt.net]
15      282 ms  281 ms  283 ms  83.231.214.146
16      *       *       *       Request timed out.
17      *       *       *       Request timed out.
18      *       *       *       Request timed out.
19      *       *       *       Request timed out.
20      *       *       *       Request timed out.
Trace Complete.

The same thing happened to the other 15 master server addresses, hence IMHO, it looks like there is some sort of policy-based(e.g. source region or source carrier) filter on german nodes(right after 83.231.214.146) actively blocking specific traffics, which is regularly happens in GBR & DEU.

Messi82 · ‎10 Apr 2017,

Still issues:

C:\Users\Noam>telnet master1.teamviewer.com 5938
Connecting To master1.teamviewer.com...Could not open connection to the host, on port 5938: Connect failed

C:\Users\Noam>telnet master1.teamviewer.com 80
Connecting To master1.teamviewer.com...Could not open connection to the host, on port 80: Connect failed

C:\Users\Noam>telnet master1.teamviewer.com 443
Connecting To master1.teamviewer.com...Could not open connection to the host, on port 443: Connect failed

C:\Users\Noam>ping master1.teamviewer.com

Pinging master1.teamviewer.com [185.188.32.1] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 185.188.32.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Noam>tracert master1.teamviewer.com

Tracing route to master1.teamviewer.com [185.188.32.1]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms CISCO34936 [IP removed]
2 8 ms 8 ms 8 ms [IP removed]
3 10 ms 11 ms 10 ms CON-HOT-N-V230-PT.hotnet.net.il [IP removed]
4 11 ms 10 ms 13 ms BB-H1-B3.230-PT.hotnet.net.il [213.57.0.178]
5 78 ms 78 ms 78 ms ix-ae-5-0.tcore1.FR0-Frankfurt.as6453.net [195.219.219.13]
6 79 ms 81 ms 79 ms ae-14.r02.frnkge03.de.bb.gin.ntt.net [129.250.8.173]
7 69 ms 70 ms 71 ms ae-5.r24.frnkge08.de.bb.gin.ntt.net [129.250.4.162]
8 80 ms 80 ms 78 ms ae-2.r00.frnkge06.de.bb.gin.ntt.net [129.250.3.72]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * *

rm · ‎10 Apr 2017,

We are still having issues as well as several other users it seems yet no mention of any down time on the website? OUr DNS has updated to new IP it seems still can't connect. Not happy havign to go back to MS support assistance, but it works.

sim · ‎10 Apr 2017,

@Henrywong wrote:
你好 sim，我在深圳，也是一样的问题，但另一台电脑和其它同事的都没问题，我相信是由于迁移数据库导致的，但为何偏偏是我？

你好Henry，搬迁难免会出状况，加之国内大小运营商的海外流量接口也很杂乱，从当前的沟通来看，可能是某些规则的逐级传递所需的延时导致的，应该会较快恢复正常，我们就稍安勿躁吧。:)

Frank88 · ‎11 Apr 2017,

Hi DomLan, any progress?

GianfrancoDiPie · ‎11 Apr 2017,

> telnet master1.teamviewer.com 5938
Connecting To master1.teamviewer.com...Could not open connection to the host, on port 5938: Connect failed
> telnet master1.teamviewer.com 80
Connecting To master1.teamviewer.com...Could not open connection to the host, on port 80: Connect failed
> telnet master1.teamviewer.com 443
Connecting To master1.teamviewer.com...Could not open connection to the host, on port 443: Connect failed

.... Just not working now....

StevenLU · ‎11 Apr 2017,

Dear Esther,

First, I am suffering the same issue. (Partially, I'll explain below)

Hope the following may help.

I have 2 desktop, a laptop and a pad.

The 2 desktop are located in 2 different location (so 2 different LAN environment), the other 2 devices are mobile connected based on where I use them.

So the PARTIALLY I mentioned at the begining. One of my 2 desktop is working fine and another, which the router is not in reach of my control, could not logon to teamviewer.

I have tried with my laptop at the GOOD location, the teamviewer works fine.

However, when I move to the BAD location, it failed.

Also another guess with my pad share a hotspot for my laptop, teamviewer works fine.

So I guess this may be LAN related. As the GOOD location's router is controlled by myself and has a regular reboot setting, I guess the DNS has been refreshed automatically. But I couldn't tell if the other location's router has been refreshed or not.

Hope the issue could be solved soon.

Stev

ifyoung · ‎11 Apr 2017,

many of my colleagues have the same problem.

Is there any one can help?

I have read some related issues, but nothig wokrs.

Why does this happen and how to do? or release a fixed version?

Best Regards!

ily1605 · ‎11 Apr 2017,

Since yesterday, could not log. Also tried above many ways, still does not work. I am using the latest version12, in Shanghai, China Telecom.

ufotech · ‎11 Apr 2017,

Getting slightly nervous, if this cannot be solved. Is there a way of reverting to a previous version on Android?
Or is there even an alternative?

shocking · ‎11 Apr 2017,

I also have the issue,the log shows time out,errorcode=10.Can someone have the workaround?

DomLan · ‎11 Apr 2017,

Hi,

have you try to change temporary your DNS resolver?

Try to use 8.8.8.8 -> Google Public DNS

Regards

Domenico Langone
MCSD: App Builder

ufotech · ‎11 Apr 2017,

Actually I tried with a Version 11 on the same Samsung device. It is exactly the same. Works for one time after installation - then never again.

So the issue seems not to be located in the application.

ufotech · ‎11 Apr 2017,

No. Using GSM, you can't select IP settings, unless using a hack and being root.

Not really an option.

The only work around so far: De-insall the app, and install it again. Then use it for one time. De-install again .......

Sibsrl · ‎11 Apr 2017,

Same problem from Italy, using Fastweb ISP. An our client has the same problem too (he's using Fastweb too).

Here is my trace route:

Traccia instradamento verso master1.teamviewer.com [185.188.32.1]
su un massimo di 30 punti di passaggio:

1 <1 ms <1 ms <1 ms [IP removed]
2 <1 ms <1 ms <1 ms [IP removed]
3 24 ms 24 ms 23 ms 83-103-13-129.ip.fastwebnet.it [IP removed]
4 24 ms 24 ms 24 ms 10.5.9.193
5 28 ms 28 ms 28 ms 10.254.11.141
6 29 ms 35 ms 28 ms 10.254.12.41
7 29 ms 29 ms 28 ms 62-101-124-94.fastres.net [62.101.124.94]
8 29 ms 28 ms 28 ms 89.96.200.18
9 29 ms 29 ms 29 ms mno-b2-link.telia.net [62.115.55.117]
10 44 ms 43 ms 44 ms ffm-bb4-link.telia.net [62.115.134.34]
11 57 ms 56 ms 56 ms win-bb2-link.telia.net [62.115.113.117]
12 56 ms 56 ms 56 ms win-b4-link.telia.net [62.115.112.215]
13 * * * Richiesta scaduta.
14 71 ms 71 ms 71 ms cr-01.0v-08-74.anx25.fra.de.anexia-it.com [37.25
2.248.14]
15 70 ms 71 ms 70 ms 217.146.22.246
16 71 ms 83 ms 71 ms 217.146.20.18
17 * * * Richiesta scaduta.
18 * * * Richiesta scaduta.
19 * * * Richiesta scaduta.

DomLan · ‎11 Apr 2017,

Hi @Sibsrl

http://www.fastweb.it/internet/dns-jumper-cos-e-e-come-funziona/

(anche se credo che il problema sia l'instradamento non aggiornato di Fastweb)

Regards

Domenico Langone
MCSD: App Builder

Frank88 · ‎11 Apr 2017,

DoLan, I tried,but not work. the master(from 1 to 15).teamviewer.com port 80 can be telneted, but not port 5983 and 443. Whatever which one DNS, your server can be pinged normally.

Cannot connect to Teamviewer server since yesterday

Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday

Re: Cannot connect to Teamviewer server since yesterday