How to Check if a Remote Server Has a Specific Port Open

[nayan]

You may need to verify that a remote server is listening on a specific port (for example, ZappySys Data Gateway on Port 5000). ZappySys Data Gateway is a tool for secure data access and integration—see official documentation for details. Here’s how to test this connectivity.

Step 1: Test Port Locally on the Remote Machine

First, verify the service is listening on the target port on the machine where it’s running:

1. Log in to the remote machine where the service is running

2. Open PowerShell

3. Run the command below, replacing 5000 with your actual port number:

Test-NetConnection -ComputerName 127.0.0.1 -Port 5000

4. If you see TcpTestSucceeded : True, the service is listening on that port

Step 2: Test Remote Connection from Another Machine

Now test if you can connect to the remote service from a different computer:

1. Log in to another PC from which you need to access the remote service

2. Open PowerShell (search for it in the Start menu)

3. Run the command below, replacing 192.168.50.246 with the remote server’s IP address and 5000 with the port:

Test-NetConnection -ComputerName 192.168.50.246 -Port 5000

4. If you see TcpTestSucceeded : True, the remote port is accessible and firewall rules are not blocking it

Successful connection example:

Failed connection example:

Step 3: If the Connection Fails—Create a Firewall Inbound Rule

If you cannot connect from the remote PC, the firewall is likely blocking inbound traffic. You’ll need to create an inbound firewall rule.

For example, to allow ZappySys Data Gateway traffic on Port 5000:

1. Create the firewall rule in the service settings:

2. Verify the inbound rule appears in Windows Firewall: