Solved Local Area Connection doesn'thave a valid IP configuation

[dsperber]

To be honest, I'm not sure what the Marvel Link Aggregation Protocol and Marvel VLAN Protocol are. They were added when I updated the driver. That said, they were not there when the issue started. I updated the driver, they appeared upon that update, and I still had the same issue.

Updated WHAT driver, after which they appeared?

Here's a relatively extreme experiment you might try, assuming you have the ability to take a quick "system image" backup from the problem machine, of your C-partition and "system reserved" partition to an external USB 3.0 drive (say which you're already currently using for your own regular backups on some machine in your home LAN) using Macrium Reflect Free, and also have a usable Win7 installation DVD and valid license product key. It'll only take 5-10 minutes to take the backup, and less than another hour to do a Win7 reinstall from scratch.

Then see if the newly installed Win7 can properly connect to your router and get to the Internet. You don't even need to do the Windows updates yet to test out the theory.

If you still can't get to the Internet or see the router or get an IP address, then there's probably some hardware explanation.

If however you now CAN get to the Internet and get an IP address from the router, well it's clearly some software problem in your old system. Don't know what, but sometimes starting from scratch is the only way to resolve these mysteries. Sometimes the OS needs a fresh install every few years, to get past anomalies like this which are software-based.

Worst case, your PC is currently unusable since it needs to get to the Internet to be usable for your mother. You can easily restore the "system image" with Macrium Reflect (erasing that experimental Win7 you just quickly tried) and you're back to where you started... no harm, no foul, and no better off.

The fact that you've tried the built-in Realtek PCIe NIC as well as the add-on card NIC and they both have failed identically, well my guess is that this is pointing to a true Windows-based corruption (or other software we're not aware of) of some kind that is responsible, and which unless we can find it, fix it, or uninstall it, we'll never resolve it.

Won't take you much time to try a fresh reinstall of Win7 from scratch if you have the tools, just to see if the problem disappears or remains. Seems like we're now at that extreme point.

 

[roybman]

To answer your last question, they appeared after updating the driver for the Realtek NIC.
Thanks for the input. I agree, I've hit the wall on this. I'll post after I've had a chance to reinstall Win7.

 

[roybman]

Just as a final update, reinstalling the OS resolve the issue. I'll never know what specifically went wrong, but at least it's fixed. Thanks again for your help.

 

[dsperber]

Just as a final update, reinstalling the OS resolve the issue. I'll never know what specifically went wrong, but at least it's fixed.

Well, you emerged victorious! And that's what's important.

Sometimes the "detritus" in an operational system accumulates over time to where it just begins to act strangely and inexplicably, and can just never be overcome no matter how smart we are. We all know it's bound to be caused by some kind of corruption to the Registry, or maybe some malware or virus that crept in over time that we never noticed, or some junk that got installed along with some vendor product we installed and foolishly forgot to take the "custom install" path to un-check all the garbage which otherwise would get installed, etc.

Whatever the history and explanation, at some point there simply seems to be no actual "fix" or "solution", other than to reinstall Windows from scratch and then reinstall all of your vendor software and customizations. Or, maybe go back to a "gold" backup you took in order to save 3-4 days of installation from scratch.

With WinXP that time frame was very commonly 6 months to a year, before it just got slower and slower and nothing we could do could fix it. With Win7 that time frame really has increased, and it's not really unusual to go 1-2 years between self-justifying a full reinstall from scratch.

But sometimes it's clearly called for, or at least worth the experiment to see if the mysterious problems all magically disappear as they almost always do (unless you've actually been chasing a hardware problem). In your current story, that appears to be what was required.

Anyway, glad you finally got this all sorted out... even if it took the extreme solution of a reinstall of Windows.