A while back, a customer contacted us because they were having problems connecting to Amazon WorkSpaces. This led me to dig into a PowerShell command which was new to me; Test-NetConnection
. In its simplest form, the command simply checks your network connectivity:

I, however, needed to confirm that I was able to connect to a specific computer, and so added the -ComputerName
parameter, and added the appropriate value:

Having confirmed that I was able to connect using the default port, I next needed to check whether the same was true for the ports specified in the documentation. Adding a second parameter, -port
, with the appropriate value achieved this nicely:

Honestly, this only scratches the very basics of what we can do with Test-NetConnection
, and I’m sure I’ll play around more with it in the future.
By posting a comment, you consent to our collecting the information you enter. See privacy policy for more information.