Windows · Windows Server · high · Networking & connectivity

169.254.x.x address — "Unidentified network, no internet"

The machine asked for an address, got no answer, and gave itself one from the automatic private range. Nothing routed can work with that address.

What you see

The adapter shows connected but the network is "Unidentified" with no internet. ipconfig shows an address starting 169.254 and no default gateway.

What is actually wrong

Either DHCP never answered — cable, VLAN, switch port, exhausted scope, a rogue server — or the reply arrived and Windows refused it because the DHCP Client service is stopped or the stack is damaged.

Codes and articles

169.254APIPAUnidentified networkDHCP_FAILURE0x8007274D

Fixes (3)

Confirm the DHCP client is actually running and asking

Elevated PowerShell10 minuteslow riskreversible

Start here. It is two commands and it rules out the cheapest cause.

Check the service and the adapter's own DHCP setting — these are two separate things and either one alone will do it.

PowerShell

Get-Service Dhcp | Format-List Name,Status,StartTypeGet-NetIPInterface -AddressFamily IPv4 | Format-Table InterfaceAlias,Dhcp,ConnectionState

If the service is stopped, start it and set it back to automatic.
PowerShell
```
Set-Service Dhcp -StartupType AutomaticStart-Service Dhcp
```
If the interface shows Dhcp Disabled but should be automatic, turn it back on.
PowerShell
```
Set-NetIPInterface -InterfaceAlias 'Ethernet' -Dhcp EnabledSet-DnsClientServerAddress -InterfaceAlias 'Ethernet' -ResetServerAddresses
```
A static address left behind by an old fix is a common cause, and the DNS servers have to be reset with it or the machine keeps pointing at a server that no longer exists.
Force a fresh request and watch what comes back.
Command Prompt
```
ipconfig /releaseipconfig /renewipconfig /all
```

Confirm it workedipconfig shows an address in the site's range with a default gateway, and the gateway answers.

PowerShell

Test-NetConnection -InformationLevel Detailed (Get-NetIPConfiguration).IPv4DefaultGateway.NextHop

If you need to undo itNothing changed that matters. If the adapter was deliberately static, put the address back with New-NetIPAddress.

Rebuild the TCP/IP stack and Winsock on this machine

Elevated Command Prompt20 minutesmedium risknot reversible

One machine only, the service is running, and a renew still gets nothing. Usually follows a bad VPN client or security product uninstall.

Note the current configuration first — this resets it.
Command Prompt
```
ipconfig /all > %USERPROFILE%\Desktop\before-reset.txt
```
Reset the two layers a broken filter driver sits between.
Command Prompt
```
netsh winsock resetnetsh int ip reset
```
Winsock reset removes third-party layered service providers; the IP reset rewrites the interface registry keys. A leftover VPN or antivirus filter driver breaks DHCP without breaking the link light, which is exactly what this looks like.
Clear the resolver and re-register.
Command Prompt
```
ipconfig /flushdnsnbtstat -Rnetsh advfirewall reset
```
Restart. This is not optional — the stack is rebuilt at boot.

Confirm it workedAfter the restart the adapter picks up a proper lease within a few seconds.

Command Prompt

ipconfig /all | findstr /i "DHCP Lease Gateway"

If you need to undo itnetsh advfirewall reset clears custom firewall rules — export them first with netsh advfirewall export if any are bespoke.

Prove where the DHCP conversation is being lost

Elevated PowerShell, plus switch access30 minuteslow riskreversible

More than one machine is affected. The fault is not on the client.

Check the physical link is what you think it is — a port negotiated at 10Mb half duplex behaves exactly like this.
PowerShell
```
Get-NetAdapter | Format-Table Name,Status,LinkSpeed,MacAddress
```
Capture the DHCP conversation so you can see whether a DISCOVER even leaves.
Command Prompt
```
netsh trace start capture=yes scenario=NetConnection tracefile=C:\dhcp.etlipconfig /renewnetsh trace stop
```
This settles the argument in one step: a DISCOVER with no OFFER is a network or server problem, no DISCOVER at all is the client.
On the DHCP server, check the scope has free addresses and the server is authorised.
PowerShell
```
Get-DhcpServerv4ScopeStatisticsGet-DhcpServerInDC
```
If the clients are on a different VLAN from the server, check the ip helper-address on the router — a missing relay is the single most common site-wide cause.

Confirm it workedClients lease normally and the scope statistics show the address count falling as they do.

If you need to undo itNothing on the client was changed. Delete C:\dhcp.etl when finished.

Related faults

Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.