How to Ping an IP Address on Windows: Ping Test and Continuous Ping
Run a ping test in Command Prompt, start a continuous ping with ping -t, and learn what Request timed out and Destination host unreachable mean.
To ping an IP address on Windows, use Command Prompt: press Win+R, type cmd,
press Enter, then type ping followed by the address:
ping 192.168.1.1
A name works too, such as ping server01 or ping example.com. Windows sends four requests and
prints a Reply from … line with the time in milliseconds for each answer. If lines with bytes= and
a time (time=3ms or time<1ms) come back, the target is reachable at the IP level. A continuous
ping that keeps going until you stop it starts with ping -t.
According to Microsoft, ping verifies IP-level connectivity to another computer by sending ICMP echo
request messages and shows the replies along with round-trip times. Microsoft calls it the primary
command for troubleshooting connectivity, reachability and name resolution. It has limits, though,
and you should know them before you read “no reply” as “the server is down”.
What ping can and cannot tell you
- Ping is a snapshot. Without
-tit sends four requests and stops. If the server goes down five minutes later, you won’t notice. - No reply does not mean “off”. Ping uses ICMP, not TCP. Many servers and firewalls don’t let ping through even though the actual service, such as a website or Remote Desktop, is running. To check a specific port, see How to check if a port is open on Windows.
- One window per target. To keep an eye on your router, file server and printer at once, you need three Command Prompt windows running three continuous pings.
- You have to read the output yourself. “Request timed out”, “Destination host unreachable” and “Ping request could not find host” mean different things. The troubleshooting table below explains each one.
Ping test in Command Prompt, step by step
- Press Win+R, type
cmd, press Enter. - Type
pingand the target, for exampleping 192.168.1.1for a router orping server01for a machine on the company network. - Read the output. A successful ping looks like this:
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms
time is the round-trip time in milliseconds. Under Ping statistics you see sent, received and lost
packets, followed by the shortest, longest and average time. Per Microsoft, 32 bytes is the default data size and four is the default number of requests.
The most useful options
| Option | What it does (per Microsoft) |
|---|---|
-t | pings until you stop it (continuous ping) |
-n 10 | sends 10 requests instead of 4 |
-w 1000 | waits at most 1000 ms for each reply (default: 4000 ms) |
-l 1000 | sends 1000 bytes of data instead of 32 (maximum 65,500) |
-a | resolves the IP address to a host name, if possible |
-4 / -6 | forces IPv4 or IPv6; only needed when you give a name |
You can combine them: ping -n 10 -l 1000 server01 sends ten requests of 1000 bytes each. Microsoft
writes the options with a slash (/n); a hyphen works the same way.
Continuous ping with ping -t
ping -t 192.168.1.1
The command runs until you stop it. According to Microsoft, Ctrl+Break shows the statistics and keeps pinging; Ctrl+C stops it. A continuous ping is useful in three situations:
- Finding a flaky connection: an occasional
Request timed outor wildly varying times point to a problem along the way, for example on Wi-Fi. - Waiting for a restart: you reboot a server and see the moment it answers again.
- Checking a cable or switch port: while the ping runs, you replug and see right away whether the replies stop.
In PowerShell the counterpart is Test-Connection. In current PowerShell 7,
Test-Connection server01 -Repeat pings continuously; Windows PowerShell 5.1, the version built into
Windows, has no -Repeat according to Microsoft. There, just use ping -t, which works in both
consoles.
Keep several servers in view: the Connections tile in Celerando
A continuous ping answers one question for one target while its window is open. If you need the same machines every day, say a file server, a Remote Desktop PC and an intranet page, a display that checks them all together helps.
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.
- The cause, not guesswork: the tile shows more than red or green. On failure it gives a reason,
depending on the type, such as “no response”, “unknown name”, “refused” (TCP, RDP) or “invalid
certificate” (web). For ping it only tells “no response”, “unknown name” and otherwise a general
“offline”; messages like “Destination host unreachable” appear only in
ping. - Several targets in one tile: instead of three windows with three continuous pings, the targets sit as rows one below the other.
- More than ping: if a server doesn’t answer ping, check the port that matters (TCP), Remote Desktop (RDP) or the website (HTTP/HTTPS) instead.
- One click to the target: for RDP and web targets, one click opens the Remote Desktop session or the page.
- Checks while the dashboard is open, at an interval you set per tile. The timeout is set there
too: by default the tile waits 2.5 seconds for a reply,
pingwaits 4 seconds.
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, and it alerts nobody. If you need to record outages over days or notify a team, you need a monitoring tool.
Set up the 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.
- Right-click the tile › Edit › plus button (“Add connection”). Enter a name, pick the Type and give the target: for Ping a host name or IP address (no port), for TCP server and port, for RDP the machine (without a port it uses 3389), for Web the address.
- Repeat for each further target. The tile shows one row per target: green with the response time, red with the cause.
Troubleshooting: what the messages mean
| Message | What it means | What helps |
|---|---|---|
Request timed out. | No reply arrived within the wait time (4 seconds by default). The target is off, the address is wrong, or a firewall drops ping | Check the address; test the service you care about by its port. If the port answers, something just blocks ping |
Reply from 192.168.1.20: Destination host unreachable. | The reply comes not from the target but from your PC or a router on the way: it can’t find the target on the network. Windows still counts these lines as “Received” in the statistics | Is the device on and on the same network? For addresses on another network: is the VPN connected? |
Destination net unreachable. | A router knows no route to the target’s network | Check the VPN and network connection, otherwise ask IT |
Ping request could not find host server01. Please check the name and try again. | The name can’t be resolved to an address | Check for typos, connect the VPN, try pinging the IP address. If the IP works but the name doesn’t, Microsoft says you probably have a name resolution problem |
General failure. or PING: transmit failed. | The request usually never left your PC | Check the network cable, Wi-Fi and network adapter; briefly disconnect VPN or security software to test |
Replies come back, but Lost is above 0 | Some packets get lost on the way | Watch longer with ping -t; on Wi-Fi, move closer to the router or test over a cable |
| Replies with high or wildly varying times | The line is busy or the wireless signal is weak | Pause downloads, compare over a cable |
Let your own PC answer ping
If your own Windows PC doesn’t answer ping on the network, the Windows Firewall often isn’t letting incoming echo requests through. Microsoft gives a firewall rule for this, which you add in a Command Prompt as administrator. Here it has two restrictions at the end, so that it only applies on private and domain networks and only to devices on your own subnet:
netsh advfirewall firewall add rule name="ICMP Allow incoming V4 echo request" protocol=icmpv4:8,any dir=in action=allow profile=private,domain remoteip=localsubnet
Without profile= and remoteip=, as in Microsoft’s example, the rule applies to every network
profile, including public Wi-Fi. It covers IPv4 only. To remove it again, run
netsh advfirewall firewall delete rule name="ICMP Allow incoming V4 echo request". On company
networks, IT usually manages this centrally.
Ping or tile: the comparison
ping in Command Prompt | Celerando Connections tile | |
|---|---|---|
| Installation | built into Windows | app, no admin rights |
| Checks | ping (ICMP) | ping, TCP, RDP, HTTP/HTTPS |
| Result | text output, you interpret it | response time or a reason: no response, unknown name, refused (TCP/RDP), invalid certificate (web); for ping otherwise “offline” |
| Several targets | one window per continuous ping | rows in one tile |
| Duration | 4 requests, with -t until stopped | while the dashboard is open |
| Afterwards | open the program yourself | for RDP and web targets, one click opens the session or the page |
| Scripts | yes | no |
| Cost | comes with Windows | included in Free |
For a quick test or a script, ping is exactly right. If you check the same machines every day, the
tile saves the typing and tells you right away where it’s stuck. Test-Connection in PowerShell
returns the same information as ping, but as an object that scripts can work with; with -Quiet it
returns just True or False.
Frequently asked questions
How do I ping an IP address?
Open Command Prompt (Win+R, cmd) and type ping with the address, such as
ping 8.8.8.8. If you get lines like Reply from 8.8.8.8: bytes=32 time=12ms, the address is
reachable.
How do I stop a continuous ping?
With Ctrl+C. According to Microsoft, Ctrl+Break shows the statistics along the way without ending the ping.
How many times does Windows ping without -t?
Four times. Use -n to set the count: ping -n 20 server01 sends twenty requests.
What does TTL in the reply mean?
TTL stands for Time To Live, a value in the IP header (Microsoft mentions it under the -i option). For
the question “reachable or not” you can ignore it.
Is a ping test the same as a speed test?
No. Online “ping tests” usually measure the latency of your internet connection, often together with
its speed. The ping command checks whether one specific target answers and how long that takes,
whether it’s on the internet or on your own network.
Why does ping work, but the website or Remote Desktop doesn’t?
Ping only checks whether the machine answers on the network. Whether the service on it is running is what a port test shows, see How to check if a port is open on Windows.
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 16, 2026.
- Microsoft Learn: ping (ICMP echo requests, options
/t,/nwith default 4,/lwith default 32 and maximum 65,500,/wwith default 4000 ms,/a,/4,/6; statistics with Ctrl+Break, stop with Ctrl+C; note on name resolution) - Microsoft Learn: Test-Connection (PowerShell 7:
-Repeat,-Count,-Quiet) and the Windows PowerShell 5.1 version (no-Repeat) - Microsoft Learn: Use netsh advfirewall firewall context (rule for incoming ICMPv4 echo requests, elevated command prompt); the
profileandremoteip=localsubnetrestrictions are listed in the help ofnetsh advfirewall firewall add rule ? - The message texts come from the English Windows resource of
ping.exe(Windows 11,C:\Windows\System32\en-US\ping.exe.mui).
More guides
- 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.
- How to organize desktop icons in Windows and keep them tidySort, arrange and hide desktop icons in Windows 10 and 11, move files off the desktop, and when a tile dashboard works better than the desktop.