What is SEC_E_NO_IP_ADDRESSES (0x80090335)?
This error means Windows can't find an IP address on any network adapter that's currently active. It almost always shows up when you're trying to authenticate via Kerberos or bind to an LDAP server — the error text is “Unable to accomplish the requested task because the local machine does not have an IP address”. The culprit here is almost always a DHCP lease that expired, a network adapter that got disabled by accident, or a misconfigured static IP.
I've seen this on Windows 10, Windows 11, and Server 2019/2022. The fix is usually quick. Let's walk through it from fastest to most involved.
Step 1: The 30-second fix — ipconfig release and renew
Open Command Prompt as Administrator. Run these two commands in order:
ipconfig /release
ipconfig /renewIf you're on a network with a DHCP server (most corporate and home networks), this forces your machine to grab a new IP lease. Wait about 10 seconds after the second command. Then check your IP with:
ipconfigIf you see an IP address (not 169.254.x.x), you're done. The error will disappear. If you get 169.254.x.x, that's an APIPA address — means DHCP is unreachable. Move to step 2.
Step 2: The 5-minute fix — Check DHCP and adapter state
If release/renew gave you a 169.254.x.x address, your DHCP server isn't responding. First, check if your network adapter is even enabled. Run:
netsh interface show interfaceLook for your adapter — it should say “Connected” and “Enabled”. If it's “Disabled”, enable it:
netsh interface set interface "Ethernet" admin=enabledReplace “Ethernet” with your actual adapter name. Then retry the release/renew.
Next, check if you accidentally set a static IP that doesn't match your subnet. Right-click the network icon in the system tray → Open Network & Internet settings → Change adapter options → right-click your adapter → Properties → Internet Protocol Version 4 (TCP/IPv4). Make sure it says “Obtain an IP address automatically” unless you absolutely need a static IP. If it's set to static but blank or wrong, that's your problem.
Another common cause: your network cable is unplugged, Wi-Fi is off, or the switch port is administratively down. Check physical connectivity. If you're on Wi-Fi, make sure you're connected to the right SSID and have a valid password. Sometimes Windows forgets the Wi-Fi profile — delete it and reconnect.
Step 3: The 15+ minute fix — Winsock reset, adapter reset, or driver reinstall
If you still have no IP after steps 1 and 2, something deeper is broken. Let's reset the network stack.
First, reset Winsock and the TCP/IP stack. Run these in an admin command prompt:
netsh winsock reset
netsh int ip reset
ipconfig /flushdnsRestart your machine. Then try step 1 again.
If that fails, it's time to reset the network adapter completely. Open Device Manager (devmgmt.msc). Find Network adapters, right-click your active adapter, and choose “Uninstall device”. Important: check “Delete the driver software for this device” only if you have the driver handy. Then restart Windows — it will reinstall the driver automatically. After reboot, run step 1 again.
Still stuck? Check if your DHCP service is running. Open Services (services.msc), find “DHCP Client”. It should be running and set to Automatic. If it's stopped, start it and set it to Automatic. Then retry the release/renew.
One last thing — I've seen a faulty third-party firewall or VPN client (looking at you, old Cisco AnyConnect) block DHCP requests. Temporarily disable any third-party firewall or VPN software. If the error goes away, you found the culprit. Update or remove that software.
When to call in the network guys
If none of this works, the problem is almost certainly on the network side — dead switch port, exhausted DHCP scope, or a VLAN mismatch. Run ipconfig /all and look at the DHCP server field. If it's 0.0.0.0, no DHCP server is reachable. Ping your default gateway (if you know it) — no response means you're not on the network.
That's it. Get that IP address back, and SEC_E_NO_IP_ADDRESSES goes away. I've fixed this exact error at least 30 times. The fix is almost always in step 1 or step 2.