How to Locate Your IP Address on a Windows PC for Troubleshooting
Finding the IPv4 or IPv6 address assigned to a Windows PC helps diagnose connectivity, routing, and security questions. This discussion covers the difference between private (local) and public (external) addresses, shows the main Windows methods to view an address—including Settings, Command Prompt (ipconfig), and PowerShell—and explains how to confirm the public IP reported by a router or modem. It also notes when administrator privileges matter and the common trade-offs between methods used for home or small-business troubleshooting.
Quick overview of IP address types and when to check them
Start by separating local network addresses from external addresses. A local (private) IP identifies a device on a home or office LAN and is useful for device-to-device troubleshooting. A public IP is the address visible to the internet and is relevant for remote access, NAT behavior, and ISP routing.
- Private (local) IP: used inside a LAN, often in ranges like 192.168.x.x, 10.x.x.x, or 172.16–31.x; important for DHCP and local connectivity checks.
- Public (external) IP: assigned to the router or modem by the ISP; relevant for port forwarding, remote access, and identifying the network externally.
- IPv4 vs IPv6: IPv4 is still dominant for most consumer networks; IPv6 addresses are longer and may appear alongside IPv4 on modern systems.
Find the IP using Windows Settings
Windows Settings provides a graphical way to view an adapter’s IP without command-line input. Open Network & Internet, choose Status or Ethernet/Wi‑Fi depending on the connection, and view the properties for IPv4 and IPv6 addresses. On Windows 10 and Windows 11 the path is similar, though labels and layout vary slightly. This approach is convenient for users who prefer visual confirmation and need adapter names and DNS settings alongside the address.
Find the IP using Command Prompt (ipconfig)
ipconfig is the standard diagnostic tool for quick CLI checks. Open Command Prompt (cmd.exe) and run ipconfig /all to see adapter lists, IPv4/IPv6 addresses, subnet masks, and DHCP/DNS details. The primary interface entry for the active adapter shows the local address. In practice, ipconfig is useful when you need text output to copy into support tickets or to confirm DHCP lease information reported by Windows.
Find the IP using PowerShell
PowerShell offers structured output and more filtering than ipconfig. A common command is Get-NetIPAddress, which lists interfaces with AddressFamily, PrefixLength, and IPAddress fields. For a compact view of IPv4 addresses on active adapters use Get-NetIPAddress -AddressFamily IPv4 -PrefixLength 24 or filter by InterfaceAlias. PowerShell output is easier to script for repeated checks, and official Microsoft documentation covers available parameters for different Windows versions.
Check the router or modem for the public IP
The public IP assigned by the ISP usually appears on the router or modem status page. Sign into the device’s web admin interface (commonly at 192.168.0.1 or 192.168.1.1) and check the WAN/Internet status line to see the external IPv4 or IPv6 address. For networks using carrier-grade NAT or multiple layers of NAT, the modem’s status may show a private address and the ISP’s portal or a hosted service will show the public-facing address. This method is the most reliable way to confirm the address seen from the internet without relying on a third-party web lookup.
When administrator permissions are required
Some diagnostic commands and router configuration pages require elevated privileges. Viewing IP addresses via Windows Settings, ipconfig, and basic Get-NetIPAddress queries typically work under a standard user account for that machine. However, changing adapter settings, examining all system interfaces, or running scripts that modify network configuration requires administrator rights. Accessing a router or modem page requires the login credentials for that device; lacking them limits visibility to what a single workstation can report.
Trade-offs and accessibility considerations
Choosing a method depends on the task, user skill, and accessibility needs. Graphical Settings are easier for users who rely on assistive technologies and avoid command-line syntax, while Command Prompt and PowerShell give concise, copyable output favored in technical support. PowerShell provides richer filtering but introduces a learning curve. Some tools and commands display only the local address; identifying the external address requires either router access or an external service. Network configurations such as VPNs, multiple NICs, virtual adapters, and carrier-grade NAT complicate interpretation; for example, a VPN will typically replace or tunnel the public endpoint, making local checks insufficient to determine the address visible to remote services. When working with accessibility tools, text output from commands can be easier to navigate with screen readers than complex web interfaces on a router page.
How to find public IP on router?
When to use PowerShell vs ipconfig?
Can a VPN hide my public IP address?
Final considerations for checking an IP address
Match the method to the problem: use Settings or ipconfig for quick local checks, use PowerShell for scripted or filtered output, and inspect the router/modem for authoritative public-IP information. Remember that IPv4 and IPv6 may appear together and that VPNs or double NAT setups change what address a remote service sees. For official command references and parameter details, consult Microsoft documentation for ipconfig and Get-NetIPAddress. Keeping a clear distinction between local and external addresses reduces troubleshooting time and avoids common misinterpretations when diagnosing connectivity or privacy concerns.
