IT Toolbox
Guide

How to find your IP address on Windows

Quickly display the IPv4 address, gateway and DNS servers used by a Windows workstation…

TopicIT Networking →
⌚ About 2 min read
View my favorites
Windows Beginner 2 min.

Quickly display the IPv4 address, gateway and DNS servers used by a Windows workstation.

Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.

Étapes à suivre

  1. 1

    Open Terminal or the Command Invite.

    Press Windows + R, type cmd and then validate, or open Windows Terminal.

  2. 2

    Show Network Configuration.

    Enter the ipconfig command and then press Enter.

  3. 3

    Find the active interface.

    Search for the Ethernet or Wi-Fi card currently connected.

  4. 4

    Read the IPv4 address.

    Find the IPv4 address line. Example: 192.168.1.25.

  5. 5

    View more details.

    Use ipconfig /all to see also DNS, DHCP and the address Mac.

Commands utiles

ipconfig.
ipconfig /all.

À retenir

  • An address beginning with 169.254 often indicates that the position did not receive a DHCP address.
  • The public IP address is not usually the same as the local IPv4 address.
← All les guides
Technical deep dive

Windows addressing: useful reference points

Technical checkpoints

  • An address in 169.254.0.0/16 is APIPA
  • Read address, mask, gateway and DNS together: a correct IP with a wrong gateway or DNS is still a broken configuration.
  • Get-NetIPConfiguration gives a structured per-interface view; ipconfig /all remains useful for DHCP lease, DNS suffix and physical address.

Example check

Compare the active adapter, DHCP origin, gateway and DNS before renewing the lease.

Get-NetIPConfiguration
ipconfig /all

Topic-specific pitfalls

  • Renewing DHCP does not fix a wrong VLAN, an unauthorized switch port or a missing DHCP server.
  • A virtual or VPN adapter can appear before the interface actually in use: check InterfaceAlias and the default route.

How to validate

  • The address belongs to the expected subnet and no APIPA is present on the interface in use.
  • Gateway, DNS and DHCP lease match the expected network; the test is repeated after any change.
♡ 0