Intel device manager diagnostics utility12/15/2023 ![]() This is a weird but true experience i have with my work laptop. Set the PC for DHCP disconnect the cable at one end or the other shut down the PC power-cycle the modem/router connect the PC to the modem/router on a different port boot the PC. It can sometimes also help to move the connection from one port to another, because of MAC addresses and the like lingering. That would tell you what address range to use during static IP configuration (192.168.0.x, for example), and you should clone those gateway and DNS server addresses in the relevant settings on the new NIC, if you can't get DHCP to work initially (which it obviously should).ĥ.97 Consider power-cycling (but not hard-resetting!) the modem or router to sort of jiggle the handle and flush things out. The gateway address will most often (but not always) be the address of the LAN port on your modem or router, whatever is handing out the DHCP address normally. What was your prior configuration (integrated 10/100 NIC, etc.), and did it work? If so, consider temporarily falling back to that configuration at least long enough to document its settings use ipconfig /all in a command shell to snag at least the gateway and DNS server addresses. But, also, maybe even before ya do that (thinking out loud, here). ![]() If it is still enabled, Windows management of it may linger and complicate management of the new NIC. ![]() Push into the device manager and disable (but do not uninstall!) it there. Make sure to completely disable the original interface, if there was one an onboard/integrated 10/100 NIC, a WiFi adapter, etc. ![]() With everything powered and connected, are there lights on at both ends of the connection? modem/router port 1, for example, and on the back of the NIC? If not, start there.ġ. It really sounds like driver issues on the PC side, but could be other things. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |