![]() Again, accessing same remote clients from a win10 box on same net as win11 host would concurrently remain responsive. So something there - I think I’ve seen cases of the unresponsive/black teamviewer screen related to display drivers, but in this case something with the network (routing? caching?) seems to be at fault, particular to win11. For the record, the ill behavior was replicated across two different ISPs on two different network stacks. (The name may be different in different parts of the world.) Navigate to the location where you downloaded the file then double click it to run the installation. I have also tried uninstall and then download afresh, but experience the same problem. Download and installation Go to the TeamViewer web page and press the Download TeamViewer button and follow the instructions to save the setup file, Teamviewsetupen.exe. ![]() There is a message saying that TeamViewer will continue to download, but that is not the case. Disconnecting from WiFi and reconnecting also did nothing. I was using V9 and tried to upgrade to V14, but the download stops part way through. Disco’ing from cell and back to WiFi, they seem to remain responsive even after multiple session restarts.Ĭonversely, shutting down TV and restarting service did nothing for me. ![]() I’ve found that disco’ing from a wifi network, reconnecting to cell network and trying again, those unresponsive clients start rendering fine. While version 10 is working perfectly, when I try to connect with teamviewer version 11, it says that there are problems with a protocol. ![]() Again the behavior I’m seeing is that some remote endpoints will seem to connect and operate fine, while others connect but just hang with a frozen screen, though they are accepting keyboard input. 1 Hey there, I have problems with my teamviewer 11. An additional note for anyone interested - I’ve found a workaround, I guess. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |