Router won't assign network adapter a valid IP address

For some reason my Router stopped assigning my LAN Adapter a valid IP address. No windows updates were made, the router did not reset, I didn't change the driver, it was entirely spontaneous.

Things I've tried with no success:

• Power cycled the PC and the Modem/Router
• /release & /renew the IP address trough the cmd prompt
• "netsh winsock reset" from the cmd prompt (and restarted machine)
• Switched ethernet ports on both the router AND my PC (I have two ethernet network adapters)
• putting my entire router in the microwave for 15 minutes with a can of gasoline
• repeated all the above steps per the direction of a "technical expert" at Verizon FiOS who clearly drinks paint for breakfast
• Replaced the ethernet cable
• Updated the driver of the network adapter
• Manually entered a valid IPv4 address through the TCP/IPv4 Properties window

Attached are screen shots of the diagnostic results from Windows 7 that fail, as well as the ipconfig /all results with the invalid IP address the router keeps assigning.

I'm running Windows 7 x64 with a Realtek RTL8168D/8111D Ethernet Adapter. Other devices on the network connect without incident, including the laptop I'm submitting this from and my Xbox 360.

mckillwashere said:

Have you checked to make sure DHCP is enabled on the router still?

Yes, it is still enabled and other devices are getting assigned valid IP addresses just fine.

Adrian said:

Whats the router brand and model?

It is an Actiontec MI424-WR Rev.E modem router combo supplied by Verizon.

I'm almost convinced it is a network adapter or windows issue though, because other devices (wired and wireless) connect to it just fine.

foogama said:

For some reason my Router stopped assigning my LAN Adapter a valid IP address. No windows updates were made, the router did not reset, I didn't change the driver, it was entirely spontaneous.


Things I've tried with no success:

• Power cycled the PC and the Modem/Router
• /release & /renew the IP address trough the cmd prompt
• "netsh winsock reset" from the cmd prompt (and restarted machine)
• Switched ethernet ports on both the router AND my PC (I have two ethernet network adapters)
• putting my entire router in the microwave for 15 minutes with a can of gasoline
• repeated all the above steps per the direction of a "technical expert" at Verizon FiOS who clearly drinks paint for breakfast
• Replaced the ethernet cable
• Updated the driver of the network adapter
• Manually entered a valid IPv4 address through the TCP/IPv4 Properties window

Attached are screen shots of the diagnostic results from Windows 7 that fail, as well as the ipconfig /all results with the invalid IP address the router keeps assigning.

I'm running Windows 7 x64 with a Realtek RTL8168D/8111D Ethernet Adapter. Other devices on the network connect without incident, including the laptop I'm submitting this from and my Xbox 360.

When you scroll down your ipconfig, how many of those tunnel adaptors do you see there?

No exclamations marks or outstanding issues in the device manager.

I have two different LAN ports on my PC to experiment with, so i updated one to the most current driver off the Realtek's website, and the 2nd one I deleted to let windows assign it its own driver. Both still have the same problem.

I gave the router a hard reset as well--no dice.

I see two tunnel adapters: "Tunnel Adapter isatap" and "tunnel adapter Local Area Connection* 9". I have no idea what either of those are or what they do. They are both disconnected though.