Asur

Windows 10 Computer will not connect.

3 posts in this topic

[ UI ] [2017-08-01T15:51:50] WARNNIG: no font file: Raleway.otf

[ UI ] [2017-08-01T15:51:50] INFO: log filename: C:/Users/derek/AppData/Local/Symless/Synergy/synergy.log

[ UI ] [2017-08-01T15:51:51] DEBUG: new added screen pos: 257 161

[ UI ] [2017-08-01T15:51:52] DEBUG: Profile ID: 73 name: default

[ UI ] [2017-08-01T15:51:52] DEBUG: current version is update to date

[ UI ] [2017-08-01T15:51:52] INFO: write configuration file complete

[ UI ] [2017-08-01T15:51:52] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:51:52] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:51:55] DEBUG: report to cloud: destId 139 successfulIp failedIp 192.168.1.132

[ UI ] [2017-08-01T15:51:55] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:51:55] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:51:58] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:51:58] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:01] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:01] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:04] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:04] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:07] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:07] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:10] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:10] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:13] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:13] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:16] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:16] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:19] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:19] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:22] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:22] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:25] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:25] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:28] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:28] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:31] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:31] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:34] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:34] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:37] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:37] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:40] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:40] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:43] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:43] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:46] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:46] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:49] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:49] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:52] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:52] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:55] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:55] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:52:58] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:52:58] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:53:01] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:53:01] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:53:04] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:53:04] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:53:07] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:53:07] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:53:10] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:53:10] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:53:13] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:53:13] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:53:16] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:53:16] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:53:19] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:53:19] DEBUG: retry in 3 seconds

[ UI ] [2017-08-01T15:53:22] DEBUG: can not find any successful connectivity result for the server screen: 139

[ UI ] [2017-08-01T15:53:22] DEBUG: retry in 3 seconds

 

 

 

 

Back to not being able to connect my Windows 10 PC after the update. 

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now