How to Find Your IP Address on Windows

Ever tried configuring a network printer or enabling remote desktop access, only to realize nobody on the team actually knows the machine's IP address? Knowing how to find your IP address on Windows is one of those foundational skills that surfaces constantly in real-world networking — whether it's pointing a second device at a shared resource, debugging a failed DHCP lease, or verifying a static assignment after a router swap. The answer is always just a few clicks or keystrokes away. For more practical guides like this one, the tech tips section covers everything from connectivity fixes to Windows productivity workflows.

IP addresses serve as the numerical identifiers that allow every device on a network to communicate. On a typical Windows machine, there are actually two distinct addresses worth knowing: the private IP assigned by the local router, and the public IP the ISP assigns to the entire household or office. Most troubleshooting tasks — including configuring shared drives, setting up local servers, and even transferring files from a PC to Android wirelessly — depend on knowing at least the private IP first.

This guide walks through every reliable method for locating both address types on Windows, covers the common mistakes that cause the most confusion, and offers practical advice for keeping network information organized over time. No advanced networking background required — though the explanations don't shy away from technical precision where it matters.

How to Find Your IP Address on Windows — Step by Step

Finding the local IP on a Windows machine takes under a minute using any of the methods below. Each surfaces the same core data, so the choice usually comes down to personal preference, workflow, and whether a terminal is already open.

Using the Windows Settings App

The Settings path works well for quick one-off lookups and doesn't require opening a terminal. The steps are essentially identical on Windows 10 and Windows 11:

1. Press Windows key + I to open Settings.
2. Navigate to Network & Internet.
3. Click the active connection — Wi-Fi or Ethernet — then click the connection name link.
4. Scroll down to the Properties section.
5. Read the IPv4 address field.

The same screen also shows the subnet mask, default gateway (the router's IP), and DNS server addresses — enough context for most home and small-office tasks. It's clean, readable, and requires no command-line experience.

Using Command Prompt and ipconfig

Command Prompt is the fastest method for anyone comfortable with a terminal. Open it by pressing the Windows key, typing cmd, and pressing Enter. Then run:

ipconfig

The output lists every network adapter installed on the machine. Look for the active one — usually labeled "Wireless LAN adapter Wi-Fi" or "Ethernet adapter Ethernet" — and read the IPv4 Address line. The Default Gateway entry shows the router's address, useful context for a lot of network tasks.

For deeper diagnostics, the extended version reveals significantly more:

ipconfig /all

This adds MAC addresses, DHCP server IP, lease acquisition and expiration timestamps, and DNS server addresses — the version to run when documenting a machine's full network profile or diagnosing DHCP behavior.

Running ipconfig /all in Command Prompt surfaces DHCP lease times, server addresses, and DNS configurations that the Settings app never exposes — the right tool when basic connectivity data isn't enough.

Using the Classic Network and Sharing Center

The Control Panel path works identically across every Windows version from 7 onward, which makes it particularly useful in mixed-OS environments or when Settings is locked down by group policy:

1. Open Control Panel → Network and Internet → Network and Sharing Center.
2. Click the active network connection link.
3. In the Status window, click Details.
4. The Network Connection Details dialog displays IPv4 address, subnet mask, gateway, and DNS servers in one view.

Understanding Private vs. Public IP Addresses

Every Windows machine on a standard home or office network simultaneously has a private IP and shares a public IP with every other device behind the same router. The two serve completely different purposes — and mixing them up causes real problems.

What Private IP Addresses Are

Private IPs are assigned by the router's DHCP server and are only valid within the local network. Standard private ranges (defined by RFC 1918) are:

• 10.0.0.0 – 10.255.255.255
• 172.16.0.0 – 172.31.255.255
• 192.168.0.0 – 192.168.255.255

Home routers almost universally use the 192.168.x.x range. The private IP is what ipconfig returns, and it's the address needed for local network tasks like sharing a printer over Wi-Fi on a home network or mapping a shared drive between machines in the same building.

What Public IP Addresses Are

The public IP is the address the ISP assigns to the router — it's what the broader internet sees. All devices behind the router share it through NAT (Network Address Translation). To find the public IP, users need to either log into the router's admin panel or use a browser-based lookup tool. Command Prompt's ipconfig output will never show it, which is a common source of confusion.

A "192.168.x.x" address from ipconfig is invisible to the public internet — sharing it with a remote technician who needs to connect in won't work without the public IP and properly configured port forwarding.

Common Mistakes to Avoid When Checking IP Addresses

Even a straightforward task like looking up an IP address has a few consistent failure points. These are the mistakes that cause the most confusion in home and small-office setups, and they're worth knowing before they cause problems.

Confusing Private and Public IPs

The most common mistake: grabbing the address from ipconfig and sharing it with someone outside the local network. Remote desktop connections, inbound VPN tunnels, game server hosting, and port-forwarded services all require the public IP — plus router-level port forwarding configured correctly. Private IPs only work within the LAN. This confusion is especially common when setting up remote access for the first time, because the machine itself doesn't visibly distinguish between its private and public identities.

Reading the Wrong Network Adapter

Modern Windows machines typically have multiple network adapters active at once: a physical Wi-Fi adapter, a physical Ethernet adapter, one or more VPN tunnel interfaces, and virtual adapters from tools like VirtualBox, Hyper-V, or VMware. Running ipconfig without reading carefully can mean pulling an address from a virtual or inactive adapter — one that doesn't carry any actual traffic.

When multiple adapters appear in ipconfig output, cross-reference with the Network & Internet settings panel to confirm which adapter is actively carrying traffic before recording or sharing the address.

Users managing multiple machines — for example, across a multi-monitor workstation setup — may find it easier to keep a terminal window dedicated to network diagnostics. The guide on setting up dual monitors on Windows covers the workflow for running multiple display configurations, which pairs naturally with managing several open windows simultaneously. Storing any collected network documentation in a password-protected folder on Windows keeps IP logs and credentials away from casual access.

Troubleshooting When the IP Address Looks Wrong

Sometimes ipconfig or the Settings app returns an address that doesn't make sense — a bizarre range, a duplicate address warning, or an IP that simply won't connect to anything. Here's how to read those signals and respond.

The 169.254.x.x APIPA Problem

An address in the 169.254.0.0/16 range is a Windows self-assigned link-local address — the result of APIPA (Automatic Private IP Addressing) kicking in because the machine couldn't reach the DHCP server. This address won't route anywhere. The machine will be effectively isolated from the network despite showing a connected status.

Common causes and fixes:

• Faulty or unplugged cable — check physical connections before anything else
• Router still booting — wait 60–90 seconds and try reconnecting
• Exhausted DHCP lease pool — run ipconfig /release then ipconfig /renew in an elevated Command Prompt
• DHCP Client service stopped — restart it through services.msc
• Network adapter driver issue — update or reinstall the adapter driver via Device Manager

IP Not Refreshing After Switching Networks

Switching between networks — from a corporate VPN to a home router, or from one Wi-Fi SSID to another — sometimes leaves stale DHCP lease data cached in Windows. The machine holds onto an old address that doesn't work on the new network. The fix sequence in an elevated Command Prompt:

1. Disconnect from the current network.
2. Run ipconfig /release to drop the current lease.
3. Run ipconfig /flushdns to clear the DNS resolver cache.
4. Run ipconfig /renew to request a fresh address.
5. Reconnect to the target network.

If the machine's boot process is slow and the network adapter is one of many services fighting for resources at startup, disabling unnecessary startup programs on Windows can help the adapter initialize faster and receive its DHCP lease before other services that depend on network connectivity attempt to launch.

Building Long-Term Network Awareness

Knowing how to find an IP address once is useful. Building habits that reduce the need to look it up from scratch every time is better. A few straightforward practices cover most home and small-office networking needs without requiring any specialized tools.

Static IPs and DHCP Reservations

Home networks use DHCP by default, which means device IPs can shift after a reboot or lease expiration. For devices that need a predictable address — NAS drives, network printers, machines running local servers — the options are:

• Static IP configured on the device: Set a fixed IP in Windows Network Adapter Settings. Requires entering the subnet mask, default gateway, and DNS server addresses manually — all available from ipconfig /all.
• DHCP reservation on the router: The router always issues the same IP to a specific MAC address. Easier to manage centrally, with no per-device configuration needed.

DHCP reservations are generally the cleaner approach for home networks, since all address management stays in one place and survives Windows reinstalls or hardware swaps.

Documenting the Network

A simple reference document — updated whenever a device is added or removed — saves time on every future networking task. At minimum it should capture:

• Each device's hostname, MAC address, and assigned IP
• The router's IP (default gateway) and admin panel URL
• DHCP range and any static assignments or reservations
• DNS server addresses (especially relevant if using a custom resolver)

Keeping that file current pairs naturally with tasks like finding saved Wi-Fi passwords on Windows when onboarding a new device, or verifying that a replacement printer picked up the right reserved address after a swap. Users who capture troubleshooting sessions on video — using the built-in screen recording tools available on Windows without extra software — find that having a baseline network document makes annotating those recordings far easier.

Every networking task on Windows — from printer sharing to remote access — starts with knowing the IP address, and knowing where to find it in under sixty seconds is a skill that never stops being useful.