Test-TeamViewerConnectivity gives no output, no timeout, unable to abort

Open pebroz opened this issue 3 years ago • 1 comments

I have a working TeamViewer installation. GUI works, ready for connection (secure connection). Remoting to many partners during the day.

Get-TeamViewerId with no arguments returns my ID. Test-TeamViewerConnectivity with no arguments only gives a static cursor.

Ctrl+C does not work. Tested both PowerShell 7.3.2 and Windows PowerShell 5.1 on Windows 10. TeamViewer version 15.38.3 (64-bit), Tensor Basic

Feb 03 '23 09:02 pebroz

You could try to invoke the command with verbose output to see, where it hangs:

Test-TeamViewerConnectivity -Verbose

The cmdlet basically uses the built-in command Test-TcpConnection to check if a TCP connection to a list of hosts is possible. The timeout settings might be very high, so it takes a while to fail the whole list.

Feb 10 '23 12:02 danieljoos