No connection to TeamViewer Server SOLVED! FOR REAL.
SOLVED FOR REAL:
Same issues everyone has with all the faux resolutions...I found one that worked.
8 hours in this is what worked. First get rid of all malware. Use a prog of your choice.
Mainly this.... I went thru the logfile for TV, saw it was trying to connect to master TV servers and failing. So I thought F it. I manually entered under advanced connection settings, under advanced network settings, teamviewer server, for me I used master13.teamviewer.com ... UDP box checked and then bam. 3 days 8 hours of **bleep** to get TV 13 to work.
Other servers can be found in your log in the teamviewer directory. Manually put one in and try it, 1st one worked for me.
No thanks to TV staff. I aint even a programmer or IT. bahhh
Comments
-
So has anyone had luck with it as I did? anything? I'm curious to see if this works for you too.
0 -
Sounds like I have the same issue but it didn't work for me. In my Log I see that I'm trying to connect to master9. Tried that first, then master13. I can ping either server fine from the command prompt. There are the lines from my log. Curious if the "MasterCommand Blocked and ID Blocked is the same that you got.
2018/10/03 12:22:32.235 4240 6052 S0 CProcessCommandHandlerMasterConnect[40]::CreateMasterConnect(): master9.teamviewer.com:5938, Connection 40, proxy=''
2018/10/03 12:22:32.441 4240 6060 S0 CProcessCommandHandlerMasterConnect[40]::HandleMasterConnect(): Sending MasterCommand addonchannels=0&client=TV&f=Login&getdeviceauthenticationtoken=1&gw=1&gwlevel=431&hideonlinestatus=0&httpout=1&ic=**Please do not post TeamViewer IDs**&id=**Please do not post TeamViewer IDs**&iguid={700bac7d-e56a-4c76-ac73-f7ebbc54e823}&language=en&licensetype=0&mid=v4c4c**Please do not post TeamViewer IDs**108032c4c04f4c523254bf644d0f84297aaa8f300dd2a5a9d**Please do not post TeamViewer IDs**beb1<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~0dd0c5b4e712d7cef7750d93b4e6b006&midf=1&midhistory=0x54bf644d0f84_1d3d1ee2cdc07fa_**Please do not post TeamViewer IDs**|u4c4c**Please do not post TeamViewer IDs**108032c4c04f4c523254bf644d0f84297aaa8f300dd2a5a9d**Please do not post TeamViewer IDs**beb1|v4c4c**Please do not post TeamViewer IDs**108032c4c04f4c523254bf644d0f84297aaa8f300dd2a5a9d**Please do not post TeamViewer IDs**beb1<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~0dd0c5b4e712d7cef7750d93b4e6b006|windows034c4c**Please do not post TeamViewer IDs**108032c4c04f4c523254bf644d0f84297aaa8f300dd2a5a9d**Please do not post TeamViewer IDs**beb1<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~0dd0c5b4e712d7cef7750d93b4e6b006&midv=2&noofactivekeepalive=0&os=Win_10.0.17134_W&port443out=0&rhash={dd91401a-c646-76d3-bd94-d30fd2edb504}&runtime=468&smidv=3&sro=0&supportedfeatures=**Please do not post TeamViewer IDs**&tcpout=1&usageenvironment=3&usednsnames=1&v=13.2.14327
2018/10/03 12:22:32.678 4240 6060 S0 CProcessCommandHandlerMasterConnect[40]::ReceivedMasterResponse(): Received MasterCommand BLOCKED
2018/10/03 12:22:32.678 4240 6060 S0!!!CKeepAliveClient::HandleLoginUserAnswer(): ID is blocked0 -
Ok wow, you found a great solution!! Its worked fine here!! THANKKSSS
0
