As is well known, the tool ping can be used to test the access to a certain network device and its response time. Not all devices will respond to a ping, but they may respond to a particular Tcp-Port if a particular network service is provided through it. Windows PowerShell allows you to test a specific port using Windows board tools. The psping tool can also measure the response time to a specific port.
Aim of this article
Using commands in the command prompt to test whether certain Internet addresses or network devices have a certain network port active
Reading time: approx. 6 Minutes
Basic network knowledge and a Windows computer
Ping is a command used to send a test packet over the network, the devices usually respond to it and send back a response packet. Responsible for the response here is not a specific service, but a part of the network stack on the device. The test on a specific port is different, here it is tested whether the remote station on the port accepts a packet, i.e. whether the TCP connection setup to the port works. The connection is established directly to the service that uses the port. By the test on a certain port, it can be tested whether a certain service answers on the device.
To test a device for their open ports, see: Portscan commands.
Test-Netconnection
PowerShell’s built-in Test-NetConnection command can be used to test the connection on a specific port.
Windows PowerShell is a fixed component of Windows,therefore a port check can be done via PowerShell without additional software or features.
The command returns for TcpTestSucceeded: True if the port is reachable.
Command prompt
Originally, the telnet command was very often misused in the command prompt to test a specific port. Telnet was a fixed part of the operating system in earlier Windows versions, but in Windows 10 / 11 the telnet command is no longer activated by default, so the command must be added beforehand via Programs and Features:
The call is then made in the command prompt: telnet IP/DNS Port
telnet 192.168.1.5 443
If the port is open, usually only a “_” flashes in the output:
Sysinternals
The psping command can also be used to measure the response time of individual services or ports, as well as the bandwidth:
Ping on a port
psping is included in the pstools from Sysinternals (Microsoft),
Measure bandwidth
psping -b -l 8k -n 10000 www.libe.net:80
Download
Download see: https://docs.microsoft.com/de-at/sysinternals/downloads/psping
Check UDP ports
UDP ports can be tested most easily with the tool “portqry”:
portqry -n 192.168.1.2 -p udp -o 161
If “UDP port ???:FILTERED” is output, the port cannot be reached.
FAQ
Strictly speaking, a ping to a specific TCP port is not a ICMP-Ping, but a TCP connection attempt. Tools like test-netconnection, telnet or psping try to establish a TCP connection to a specific service and thus test a network connection on TCP/IP level.
What does a high ping mean in games?
This is the only solution that works for VPNs with the client machine being Windows Vista or Windows 7, as other listed answers simply do not function. This answer was previously deleted and should not have been, as this is the only solution for a real-world common case. Since there is no appeal available for the delete, I am reposting it to save others the frustration I had with trying to use the other answers.
The example below finds which IPs on the VPN that have VNC/port 5900 open with the client running on Windows 7.
A short Python (v2.6.6) script to scan a given list of IPs and Ports:
Results looked like:
The four variables at the top would need to be changed to be appropriate to whatever timeout, network, hosts, and ports that are needed. 5.0 seconds on my VPN seemed to be enough to work properly consistently, less didn’t (always) give accurate results. On my local network, 0.5 was more than enough.
A ping is a tool and command used to troubleshoot network and system-related problems. The ping command normally uses the ICMP protocol and make checks if the remote system is up or down without a TCP or UDP. The ping port is a term used to check a remote port which can be TCP or UDP if it is open and accessible. There are different tools that can be used to ping a TCP or UDP port. Telnet, nmap, putty, netcat,psping are some of them.
- The application can not connect database service.
- If the firewall has configured properly to allow or deny specific ports.
- Check if the remote SNMP service is running properly.
- Before attacking the remote port if the port is up and responding properly.
Ping Specific Port with telnet Command
The most popular and basic tool to ping a remote port is the telnet command. Telnet is a tool and protocol created to connect remote systems via the command line. Telnet work from the command line and provides simple access to the remote telnet server. Telnet command uses the TCP protocol and first tries to connect remote port which is very useful to check remote port.
By default, telnet is not installed for both Linux and Windows systems. In Linux systems like Ubuntu, Debian, Mint, Kali you can install the telnet command like below.
$ sudo apt install telnet
Alternatively, you can use 3rd party tools like Putty for telnet command but it is not practical as expected. Syntax of the telnet command to ping the remote port is like below. The telnet command only uses the TCP protocol which is the most popular transmission protocol. So only TCP ports can be pinged with the telnet command which can not be used for the UDP ports.
telnet IP PORT
telnet DOMAIN PORT
- IP or DOMAIN is used to specify the remote system.
- PORT is the remote system port number which is a number from 9 to 65000.
Let’s ping the remote HTTP port with the telnet command by providing the port number as 80. We will ping the google.com TCP port number 80 like below.
The output will be like below where the telnet will try to connect remote system port number 80 and when the connection is established e will see the message “Connected to google.com.”
Ping Specified Port with telnet
Alternatively, we can try to ping a remote port with the IP address. We will just change the domain name with the IP address below.
$ telnet 172.217.18.110 80
Ping Specific Port with nc (netcat) Command
The nc or with its well-known name netcat is a tool used by security professionals for remote connectivity and management. Similar to the telnet command nc command can be used to ping specific port numbers for a remote system.
The nc command is provided by the Linux distributions like Ubuntu, Debian, Mint, Kali and can be installed like below.
$ sudo apt install netcat
For Windows operating systems the nc command and executable can be downloaded from alternative locations where one of them is https://github.com/diegocr/netcat .
The syntax of the nc command is very similar to the telnet command. But the difference is -v and -z parameters should be specified. The -v parameter is used for verbose output in order to see the log or status information like connected or not connected. The -z parameter is used for scan mode which will check or scan the specified remote port.
nc -vz DOMAIN PORT
nc -vz IP PORT
- The DOMAIN is the remote system domain name.
- The IP is the remote system IP address.
- The PORT is the remote system port number we want to ping.
We can see that the connection is succeeded which means the remote port number 80 responds to ping requests. We can also use the IP address for the remote system.
$ nc -vz 172.217.18.110 80
$ nc -vz goole.com 89
nc: connect to goole.com port 89 (tcp) failed: Connection refused
As we can see from the result we will get the “Connection refused” message which means the remote port does not respond to ping.
Ping Specific Port with nmap
The nmap is a security tool used to scan remote systems ports and services. The nmap can be also used to ping a specific port. Nmap can be installed for the Linux distributions like Ubuntu, Debian, Mint, Kali like below.
$ sudo apt install nmap
For Windows operating systems use the official nmap site Windows download section like below.
The syntax of the nmap command for the port ping is like below.
nmap -p PORT_RANGE TARGET
- PORT_RANGE is the remote port number or protocol name. The PORT_RANGE can be also a range of port numbers too.
- TARGET is a domain name or IP address. Also the target can be an IP range too which includes multiple sequencial IP addresses.
Let’s make an example with the nmap to ping remote port. We will provide the port number with the -p parameter which will be 80 and the remote system is google.com.
$ nmap -p 80 google.com
The nmap is the fastest tool to ping a specified remote port. The command will be executed in 2 seconds and detailed output about the remote port will be provided like below. The line “80/tcp open http” simply expresses that the remote port number 80 responds to pings.
Starting Nmap 7.80 ( https://nmap.org ) at 2020-11-11 18:27 PST
Nmap scan report for google.com (172.217.18.110)
Host is up (0.036s latency).
Other addresses for google.com (not scanned): 2a00:1450:4001:809::200e
rDNS record for 172.217.18.110: zrh04s05-in-f110.1e100.net
PORT STATE SERVICE
80/tcp open http
Nmap done: 1 IP address (1 host up) scanned in 0.28 seconds
Ping Specified Port with nmap
Alternatively, we can specify the IP address of the remote system we want to ping port.
$ nmap -p 80 172.217.18.110
$ nmap -p 80-90 google.com
The output will be like below where the open ports will be listed with the STATE open.
Starting Nmap 7.80 ( https://nmap.org ) at 2020-11-11 18:32 PST
Nmap scan report for google.com (172.217.18.110)
Host is up (0.039s latency).
Other addresses for google.com (not scanned): 2a00:1450:4001:809::200e
rDNS record for 172.217.18.110: fra16s42-in-f14.1e100.net
PORT STATE SERVICE
80/tcp open http
81/tcp filtered hosts2-ns
82/tcp filtered xfer
83/tcp filtered mit-ml-dev
84/tcp filtered ctf
85/tcp filtered mit-ml-dev
86/tcp filtered mfcobol
87/tcp filtered priv-term-l
88/tcp filtered kerberos-sec
89/tcp filtered su-mit-tg
90/tcp filtered dnsix
Ping Multiple Specified Ports with nmap
Ping Specific Port with Test-Connection In PowerShell
The Windows operating system provides the strong command-line interface named PowerShell with its recent versions. PowerShell provides a lot of useful commands like Test-NetConnection . The Test-NetConnection can be used to ping specified remote ports easily and provides detailed information. The Test-NetConnection is the preferred tool over the telnet command for Windows systems. The Test-NetConnection command is by default with PowerShell and Windows so there is no need for an extra installation process.
The syntax of the Test-NetConnection command is like below.
Test-NetConnection TARGET -p PORT
- TARGET is an IP address or domain name to port ping.
- PORT is the remote system port number.
The output of the ping remote port with the Test-NetConnection command will be like below. We can see that remote system ComputerName, RemoteAddress, RemotePort, InterfaceAlias, SourceAddress, TcpTectSucceeded information is provided.
ComputerName : google.com
RemoteAddress : 172.217.18.110
RemotePort : 80
InterfaceAlias : Ethernet0
SourceAddress : 192.168.142.130
TcpTestSucceeded : True
Ping Port with PowerShell Test-NetConnection
Let’s make another test for port number 89 for google.com.
The output is like below which means the ping port is failed. For failed ping port operations extra information like PingRelyDetails (RTT), TcpTestSucceeded is provided.
WARNING: TCP connect to (172.217.18.110 : 89) failed
ComputerName : google.com
RemoteAddress : 172.217.18.110
RemotePort : 89
InterfaceAlias : Ethernet0
SourceAddress : 192.168.142.130
PingSucceeded : True
PingReplyDetails (RTT) : 46 ms
TcpTestSucceeded : False
Ping Port with PaPing Tool
The PaPing tool is a 3rd party tool created to ping remote specified port. The PaPing project is open source and located in Google Code.
Ping Port with curl Command
$ curl 192.168.136.136:80
If the remote port is open some response like a warning, error, etc is returned by the remote port service.
Ping Port with curl Command
Ping Port with psping Command
Windows Sysinternals is used to debug, troubleshoot the Windows operating system. The psping is a Windows Sysinternals tool that can be used to ping a port. The syntax of the psping tool is like below.
The ping is a term and command-line tool used to check remote system network connectivity. It is one of the most popular tools for network diagnostics. By default, the usage of the ping command does not require any port number and will work with just a target IP address or domain name. But you may ask what port number is used by the ping command.
The TCP and UDP protocols are very popular where they can provide multiple port numbers to provide different services over the network. The ping command can be related to these TCP and UDP protocols but it does not use TCP or UDP. This may be even asked you in an interview or certificate exam or class exam. The ping command uses the ICMP protocol. The ping is an old method and tool described in the RFC792 and this standard does not provide any port number for the ping.
Ping and ICMP Protocol
The ping tool uses the ICMP protocol which is different from the TCP and UDP protocol where it is tightly integrated with the IP protocol. The ICMP is a layer 3 protocol that is transmitted with the IP packets even the IP is also a layer 3 protocol too. The ICMP is created to support the IP protocol.
Ping Uses ICMP Type 8 and Type 0
$ ping 8.8.8.8
Ping ICMP Request Packet Details
Ping ICMP Reply Packet Details
Is Port 7 Used For Ping ICMP?
Можно ли вы пинговать конкретный порт машины, и если да, то можете ли вы привести пример?
Ищу что-то вроде ping ip address portNum.
Ответ 1
Нельзя пинговать порты, так как Ping использует ICMP, который не имеет понятия о портах. Порты относятся к протоколам транспортного уровня, таким как TCP и UDP. Однако вы можете использовать nmap, чтобы узнать, открыты ли порты или нет.
nmap -p 80 example.com
Как уже упоминалось, nmap – это больше, чем просто пинг-для-портов. Это лучший друг аудиторов и хакеров, который предлагает массу интересных опций. Проверьте в документации все возможные флаги.
Ответ 2
Откройте сеанс telnet для определенного порта, например:
Ответ 3
Если вы используете Windows с PowerShell v4 или новее, вы можете использовать модуль PowerShell test-netconnection:
Ответ 4
Можно использовать PaPing:
Connected to 209.85.225.147: time=24.00ms protocol=TCP port=80
Connected to 209.85.225.147: time=25.00ms protocol=TCP port=80
Attempted = 4, Connected = 4, Failed = 0 (0.00%)
Approximate connection times:
Minimum = 24.00ms, Maximum = 25.00ms, Average = 24.25ms
Ответ 6
Попробуйте curl команду, например:
$ curl host:port
Вышеупомянутая команда вернет Fail при ненулевых кодах статуса выхода. В некоторых конкретных случаях, таких как пустой или искаженный ответ.
Ответ 7
Нет, нельзя, потому что ping использует протокол ICMP , в котором даже нет понятия портов.
Ответ 8
Я нашел более простое решение с помощью PsPing:
Это часть Windows Sysinternals .
PsPing реализует функции Ping, TCP ping, измерение задержки и пропускной способности.
Ответ 9
В Linux вы можете использовать hping, он использует TCP, а не ICMP.
Ответ 10
Ping очень специфичен, но если вы хотите проверить, открыт ли порт или нет, и используете ли вы окно Windows, тогда PortQry – ваш друг.
Я использовал его только для тестирования контроллеров домена на предмет проблем с подключением, он сработал, поэтому должен сработать и у вас.
Ответ 11
Вот консольное приложение .NET:
string addressArgument = null, portArgument = null;
System.Net.Sockets.TcpClient tcpClient = null;
portNumber = Int32.Parse(portArgument);
tcpClient = new System.Net.Sockets.TcpClient();
var endPoint = new System.Net.IPEndPoint(address, portNumber);
if (tcpClient != null)
Ответ 12
Пример ниже находит, какие IP на VPN имеют открытый VNC/порт 5900 с клиентом, работающим на Windows 7.
Короткий скрипт Python (v2.6.6) для сканирования заданного списка IP и портов:
from socket import *
fTimeOutSec = 5.0
sNetworkAddress = ‘192.168.1’
aiHostAddresses = range(1,255)
for h in aiHostAddresses:
for p in aiPorts:
s = socket(AF_INET, SOCK_STREAM)
address = (‘%s.%d’ % (sNetworkAddress, h))
result = s.connect_ex((address,p))
if ( 0 == result ):
print “%s:%d – OPEN” % (address,p)
elif ( 10035 == result ):
# вышло время запроса – выход
print “%s:%d – closed (%d)” % (address,p,result)
print “Сканирование завершено.”
192.168.1.1:5900 – closed (10061)
192.168.1.7:5900 – closed (10061)
192.168.1.170:5900 – OPEN
192.168.1.170:5900 – closed (10061)
Четыре переменные в верхней части нужно будет изменить, чтобы они соответствовали таймауту сети, хостам и портам, которые необходимы. 5,0 секунд, на моей VPN, казалось, будет достаточно для стабильной работы, но не всегда давало точные результаты. В моей локальной сети 0,5 было более чем достаточно.
Ответ 13
В оболочке Bash вы можете использовать pseudo-device file TCP , например:
Вот версия, реализующая тайм-аут в 1 секунду:
Ответ 14
Если вы используете операционную систему * nix, попробуйте установить и использовать «zenmap», это графический интерфейс для nmap и несколько полезных профилей сканирования, которые очень помогают новому пользователю.
In this post, we will discuss how you can use various tools to send a ping request to check if a target port on a specific host is alive.
Ping is one of the most fundamental tools when it comes to network troubleshooting. It allows you to quickly test whether a given service/port is responding or not. Due the lightweight nature of ICMP packets, it allows ping to quickly fetch useful information about a given system without sending a series of packets that would otherwise overwhelm the host (in some cases).
Although pinging an entire host can be useful for checking if a given host is up, it does not offer much information about if a target port is up.
Method 1 – Use Telnet
You are probably familiar with telnet. Also known as Terminal or Network, Telnet is a command-line utility that allows you perform interactive network communication using the TELNET protocol.
An telnet tutorial is coming up soo. Stay tuned for that.
To ping a specific port using telnet, use the command syntax as:
The telnet command is available in both Windows and Unix systems. However, you may need to enable Telnet in Windows.
To learn how do that, check the link below:
On macOS, use brew to install Telnet:
brew install telnet
On Debian and Debian-Based distributions, install telnet:
sudo apt-get install telnet
The example below shows how to use telnet to check if Nginx Server is running.
telnet 67.205.166.236 80
If the service is running, telnet will connect and return an output as:
Method 2 – Using Nmap
Start by installing nmap:
sudo apt-get install nmap
brew install nmap
sudo yum install nmap
Once installed, check if a port is up by running the command:
sudo nmap -p 80 67.205.166.236
Nmap will return detailed information including the latency, port number, associated service and its state. An exmaple output is as shown:
Starting Nmap 7.93 ( https://nmap.org ) at 2022-10-02 10:49 EAT
Nmap scan report for 67.205.166.236
Host is up (0.28s latency).
PORT STATE SERVICE
80/tcp open http
Nmap done: 1 IP address (1 host up) scanned in 0.65 seconds
Method 3 – Using Netcat
To ping a port using netcat, run the command:
We can see that the connection to the target address and port is successful. This indicates the port/service is up.
Method 3 – Using cURL
We obviously cannot forget to mention cURL in this list. The command syntax is as shown:
The command should “Connected” if the port/service is up.
Method 4 – Using Windows PowerShell
In Windows, you can use the Test-NetConnection cmdlet to test if a port is up and running. The command syntax is as shown:
Test-NetConnection 67.205.166.236 -p 80
The command should return details about the target host and the connection status.
ComputerName : 67.205.166.236
RemoteAddress : 67.205.166.236
RemotePort : 80
InterfaceAlias : Ethernet
SourceAddress : 192.168.1.101
TcpTestSucceeded : True
Method 5 – Using PsPing Utility
In Windows, you can also use the PsPing utility which is part of Windows SysInternals tools. Download the tool in the resource below:
You can then use the command synax below to ping a specific port:
The command should send ping request to the target address and port and return the output as shown:
The above port is up.
Conclusion
In this post, we explored various methods and tools you can use to ping a specific port in both Windows and Unix based systems.
Thanks for reading and catch you in the next one!!
If you enjoy our content, please consider buying us a coffee to support our work:
One of the things I do the most when troubleshooting deployments of services exposing data to the internet is pinging the IP and port where the service is supposed to be alive. In this tutorial, I will show you how to ping IP and port on Linux and Windows.
Often it’s enough to just ping an IP to validate that you got “life” on the server. However if you like me often got many services running on one server (often when using Docker), I need to ping the specific port number on the server. One of the Kubernetes clusters I manage is running more than 100 services and here I use it a lot.
In this article/reference post, I will show you how to ping IP and port on your Windows or Linux machine using different commands in the terminal (CLI).
Ping IP and port using Telnet
This is my favorite when working on both Windows and Linux. I also think that it’s the easiest one to use and it’s called Telnet. You can with a simple command using Telnet ping IP and port on the remote server you would like to check.
Telnet – WikipediaWikimedia Foundation, Inc.Contributors to Wikimedia projects
If you want to, you can also use a domain instead of the IP. A domain is often easier for humans to remember instead of numbers to multiple different servers locally or externally.
Below are the commands to ping IP and port on a server using Telnet:
As I mentioned above, you can use Telnet on both Windows and Linux computers/servers which makes it a great choice for most sys-ops.
On most computers, telnet is not installed by default. If you get the annoying error “telnet: command not found”, you have to install Telnet on the machine using the commands below:
Install Telnet on Linux
If you are working on a Linux Server or Desktop, you can use the below command to install Telnet on that machine:
Install Telnet on Windows
- Click on Start.
- Select Control Panel.
- Choose Programs and Features.
- Click Turn Windows features on or off.
- Select the Telnet Client option.
- Click OK.A dialog box appears to confirm installation when it’s done. The telnet command should now be available in your Command Prompt. Remember to restart your CMD window.
Ping IP and port with Telnet example
Let’s check out how Telnet works. This website is running at IP: 172.67.161.26 – this is the public IP address of the website to which the domain is mapped to.
By default, all requests are redirected to HTTPS (port 443) if a request is made at port 80. This means that the server accepts connections on port 80 too – let’s try and ping both ports:
That went well. We got connected and could see that the server is responding on both ports. This simply means that the service on the port is up and running.
Ping IP and port using Nmap
Another well-used tool is Nmap. In Nmap, you can ping a port by using the “-p” option including the IP or domain you would like to scan.
Nmap: the Network Mapper – Free Security ScannerNmap Free Security Scanner, Port Scanner, & Network Exploration Tool. Download open source software for Linux, Windows, UNIX, FreeBSD, etc.Free Security Scanner
A heads up – be aware of legal issues!
“When used properly, Nmap helps protect your network from invaders. But when used improperly, Nmap can (in rare cases) get you sued, fired, expelled, jailed, or banned by your ISP.” – Nmap website.
If you get an error telling you that Nmap is not available on your computer/server, you would have to install it.
Install Nmap on Linux
To install Nmap on your Linux machine, you can use the below command:
Install Nmap on Windows
Not as simple as Linux, but it’s still easy to use the official installer from Nmap’s website. Go to this page: Download Nmap and look under the Windows Binaries for the latest available installer file.
Once the installer has completed installing, you are now ready to use Nmap on your Windows computer.
Well, once again the port is returned as open on the server. This means that there is a service accepting data at port 443, which was just verified by Nmap.
Ping IP and port using PowerShell
Normally when I’m not on my own machines, which means I’m working on production servers not related to my own business/platform and it’s a Windows Server Environment, I always use PowerShell to ping IP and port.
A great thing about PowerShell is that you can use the methods in scripts running automated stuff in the background or during the setup of service or multiple services. A great thing if deploying with PowerShell would be to check if the ports were active after deployment and return a status to the terminal.
Below is an example of what this would look like on a local network:
In the test above you can see that the TCP call to my gateway at home succeeded at port 80. If you can’t get through to the service you will status False in TcpTestSucceeded.
Summary
In this quick article on how to ping IP and port using different tools on Windows or Linux machines, we learned how we can use the terminal to check if a given port is open and accepting requests.
If you got any issues, questions, or suggestions, please let me know in the comments below. Happy pinging!
While ping is one of the most basic command utilities to troubleshoot networking issues, it only sends ICMP packages (belonging to the IP layer) and ports (belonging to the Transport layer) making it impossible to ping on specific ports!
So what’s the solution? Well, I’m going to use other utilities that have the same effect as the ping command with the ability to specify ports!
- nmap
- netcat
So let’s get started with the nmap utility.
Ping UDP using nmap
The nmap utility is mainly used for security auditing as it provides real-time data, a list of live hosts, and a lot more but can also be used to do a UDP ping.
But it requires manual installation and if you’re on a Debian-based distro, you can use the given command to install nmap:
For example, I’ve used UDP port 161 of the host at itsfoss.com:
sudo nmap -sU -p 161 itsfoss.com
Now, let me break down the used options with nmap:
- -sU was used to force nmap to scan for UDP ports
- -p option was used to mention specific ports or you can also use a range of ports here
Ping UDP using netcat
The netcat utility covers everything that comes under TCP and UDP which fits perfectly for our use case.
For example, I’ll be pinging itsfoss.com at UDP port 161 to check for listening ports only:
- -v was used to produce verbose output
- -u uses UDP instead of TCP (the default behavior)
- -z scans for listening ports only
And that should get your job done. Have more ideas? I would love to hear from you.
Final Words
This was my take on how to perform UDP ping with two different utilities so you can choose what suits your workflow.
And if you have any queries, feel free to ping them in the comments!
