How to check if a port is open on Windows (no Telnet needed)
Test a port on Windows with Test-NetConnection instead of Telnet, read what the result means, and keep your servers in view with a dashboard tile.
The quickest way to check if a port is open on Windows is PowerShell, no Telnet required:
Test-NetConnection server.example.com -Port 443
If the output says TcpTestSucceeded : True, the server accepted a connection on that port. If it
says False, no connection was made. Test-NetConnection is built into Windows. Telnet, by contrast,
has to be installed before the command works at all, as Microsoft notes.
The built-in tools share one limit: each gives you a snapshot. If you rely on several servers, remote desktop machines or web addresses every day, you end up typing the same command again and reading text output. Further down there is a tile that checks every time you open the dashboard and shows the status and the cause right away. First, the built-in tools.
What “port open” actually means
A port counts as open when a service on the target machine is listening on it (a web server on 443, Remote Desktop on 3389) and no firewall along the way drops the connection. That is why a test can end in different ways, each with a different cause:
- Accepted: the service is running and the path is clear.
- Refused: the machine is reachable, but nothing listens on the port, or a firewall actively rejects the connection.
- Timeout: no answer at all. Usually a firewall silently drops the packets, or the machine is off.
- Unknown host: the server name cannot be resolved to an address. The port was never asked.
It also matters where you test from. A test on your PC checks the path from your PC to the server. Online “port checker” sites test your public address from a server on the internet, that is, whether your router forwards a port correctly. These are two different questions; an online check says nothing about whether your workstation can reach the company server.
Test a port with PowerShell: Test-NetConnection
Test-NetConnection is part of the NetTCPIP PowerShell module that ships with Windows. Open
PowerShell (Start menu, type “PowerShell”) and give it a server and a port:
Test-NetConnection fileserver01 -Port 445
The most useful options, according to Microsoft:
-Port <number>tests any TCP port.-CommonTCPPortaccepts four short names:HTTP,RDP,SMBandWINRM. SoTest-NetConnection rdp-host -CommonTCPPort RDPsaves you the port number.-InformationLevel Quietreturns onlyTrueorFalse. Handy in scripts.-InformationLevel Detailedadds name resolution, network interface and route.- With just the target name, that is without
-Portand without-CommonTCPPort, the command only pings and reportsPingSucceeded.
The output lists the name (ComputerName), the resolved address (RemoteAddress), the port
(RemotePort) and the result (TcpTestSucceeded). When the result is False, the command does not
tell you whether the port was refused or the connection timed out. When you troubleshoot, that is
often exactly the question that matters.
Test a port from Command Prompt (cmd)
The classic Command Prompt has no dedicated port test. Two ways around it:
- Call PowerShell from cmd:
powershell -Command "Test-NetConnection server -Port 443"gives the same result as above. - Telnet:
telnet server 443attempts a TCP connection to the given port (without a port, Telnet uses 23). Microsoft notes that the Telnet client must be installed first; a fresh Windows does not include it. Telnet was built for remote sessions, not as a testing tool. If you only need it for port tests,Test-NetConnectionis the shorter route.
Which ports your own PC is listening on: netstat
Sometimes the question is the other way round: is the service on your machine listening at all?
netstat shows that:
netstat -ano
According to Microsoft, -a lists all active TCP connections and the TCP and UDP ports the computer
is listening on, -n shows addresses and ports as numbers, and -o adds the process ID, which you
can match to the program in Task Manager. If your port is not in the list, no firewall rule will
help: the service is not running or is listening on a different port.
Keep servers in view: the Connections tile in Celerando
Celerando is a Windows app with a dashboard of tiles that you open over any program with Alt+Q. Besides tiles for programs and web apps, it has widget tiles, among them Connections: servers and web addresses in view, via RDP, TCP, HTTP/HTTPS or ping.
What the tile changes compared with a one-off command:
- The cause, not just True/False: the tile shows more than red or green. It names the cause: “refused”, “unknown name”, “no response” (the timeout from above), and for web addresses also “invalid certificate” or “login required”. Those are exactly the cases from the section above, without you having to interpret the output. When all is well, it shows the response time, or the HTTP status code (such as 200) for web addresses.
- Several targets at a glance: file server, remote desktop machine and intranet page sit as rows in one tile instead of three commands typed one after another.
- HTTPS including the certificate: for web addresses the tile also reports a certificate problem. A plain port test only sees that 443 answers.
- One click to the target: one click on an RDP target opens the remote desktop session, one click on a web address opens the page. TCP and ping targets are display only.
- Checks while the dashboard is open: when you open it, the tile checks its targets, then every 5 seconds, web addresses every 30 seconds. You set timeout and interval per tile under Checks.
The widget tiles, including Connections, countdown, Pomodoro, time tracking, QR code and text templates, are part of Free, free forever. Free allows up to 5 tiles on the dashboard, Free+ (free with email registration) 10, Pro (€36, one-time) unlimited; all editions are listed under Editions and prices.
To be clear: the tile is a status display for your workstation, not a monitoring system. While the dashboard is closed it checks nothing; it alerts nobody, and it does not replace network analysis. If you need to scan hundreds of ports or report outages to a team, that belongs in a monitoring tool.
Step by step: set up the Connections tile
- Download and install Celerando (Windows 10 build 19041 or later, or Windows 11). It installs into your user profile, with no admin rights and no account.
- Open the dashboard with Alt+Q.
- Right-click the heading of a tile group or an empty spot › Add widget › Connections.
- Enter your targets: right-click the tile › Edit › plus button (“Add connection”). In the dialog
give it a name and a Type: RDP (machine; without a port it uses 3389), TCP (server and
port), Web (address; without
http://in front, the tile useshttps://) or Ping (machine name). Repeat for each further target; one tile holds several targets. - The tile now shows one row per target: green with the response time (web: status code), yellow for a certificate or login issue, red with the cause. Before the first check, the dot is grey.
- One click on an RDP target opens the remote desktop session; one click on a web address opens the page.
You can place the programs you use to manage those servers next to it as tiles, and launch intranet pages as web app tiles; the guide Save a website to your desktop shows how.
Troubleshooting: what the answer tells you
| What you see | Likely cause | What helps |
|---|---|---|
TcpTestSucceeded : False, ping works | port refused or filtered | on the server, check with netstat -ano whether the service is listening; then the server’s firewall and anything in between |
TcpTestSucceeded : False, ping fails too | machine off, wrong address, or everything filtered | check the address; many servers do not answer ping, so also test a port you know is open |
| Ping fails, the port works | ping (ICMP) is blocked along the way, the service runs | nothing to fix; for reachability, the port is what counts |
| Name cannot be resolved | typo, wrong DNS server, or VPN not connected | check the name, connect the VPN, try the IP address |
| HTTPS target reports a certificate problem | certificate expired, wrong name, or internal certificate authority | have the server’s certificate checked; an open port alone does not mean the page loads cleanly. With an internal certificate authority, ask IT to install its root certificate as trusted in Windows rather than turning the warning off |
| Online checker says “closed”, it works on the LAN | port forwarding missing on the router, or your provider gives you no public address of your own | check the router’s port forwarding; that is a different question from testing from your PC |
telnet is not recognized | Telnet client not installed | use Test-NetConnection |
| Celerando: a tile is locked (“This tile is locked”) | Free allows up to 5 tiles, widget tiles count | move to Free+ (free with email registration, 10 tiles) or to Pro (€36, one-time, unlimited) |
Test-NetConnection or the tile: comparison
| Test-NetConnection | Celerando Connections tile | |
|---|---|---|
| Installation | included in Windows | app, no admin rights |
| Checks | TCP port, ping, route | RDP, TCP, HTTP/HTTPS, ping |
| Result | True/False plus details | response time (web: status code), or the cause: refused, unknown name, no response, invalid certificate, login required |
| Several targets | one command per target (or a script) | as rows in one tile |
| When it checks | each time you run it | while the dashboard is open: on opening, then every 5 s (web 30 s) |
| Afterwards | open the program yourself | one click opens RDP or the page |
| Scripts, automation | yes (-InformationLevel Quiet) | no |
| Cost | comes with Windows | included in Free |
For a quick one-off test and for scripts, Test-NetConnection is the right tool. If you need the same
servers every day, the tile saves the typing and tells you right away what is wrong.
Telnet also tests TCP ports, but has to be installed first and only shows whether a connection is
made. netstat answers the other question: which ports your own machine offers.
Frequently asked questions
How do I check if a port is open without Telnet?
In PowerShell with Test-NetConnection <server> -Port <number>. The command comes with Windows;
TcpTestSucceeded : True means the port accepted the connection.
Can I test a UDP port this way?
No. Test-NetConnection and Telnet test TCP, and the Celerando tile covers RDP, TCP, HTTP/HTTPS and
ping, but not UDP. UDP has no connection setup that the server would have to confirm. Whether a UDP
service answers is best shown by a real request from the matching program.
Which port does Remote Desktop use?
According to Microsoft, Remote Desktop listens on port 3389 by default. The port can be changed; you
then add it after the name when connecting, for example pc1:3390. Test-NetConnection checks the
default port with -CommonTCPPort RDP.
Why does the server not answer ping although the service is running?
Ping uses ICMP, not TCP. Many servers and firewalls block ping while the actual service is reachable.
So always test the port you care about. What the messages from ping mean and how a continuous ping
works is shown in the guide How to ping an IP address on Windows.
What is the difference from an online port checker?
Online checkers test your public address from the internet, for example after setting up port forwarding on your router. A test on your PC checks the path from your machine to a server, for example on the company network.
Does Celerando need the internet for this?
The tile connects to the addresses you enter and nothing else. Overall, Celerando goes online only for the downloads you choose (models, additional languages, the optional CUDA runtime), the update check, license activation including the query of occupied seats, a one-time installation ping on the very first launch, and addresses you enter yourself (web app tiles load the site’s icon, the connections tile checks your servers). If your servers are on the company network, the check stays there.
Which other widget tiles are there?
Translator, countdown, Pomodoro, time tracking, QR code and text templates. How Pomodoro and time tracking work together is shown in the guide Pomodoro timer for Windows.
Sources
As of November 1, 2026.
- Microsoft Learn: Test-NetConnection (NetTCPIP) (parameters
-Port,-CommonTCPPortwith HTTP, RDP, SMB, WINRM,-InformationLevelQuiet/Detailed, outputTcpTestSucceeded,PingSucceeded) - Microsoft Learn: telnet (syntax
telnet <host> [<port>], default port 23, client must be installed) - Microsoft Learn: netstat (parameters
-a,-n,-o) - Microsoft Learn: Change Remote Desktop listening port on Windows and Windows Server (default port 3389,
name:portformat)
More guides
- How to Ping an IP Address on Windows: Ping Test and Continuous PingRun a ping test in Command Prompt, start a continuous ping with ping -t, and learn what Request timed out and Destination host unreachable mean.
- Recent Files in Windows 11 and 10: Find, Hide and Clear ThemWhere Windows shows your recently opened files: File Explorer, Start, Jump Lists and Office. Plus how to hide or clear the list and keep files pinned.
- How to get the old right-click menu back in Windows 11Restore the full Windows 10 context menu in Windows 11: once with a shortcut, permanently with a registry entry or with a switch in Celerando.