Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
pebroz opened this issue Feb 3, 2023 · 1 comment
Labels
Improvement Indicates an improvement for existing functionality

Comments

@pebroz
Copy link

pebroz commented Feb 3, 2023

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

@danieljoos
Copy link
Contributor

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.

@ChristianJ-TV ChristianJ-TV added the Improvement Indicates an improvement for existing functionality label Jul 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Indicates an improvement for existing functionality
Projects
None yet
Development

No branches or pull requests

3 participants