Quote:
Originally Posted by footfootfoot
lately when I have been using cmd prompt nothing at all has been happening...
|
Do not change anything until important facts are obtained. Fixing without identifying the problem can exponentially complicate the problem.
ISO defines three relevant layers of communication. Start by defining what is happening at the lowest level (especially since IPCONFIG reported that as a potential defect).
An ethernet cable terminates at the computer and at the router. On the computer receptacle should be some lights. As the cord is disconnected, what happens to those lights. Repeat the same test on the router end. These lights will be on the front panel. Report those lights (and router model).
NIC's computer must talk with the router's computer. Those lights are reporting a conversation that you otherwise never see or know about. Are NIC and router computers talking? Do they talk both in Safe modem and when booted normally?
Next, go to Device Manager (obtained via Computer Management or Control Panel or Help). What is reported for the Network Adapters?
Do not try to change drivers by deleting software. First delete the device in Device Manager. And reboot. Or use Device Manager to Update Driver. But do not do that yet. First collect facts.
Helpful would be the manufacturer and model of that computer. Some manufacturers provide comprehensive hardware diagnostics to immediately solve such problems without all this sweat and confusion. Since Windows only tries to work around problems. But diagnostics seek to identify hardware problems even before you know the problem exists.
A diagnostic may also be available from the NIC manufacturer.
All this is about defining the first layer as good or bad. If the NIC appears good, then go back to Device Manager to update what should have been a perfectly good driver. Reboot. And report back what IPCONFIG /ALL reports.