manicdefender
New Around Here
Hi All.
I'm having a weird issue. When Win 10 gets to the login screen, it takes anywhere from 30-45 seconds for it to realize it's been issued a IP. I get the "limited or no connectivity" icon until finally it picks up it's IP address from the router. The odd thing is it's statically addressed/reserved from the router side so it should be instant. I've even gone as far as reinstalling Windows, latest drivers/BIOS etc. Windows is set to DHCP. Rebooted router etc. No obvious cause. Motherboard is a TUF-B450-PLUS GAMING
Syslog is attached. The one called syslogrebootpc.txt is where I cleared the log and then immediately restarted the PC to see whether anything obvious flagged up straight away. But I'm not sure why it's complaining about Port 3, I only use ports 1 + 2. Port 3 does have a cable in, but nothing plugged on the other end. PC is plugged into Port 1, TP-LINK switch into Port 2.
Any suggestions welcomed.
I'm having a weird issue. When Win 10 gets to the login screen, it takes anywhere from 30-45 seconds for it to realize it's been issued a IP. I get the "limited or no connectivity" icon until finally it picks up it's IP address from the router. The odd thing is it's statically addressed/reserved from the router side so it should be instant. I've even gone as far as reinstalling Windows, latest drivers/BIOS etc. Windows is set to DHCP. Rebooted router etc. No obvious cause. Motherboard is a TUF-B450-PLUS GAMING
Syslog is attached. The one called syslogrebootpc.txt is where I cleared the log and then immediately restarted the PC to see whether anything obvious flagged up straight away. But I'm not sure why it's complaining about Port 3, I only use ports 1 + 2. Port 3 does have a cable in, but nothing plugged on the other end. PC is plugged into Port 1, TP-LINK switch into Port 2.
Any suggestions welcomed.