How do I inspect my Windows IP address, gateway and DNS servers?
Inspect your local interface, gateway and DNS information to understand the path used to reach a server. A local private IP is not necessarily the public source address seen by the server, especially through NAT or a VPN.
Instructions
1. Read the PowerShell network summary
This command does not renew addresses or modify routing.
Get-NetIPConfigurationReview the relevant interface alias, addresses, default gateway and DNS servers.
2. Use the CMD detail view if needed
The output can contain internal network details, so redact it before sharing.
ipconfig /allThis shows adapter configuration, including disconnected or virtual adapters. Select the adapter actually used for the connection.
3. Check the selected route for the service test
The TCP diagnostic identifies the chosen source address and interface.
Test-NetConnection 203.0.113.10 -Port 22 -InformationLevel DetailedCompare SourceAddress and InterfaceAlias with the intended VPN or network path.
Check the result
- The active interface has the expected address, gateway and resolver configuration.
- The server test uses the intended source interface.
Troubleshooting
- Several adapters are present
- A VPN, virtual switch or container platform can add adapters. Do not assume the first listed adapter is the relevant one.
- The server allowlist expects another source IP
- Confirm the authorised public egress address with your network administrator; the local private address is not sufficient.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.