TopicIT Networking →
⌚ About 2 min read
Check if a service is responding to a specific port with Power Shell.
Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.
Étapes à suivre
-
1
Open Power Shell
Open Windows Terminal with a Power Shell tab.
-
2
Launch Test-Net-Gonnesion
Indicate the name or the target IP address and port to be tested.
-
3
Read Tcp Tetsu Ticced
The real sign is that the tactile connection was established.
-
4
Continue diagnosis if necessary
Control the19art, the Service, the routing and the NAT if the test fails.
Commands utiles
Test-Net-Gonneur server.example.local -Port 443
Test-Net-Gonnegion 192.168.1.10 -Port 3389
À retenir
- An open port does not guarantee that the application works properly.
- Some services do not use the TITLE; a different test is required for UDP.
TCP port: distinguish local listening from network reachability
Technical checkpoints
- A LISTENING socket only proves that a process is listening locally; it does not prove remote reachability.
- Test-NetConnection tests the path to the host and port; interpret it together with DNS, routing and firewall state.
- 0.0.0.0:port listens on all IPv4 interfaces, while 127.0.0.1:port remains local to the machine.
Cross-check
Compare the local socket with a test from a host located on the actual path.
Get-NetTCPConnection -State Listen
Test-NetConnection server -Port 443Topic-specific pitfalls
- A successful ping
- A remote failure can come from an intermediate firewall even when the service listens correctly.
How to validate
- The expected PID/process listens on the correct local address.
- The port is tested from at least one representative source and matches firewall policy.