Tried the release/renew thing and it is unable to renew the IP because it couldnt contact the DHCP server and it timed out.
OK, the higher level functions will not operate if the network is not working at a lower level. You do not know if the lower level is working until you do those things I posted a day or so ago.
For example, what do those lights report both on computer and router? Do you even see the NIC listed in the Device Manager? What was listed in the system (event) logs?
Reloading an OS is a worst thing you could do for too many reasons to list including the long periods of reloading all the updates and better drivers for everything else. Reloading an OS is the worst example of fixing something without first identifying the problem. It typically creates numerous other problems. However, if you are more interested in learning than in fixing the computer, well, I could think of few other actions that will force more learning.
Even better than a 'nuke n pave' is Mulreay's 'remove and reload the driver' suggestion.
BTW, your problem is exactly why we buy better computers that come with the manufacturer’s comprehensive diagnostics. See all those previous posts? About half of them would be unnecessary why simply executing a comprehensive hardware diagnostic that only the better computer manufacturer’s provide.
I don’t see where anything says your network is working at the lowest level. Working at the second level was supposed to confirm lowest level protocols are working. If not, then your second level frustrations are explained. Very first step – what do lights report at both ends of the cable? Does Device Manager even see the NIC? Maybe locate a hardware diagnostic for your NIC that comes from the NIC manufacturer (even some chip manufacturers provide that diagnostics).
Currently I see nothing that says your NIC is working even at the lowest level. Only after we know that, then we can move on to why the NIC has failed. But if you ‘nuke n pave’ then nothing useful is learned. And you have reloading the hard drive using hardware (motherboard) that has at least one (and maybe more) defects. IOW only made the problem exponentially more complex. OS did not go bad.
