How to See All IP Addresses on Your Network in Windows 10

Trying to work out which address belongs to the printer, or what that unfamiliar gadget on the Wi-Fi is? Windows 10 has no single screen that lists everything. The quickest complete route is to ping every address in your range, then read the neighbor table with Get-NetNeighbor in PowerShell (or arp -a in Command Prompt). Your router’s client list is the cross-check, because it knows devices your PC never talks to.

Why no single Windows list shows every device

Your PC keeps a short list of devices it has exchanged traffic with recently. In IPv4 this list is called the ARP cache (Microsoft’s PowerShell documentation calls it the neighbor cache). It pairs each IP address with a MAC address, the hardware ID of a network adapter. A smart plug that has never sent anything to your PC is not in that list, so a bare arp -a usually shows only the router and a handful of devices.

Three sources together give you the full picture:

Source	What it knows	What it misses
Ping sweep (sending one ping to every address)	Which addresses answer right now	Devices whose firewall ignores pings
ARP or neighbor cache on your PC	IP and MAC address of everything that answered, even devices that ignore pings but still reply at the network layer	Devices on another network segment, such as a guest Wi-Fi
Router client list	Names, MAC addresses, often Wi-Fi or wired, every device the router handed an address to	Devices with a manually set address, on some routers; can also show devices that left hours ago

The commands are the same on Windows 11. Windows 10 itself reached end of support on October 14, 2025; Microsoft says PCs enrolled in consumer Extended Security Updates stay protected until October 12, 2027 (see Microsoft’s Windows 10 end of support page).

Work out your network range first

Every device on a home network shares the first part of its address with your PC. You need that shared part before you can scan anything.

1. Press Windows + R, type cmd and press Enter.
2. Type ipconfig and press Enter.
3. Find the adapter you are connected with (Wireless LAN adapter Wi-Fi or Ethernet adapter Ethernet) and note three lines: IPv4 Address, Subnet Mask and Default Gateway.

If you only need your own PC’s address, the steps to check your IP address on Windows 10 are shorter. Here you need the mask, because it decides how many addresses to scan:

Subnet Mask shown	Example IPv4 Address	Addresses to scan
255.255.255.0 (the usual home setting)	192.168.1.23	192.168.1.1 to 192.168.1.254
255.255.254.0	192.168.0.40	192.168.0.1 to 192.168.1.254 (two blocks of 254)
255.255.0.0	10.0.5.12	Over 65,000 addresses; use the router list or a scanner instead of a ping loop

Worked example: a laptop shows IPv4 Address 192.168.0.40, Subnet Mask 255.255.255.0 and Default Gateway 192.168.0.1. Its prefix is 192.168.0, so every command below uses 192.168.0 where the examples say 192.168.1. Do not assume 192.168.1; many routers use 192.168.0, 10.0.0 or something else entirely.

Build the full list in PowerShell

PowerShell gives the cleanest result, because Get-NetNeighbor reports a state for each entry and can filter out the noise. If you have not used it before, see how to open PowerShell in Windows 10; an ordinary (non-administrator) window is enough to read the list.

1. Right-click Start and choose Windows PowerShell.
2. Set your prefix (change the value to match your own range):

   $prefix = "192.168.1"

3. Ping every address once, with a short timeout, and hide the output:

   1..254 | ForEach-Object { ping.exe -n 1 -w 100 "$prefix.$_" | Out-Null }

   This can take a few minutes, because each address with no device waits for the timeout. The -n 1 switch sends a single echo request and -w 100 waits 100 milliseconds for a reply, per Microsoft’s ping command reference (the docs write the switches with a slash; the dash form works too).

4. Read the neighbor table, keeping only live entries and sorting the addresses in numeric order:

   Get-NetNeighbor -AddressFamily IPv4 -State Reachable,Stale,Delay,Probe | Sort-Object { [version]$_.IPAddress } | Format-Table IPAddress, LinkLayerAddress, State, InterfaceAlias

You get one row per device: the IP address, the MAC address (shown as LinkLayerAddress), its state and the adapter it was seen on. Leaving out the Permanent state removes the fixed broadcast and multicast entries Windows keeps for itself, and leaving out Unreachable and Incomplete removes addresses that did not answer.

What the states mean

Microsoft’s Get-NetNeighbor documentation lists these values for the -State parameter:

• Reachable: confirmed within roughly the last minute. Treat it as online now.
• Stale: was valid, but has not been confirmed recently. The device may still be there or may have left.
• Delay and Probe: Windows is in the middle of rechecking the entry.
• Incomplete and Unreachable: Windows asked for the address and got no answer.
• Permanent: a fixed entry, such as a multicast address, not a real device.

If you have both Wi-Fi and Ethernet connected, add -InterfaceAlias “Wi-Fi” (or “Ethernet”) to the Get-NetNeighbor command so you only see one network.

Save the list to compare later

Swap the Format-Table part for an export to keep a copy on your desktop:

Get-NetNeighbor -AddressFamily IPv4 -State Reachable,Stale | Select-Object IPAddress, LinkLayerAddress, State | Export-Csv "$env:USERPROFILE\Desktop\network-devices.csv" -NoTypeInformation

Open the file in Excel or Notepad and add a column for what each device is once you identify it. Next month, run the same sweep and look for MAC addresses that are not on the old list.

The Command Prompt version with arp -a

If you prefer Command Prompt, or PowerShell is blocked on a managed PC, the same idea works in two commands. Replace 192.168.1 with your own prefix.

1. Run the ping sweep (type it exactly, including the percent signs):

   for /L %i in (1,1,254) do @ping -n 1 -w 100 192.168.1.%i | find "TTL"

   Each line that appears is a device that answered. Silence for an address just means no reply. If you put this line in a .bat file instead, double the percent signs (%%i).

2. When the loop finishes, run arp -a.

The output is grouped under an Interface line for each adapter, with three columns: Internet Address, Physical Address and Type. Microsoft’s arp command reference also documents -N followed by your own IP address to show just one interface, which helps when a VPN adapter adds its own block. To save the output, run arp -a > “%USERPROFILE%\Desktop\arp-list.txt”.

Unlike Get-NetNeighbor, arp -a does not tell you how fresh an entry is. If the list looks crowded with devices you know are switched off, clear the ARP cache from an administrator prompt, then run the sweep again so only current devices come back.

Read the results without being fooled

A few rows in every list are not devices at all, and a few real devices look odd. Before you start counting:

• Addresses ending in .255 (on a 255.255.255.0 network) and 255.255.255.255 are broadcast addresses. They reach everything and belong to nothing.
• Addresses from 224.x.x.x to 239.x.x.x are multicast groups, used by things like casting and device discovery. Ignore them.
• Type static in arp -a usually marks those broadcast and multicast rows. Type dynamic rows are the ones to look at, though a dynamic entry can still belong to a device that has since left.
• Your own PC is not in the list. Its address is the IPv4 Address from ipconfig.
• The Default Gateway is your router. On mesh systems you may also see each satellite unit as a separate device.
• One device can appear twice if it is plugged in and on Wi-Fi at the same time, because each adapter has its own MAC address and gets its own IP address.

Put names to the addresses

An address on its own does not tell you whether it is the printer or the doorbell. Try these in order, from quickest to most reliable.

Ask the device for its name

• ping -a 192.168.1.40 in Command Prompt tries a reverse name lookup and prints a host name in the first line if one exists. Microsoft documents this as the /a switch.
• nbtstat -A 192.168.1.40 (capital A) asks a Windows PC or NAS for its NetBIOS name table, according to Microsoft’s nbtstat reference. Phones, TVs and most smart-home gear do not answer.
• Resolve-DnsName 192.168.1.40 in PowerShell does the same reverse lookup as ping -a. It only returns a name if your router registers device names in its DNS, which many home routers do and some do not.

Look up the maker from the MAC address

The first three pairs of a MAC address (for example 3C-22-FB) identify the manufacturer of the network chip. Paste them into any MAC vendor lookup site and you will often get a brand name that narrows the device down, such as a printer maker or a TV brand. Note that the chip maker is not always the device maker.

This fails for most phones and many laptops, because they use a private (randomized) MAC address on each Wi-Fi network. Apple’s support page on private Wi-Fi addresses explains that iPhones use a different MAC address for each network by default, under the Private Wi-Fi Address setting (Off, Fixed or Rotating). A randomized address matches no manufacturer, so a lookup that comes back empty is normal for phones and not, on its own, a sign of an intruder. To see the MAC address your own PC uses, follow the steps to find your MAC address in Windows 10.

Use the switch-off test

When nothing else works, turn one suspect device off (or put a phone in airplane mode), wait a minute, run the sweep again and see which row disappears or changes to Unreachable. It is slow, but it never lies.

Check the list against your router

The router is the device that hands out addresses, so its list usually has the best names. It also catches devices that ignore pings.

1. Open a browser and type the Default Gateway address from ipconfig, for example http://192.168.1.1. If your internet provider supplied a phone app for the router, that app usually shows the same list.
2. Sign in with the router’s admin password. If you never changed it, it is often on a label on the router.
3. Look for a page named something like Connected Devices, Attached Devices, Device List, Client List or DHCP Clients. The name varies by brand.

Match the rows by MAC address, not by name: the router may call a device “android-7f3c” while your PowerShell list only has its MAC. Many router lists also show whether each device is on Wi-Fi or wired and which band it uses. Some keep showing devices that left hours ago until their address lease runs out, so a router list can be longer than the live list from your PC.

While you are in the router, you can usually reserve an address for a device such as a printer, so it gets the same IP every time. That is easier than setting a fixed address on the device itself and keeps your PC on automatic addressing; the steps to enable DHCP in Windows 10 cover the PC side of that.

Bigger networks, other subnets and scanner apps

The ping loops above suit a normal home network. Reach for something else when:

• You want one window instead of commands. Free Windows scanners such as Advanced IP Scanner and Angry IP Scanner scan a range and list IP addresses, names and MAC addresses. Download them only from the developer’s own site, and expect a security prompt during setup.
• You are comfortable with a power tool. Nmap’s host discovery command nmap -sn 192.168.1.0/24 lists live hosts without scanning their ports. Nmap’s documentation says that when it runs with administrator rights on a local Ethernet network it uses ARP requests, which find devices that ignore pings.
• You only care about Windows PCs and shared drives. File Explorer’s Network section shows names of computers, printers and media devices that announce themselves, once network discovery is turned on for a private network. It does not show IP addresses for most entries. The net view command is similar and often comes back empty on home networks.

Scan only networks you own or have permission to scan. On a work or school network, a scan can trip security alerts and break policy even if you mean no harm, so ask IT for their device list instead.

Devices that never show up

If you know something is connected but it is missing from every Windows list, the cause is usually one of these:

• It is on the guest network. Guest Wi-Fi is normally a separate subnet that your PC cannot see, by design. Only the router list shows it.
• It is asleep. Phones, tablets and battery cameras drop off Wi-Fi to save power. Wake the device and run the sweep again.
• Its firewall blocks pings. Windows PCs often ignore incoming pings, and so do many other devices. The neighbor cache often still catches them on the same Wi-Fi, but not always; the router list does.
• Your PC is on a different segment. Some mesh systems and range extenders, and any office network split into VLANs, put devices on separate segments. The ARP cache only covers your own segment.
• You scanned the wrong prefix or adapter. Check the IPv4 Address again, especially if a VPN is connected, because the VPN adapter has its own range.

If a device looks unfamiliar

An unknown row is usually something forgotten: a smart speaker, a games console, a relative’s phone with a private MAC address. Rule those out with the switch-off test and the router’s names first. If a device is still unexplained:

1. Change the Wi-Fi password in the router, then reconnect your own devices. Anything that does not come back was not yours, or you will find out when it stops working.
2. Make sure the router uses WPA2 or WPA3 security, and change the router’s own admin password if it is still the one on the label.
3. Move visitors and smart-home gadgets to the guest network so they cannot see your PCs.
4. If the worry is your PC rather than the network, look for software that should not be there: the checks to find a backdoor on Windows 10 cover that, and you can block a specific IP address in Windows Firewall while you investigate.

Not sure which Wi-Fi you are on before you start? You can find your network name in Windows 10 from the taskbar or Settings.

Network device questions

Why does my router list more devices than PowerShell does?

The router remembers every device it gave an address to until the lease expires, including ones that left, and it sees the guest network. Your PC only sees devices on its own segment that answered recently. Use the router count as the upper limit and the Reachable rows as what is online right now.

Does the ping sweep slow down the network?

Not noticeably on a home network. It sends one small packet per address, about 254 packets in total, spread over a few minutes.

Why did a device get a different IP address since last week?

Routers lend addresses for a limited time and can hand out a different one after a restart or when a device has been away. Track devices by MAC address in your saved list, or reserve an address in the router for anything you need to find again.