Use PowerShell to test a network port instead of using Telnet

Here is a quick post to show that you can use PowerShell in place of Telnet to test network connectivity

Test-NetConnection -ComputerName 192.168.0.1 -port 3610

or in short form

tnc 192.182.1.10 -port 443

2 Replies to “Use PowerShell to test a network port instead of using Telnet”

Sir Zzyzx says:

October 10, 2020 at 11:58 pm

Hrm… why does tnc w/o argumets test this ip address?

PS C:\Users\njmea> tnc ComputerName : internetbeacon.msedge.net
RemoteAddress : 13.107.4.52
InterfaceAlias : Wi-Fi
SourceAddress : 192.168.1.10
PingSucceeded : True
PingReplyDetails (RTT) : 171 ms

Reply
1. Peter Dolkens says:
  
  October 11, 2020 at 5:22 am
  
  This is windows’ inbuilt internet-detection endpoint. It is what changes your network icon from “no internet” to the “ethernet” or “wifi” icon.
  
  Presumably, it’s using tnc to do so.
  
  I believe you can also customize that endpoint via registry.
  
  Reply