Question Only have network connection after restart pc

[Kilo702]

Hi all,

I've been having some trouble with the network connection on my pc
When I turn my pc on, all the software and peripherals seem to work just fine, but it can't connect to my internet network. Only after restarting my pc (with the windows 'restart' button), it connects after about 30 seconds.

When it is connected, my internet speed is completely fine.
I've tried the Windows troubleshooter, multiple different ethernet cables and flushed the dns but they all haven't worked (flushing DNS worked once though I think that was just a coincidence).

To summarize:
PC on = no internet --> PC restart --> PC has restarted successfully --> wait ≈ 30 seconds more --> PC connected to the internet!

Could it be hardware, BIOS, DNS or anything else related? How can I fix this?
Thanks in advance!

Kilo702 (I'm on Windows 11, no WiFi)

 

[bill001g]

try IPCONFIG /all and see the status of the port. Is it disconnected. Does it have a IP or is it using something that starts with 169.x.x.x

You could also try ipconfig /release ipconfig /renew

 

[Kilo702]

try IPCONFIG /all and see the status of the port. Is it disconnected. Does it have a IP or is it using something that starts with 169.x.x.x

You could also try ipconfig /release ipconfig /renew

I've tried ipconfig /release & renew, both haven't really done anything as far as I know (in fact, - /renew crashed my command prompt somehow?)


The results of the ipconfig /all -->
https://linksharing.samsungcloud.com/latBrCT65bzn

IP starts with 169 so there's a problem there. Gateway can't be found.
I've checked my router: when connecting my laptop to it with a cable, it works fine.

That's kind of where my network connection knowledge stops..

 

[bill001g]

This is a dhcp problem. Since other devices work it is not likely a router issue but the router is what is giving you the IP.

This is something blocking the dhcp messages but I am surprised that upconfig /renew does not fix it.

If you want the lazy way out you can just go into the IPv4 settings on your nic and put in a fixed value. You could copy the info from your post where you say it works but you run the risk of the router giving out the IP to another device if you computer happens to be offline.
I would use 192.168.1.250. Very technically you want a IP outside the scope of the dhcp server on the router. If your router start giving out addresses at 200 it likely will never get to 250.

This does not actually fix the problem it more hides it. It would likely be some driver issue or maybe some power save option. Not sure normally DHCP works very well.

 

[Ralston18]

The No network connection screen is showing a subnet mask of 255.255.0.0

Not what I would expect. Most likely the subnet mask should be 255.255.255.0.

As is shown in the "After restart" ipconfig /all.

So what happens during the restart to enable the network adapter and obtain a DHCP IP address = ?

All I can think of is that the network adapter is "cold" when the system first boots and fails. Hence the default 169. 254.13.266 Autoconfiguration IPv4 address along with the corresponding default subnet 255.255.0.0

Once the network adapter is physically warmed up a bit some loose connection tightens up and connectivity is changed. Router then "sees" the network adapter and issues a DHCP IP address.

You can test that by just being aware of how long the PC needs to be off (and cool down) between restarts that fail and restarts that succeed.

Also look in Reliability History and Event Viewer. Either one or both may be capturing some error code, warning, or informational event that you can match to the failed connection attempts.

 

[alceryes]

The No network connection screen is showing a subnet mask of 255.255.0.0

This is normal. It's due to the APIPA assignment.

 

[alceryes]

Hi all,

I've been having some trouble with the network connection on my pc
When I turn my pc on, all the software and peripherals seem to work just fine, but it can't connect to my internet network. Only after restarting my pc (with the windows 'restart' button), it connects after about 30 seconds.

When it is connected, my internet speed is completely fine.
I've tried the Windows troubleshooter, multiple different ethernet cables and flushed the dns but they all haven't worked (flushing DNS worked once though I think that was just a coincidence).

To summarize:
PC on = no internet --> PC restart --> PC has restarted successfully --> wait ≈ 30 seconds more --> PC connected to the internet!

Could it be hardware, BIOS, DNS or anything else related? How can I fix this?
Thanks in advance!

Kilo702 (I'm on Windows 11, no WiFi)

Please describe the physical topology. Is it ethernet cable out of your NIC into the wall and then from the wall to the router on the other side? Any other devices in the middle?

When you have no network are there any lights on on your NIC?

 

[Ralston18]

This is normal. It's due to the APIPA assignment.

Agree.

"Hence the default 169. 254.13.266 Autoconfiguration IPv4 address along with the corresponding default subnet 255.255.0.0"

What I am wondering about is the cause of that 169. assignment.

I had not thought about the problem being further along in the cables, wall outlets, etc.. Or other devices. May well be but my sense is that those sort of infrastructure problem(s) would not stop with a restart.

Good point. Thanks.

 

[Kilo702]

Hi, thanks for all the help and ideas!
I've fixed the problem: someone wrongly put the wires in the utp port (if that's it's name) in the wall (white green / green / white orange / orange); switched them around and it suddenly all works!
Only problem now, is that my pc thinks it's an 'unidentified network'. So far, windows troubleshooter seems to fix that as well.