-
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
Arrggh stupid router
- Thread starter GoodToGo
- Start date
Perhaps you have your router set such that it only accepts "X" number of computers on the network, with your new computer being X+1; thus the router not allowing your computer to be on. Also, perhaps you have MAC address filtering such that the new MAC address of your new NIC is not accepted by the router.
Don't blame your computer.
Don't blame your computer.
iwearnosox
Lifer
Maybe his router is east coast and his computer west.
imported_Phil
Diamond Member
RTFM?
rh71
No Lifer
Whenever you get a 169.x.x.x address, you need to make sure you are performing the proper boot sequence... modem --> router --> PC. Make sure you give it at least 30 seconds in between. Turn everything off and reset what you can... then back on in that order with time in between.
Alternatively, if this still doesn't work, you can assign a static private IP to your NIC instead of using DHCP (where it is apparently failing now). Just gotta make sure your router has acquired an IP from the modem.
EDIT>> First thing's first... make sure device manager isn't showing any problems with your NIC. Make sure the drivers are good.
Alternatively, if this still doesn't work, you can assign a static private IP to your NIC instead of using DHCP (where it is apparently failing now). Just gotta make sure your router has acquired an IP from the modem.
EDIT>> First thing's first... make sure device manager isn't showing any problems with your NIC. Make sure the drivers are good.
FoBoT
No Lifer
its a networing issue
you aren't getting an IP from your router
it is either the router not giving one to the PC or the PC isn't asking the router for it
set you IP statically to an IP not in use that is in the correct range for your LAN environement
if it works/you can ping the router's IP , then the problem is that the router isn't giving you a DHCP IP
if you can't ping the router, then it is your NIC or something wrong with your PC , you can delete the network connection in windows and recreate it, this sometimes corrects these issues
also check the cable, but you shirley did that first 😉
you aren't getting an IP from your router
it is either the router not giving one to the PC or the PC isn't asking the router for it
set you IP statically to an IP not in use that is in the correct range for your LAN environement
if it works/you can ping the router's IP , then the problem is that the router isn't giving you a DHCP IP
if you can't ping the router, then it is your NIC or something wrong with your PC , you can delete the network connection in windows and recreate it, this sometimes corrects these issues
also check the cable, but you shirley did that first 😉
rh71
No Lifer
As stated above, on your router settings, check that the number of DHCP machines allow room for one more to get assigned. Otherwise, assign a static IP and see if that works. If not, you need to check the cables.. or else reinstall your network adapter (through device manager). It doesn't hurt to power down the machine once more and leave it off a bit either... then try again.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 25K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 24K
-
-
