No valid ip at startup

[LaLiLuLeLo]

About 95% of the time I find that my LAN connection doesn't correctly acquire an ip address at startup. I'm able to solve this easily by renewing ip but its pretty annoying because I have to do this extra step each time I turn on my computer. Anyone know why this is happening exactly?

 

Thank you.

[Lurick]

Just now, LaLiLuLeLo said:

About 95% of the time I find that my LAN connection doesn't correctly acquire an ip address at startup. I'm able to solve this easily by renewing ip but its pretty annoying because I have to do this extra step each time I turn on my computer. Anyone know why this is happening exactly?

 

Thank you.

What router do you have?

Do you have any static addresses set on the network?

[ttam]

Open network and sharing

On the right click Change adapter settings

Right click your connection, go to properties

Click Internet Protocol Version 4 and click Properties

 

Just make sure Obtain IP address automatically is checked in there

[Master Disaster]

1) Run a command prompt as admin

2) Enter

netsh winsock reset

and press enter

3) Reboot

[LaLiLuLeLo]

3 hours ago, Lurick said:

What router do you have?

Do you have any static addresses set on the network?

Its one provided by my ISP. In the configuration page it says ADB (model-VV2222), so I presume thats the manufacturer. Static IP.

[LaLiLuLeLo]

7 hours ago, ttam said:

Open network and sharing

On the right click Change adapter settings

Right click your connection, go to properties

Click Internet Protocol Version 4 and click Properties

 

Just make sure Obtain IP address automatically is checked in there

Yes, I already checked that. Its on auto, both IP and DNS. Only time I changed it was to connect my laptop for some large file transfers, but I made sure everything was back to the way it was after that.

[LaLiLuLeLo]

6 hours ago, Master Disaster said:

1) Run a command prompt as admin

2) Enter

netsh winsock reset

and press enter

3) Reboot

Did it and after some testing it looks like the problem is gone. I hope it says that way. Thank you so much.

 

I did some research and I found that this command basically uninstalled all Winsock LSP's and returns Winsock to its clean state. I'm not going to pretend I understand what that means but I did see that problems with LSP's can arise from Spyware, adware or malware. I never found anything with MalwareBytes or Windows Defender though. Could there have been some other reason?

[0x1e]

1 hour ago, LaLiLuLeLo said:

Did it and after some testing it looks like the problem is gone. I hope it says that way. Thank you so much.

 

I did some research and I found that this command basically uninstalled all Winsock LSP's and returns Winsock to its clean state. I'm not going to pretend I understand what that means but I did see that problems with LSP's can arise from Spyware, adware or malware. I never found anything with MalwareBytes or Windows Defender though. Could there have been some other reason?

It's not the full answer but LSP is like a table for a directory. Some things can corrupt this, either software, hardware and also user error.

The LSP is contained within the drivers, so lets say Realtek and Intel will handle their LSP differently so one may be better than the other. So far Intels is the best for consumers.

I used to use a Killer2100 NIC and it's LSP was complete trash and always got corrupted because the NIC always wrote to it wrong which meant a constantly reinstall / flush of the LSP for a clean one.

[LaLiLuLeLo]

15 hours ago, 0x1e said:

It's not the full answer but LSP is like a table for a directory. Some things can corrupt this, either software, hardware and also user error.

The LSP is contained within the drivers, so lets say Realtek and Intel will handle their LSP differently so one may be better than the other. So far Intels is the best for consumers.

I used to use a Killer2100 NIC and it's LSP was complete trash and always got corrupted because the NIC always wrote to it wrong which meant a constantly reinstall / flush of the LSP for a clean one.

I see, I even tried updating all drivers, including LAN, when I started having this issue, with no success. I use the onboard LAN, so no NIC. By the way, it happened again. I think it happens more when I boot up after a long gap. Never happens on reboots or startup after a short break. This is so annoying. 

 

[0x1e]

On 10/22/2017 at 12:42 PM, LaLiLuLeLo said:

I see, I even tried updating all drivers, including LAN, when I started having this issue, with no success. I use the onboard LAN, so no NIC. By the way, it happened again. I think it happens more when I boot up after a long gap. Never happens on reboots or startup after a short break. This is so annoying. 

 

It could be, but it's a long shot that it's your OS that is causing the problem if a driver install doesn't fix it.

Your OS does all the internet. Every single webpage, online game and download has to be handled by the OS and subsequently it also handles the LSP.

 

The networking portion of computers is complicated because it's new tech built on top of legacy technology which has created far too many layers to keep track of. Especially with Windows as they want to keep as many old systems operational as possible.

 

However if you've got patience then you can track down what is actually causing this. There must be a pattern to it if it only happens sometimes. Find the pattern to find the program, then kill the program. 

[LaLiLuLeLo]

15 hours ago, 0x1e said:

It could be, but it's a long shot that it's your OS that is causing the problem if a driver install doesn't fix it.

Your OS does all the internet. Every single webpage, online game and download has to be handled by the OS and subsequently it also handles the LSP.

 

The networking portion of computers is complicated because it's new tech built on top of legacy technology which has created far too many layers to keep track of. Especially with Windows as they want to keep as many old systems operational as possible.

 

However if you've got patience then you can track down what is actually causing this. There must be a pattern to it if it only happens sometimes. Find the pattern to find the program, then kill the program. 

Ok, so the pattern is that it happens exclusively after a long downtime. Overnight. Looking around my router settings I noticed DHCP lease time. It's at 12h 4mins. Could this be the problem? I doubt it because I've never changed the router's setting and I've never had this issue but maybe it could be a temporary fix. It is even safe to make this unlimited?

 

As far as programs go, I have installed only a few recently. A streaming service plugin, Tunnelbear, Dropbox, all the drivers except intel graphics, and Spybot Anti-Beacon to block Windows 10 telemetry. How do you suggest I pinpoint which program it could be? Only way I can think of is uninstall one by one. 

[0x1e]

11 hours ago, LaLiLuLeLo said:

Ok, so the pattern is that it happens exclusively after a long downtime. Overnight. Looking around my router settings I noticed DHCP lease time. It's at 12h 4mins. Could this be the problem? I doubt it because I've never changed the router's setting and I've never had this issue but maybe it could be a temporary fix. It is even safe to make this unlimited?

 

As far as programs go, I have installed only a few recently. A streaming service plugin, Tunnelbear, Dropbox, all the drivers except intel graphics, and Spybot Anti-Beacon to block Windows 10 telemetry. How do you suggest I pinpoint which program it could be? Only way I can think of is uninstall one by one. 

Changing the DHCP time wouldn't have any real effect if you change it. So there's no harm in making it unlimited as it's only a home network. If you had it in a business environment then it would be different. Also, DHCP time is 1/2 of what's set. Yours is 12 hours but it will begin to request a new IP after 6 hours. Those extra 6 hours is a buffer encase the first request wasn't completed. It's always half. So 12, 6, 3, 1.5....

 

It could be (a long shot)  your router is not updating your IP when your machine is off (which is should), and when you turn your machine on you have to wait X amount of time for Windows to send a new request. So increase the wait time and see if the problem takes longer to surface. If it does then I would first reset the router (power cycle it) and if that doesn't work then just set it as unlimited.

Some routers do gain problems over time. I've had a few as my ISP pushes down updates over the line without me even knowing.

[LaLiLuLeLo]

18 hours ago, 0x1e said:

Changing the DHCP time wouldn't have any real effect if you change it. So there's no harm in making it unlimited as it's only a home network. If you had it in a business environment then it would be different. Also, DHCP time is 1/2 of what's set. Yours is 12 hours but it will begin to request a new IP after 6 hours. Those extra 6 hours is a buffer encase the first request wasn't completed. It's always half. So 12, 6, 3, 1.5....

 

It could be (a long shot)  your router is not updating your IP when your machine is off (which is should), and when you turn your machine on you have to wait X amount of time for Windows to send a new request. So increase the wait time and see if the problem takes longer to surface. If it does then I would first reset the router (power cycle it) and if that doesn't work then just set it as unlimited.

Some routers do gain problems over time. I've had a few as my ISP pushes down updates over the line without me even knowing.

Ok, I'll try setting it to unlimited for now. I have hard reset the router a few times already but it didn't change anything. Funny thing is this is a relatively new router, the old one worked perfectly for 6-7 years (shitty 5 mbps connection but still, it always worked).

 

Thanks for the help.

[LaLiLuLeLo]

On 10/25/2017 at 12:36 AM, 0x1e said:

Changing the DHCP time wouldn't have any real effect if you change it. So there's no harm in making it unlimited as it's only a home network. If you had it in a business environment then it would be different. Also, DHCP time is 1/2 of what's set. Yours is 12 hours but it will begin to request a new IP after 6 hours. Those extra 6 hours is a buffer encase the first request wasn't completed. It's always half. So 12, 6, 3, 1.5....

 

It could be (a long shot)  your router is not updating your IP when your machine is off (which is should), and when you turn your machine on you have to wait X amount of time for Windows to send a new request. So increase the wait time and see if the problem takes longer to surface. If it does then I would first reset the router (power cycle it) and if that doesn't work then just set it as unlimited.

Some routers do gain problems over time. I've had a few as my ISP pushes down updates over the line without me even knowing.

Unlimited DHCP lease time seems to have done the trick. First time its connected properly after a long break.

[johnukguy]

You say it happens after downtime, are you letting the PC sleep or turning it off? I'd suggest disabling sleep/hibernate states and actually turning the system off instead.

[LaLiLuLeLo]

On 10/27/2017 at 5:23 AM, johnukguy said:

You say it happens after downtime, are you letting the PC sleep or turning it off? I'd suggest disabling sleep/hibernate states and actually turning the system off instead.

It was happening after a proper shutdown. I never sleep/hibernate. I found that it was happening after DHCP lease time expired. For now I have solved it by setting DHCP lease time to unlimited but I'm pretty sure thats not the root cause. The problem would surely show up again if I set it back to default. No idea whats causing it. But atleast I don't have to manually renew IP everytime now.

[johnukguy]

Did you contact your ISP and ask them why your DHCP is behaving this way? They ultimately have control at their end and it sounds like something isn't configured correctly there. If you get someone reading from a script when you call them, ask them to elevate the issue.

[LaLiLuLeLo]

On 11/6/2017 at 1:07 AM, johnukguy said:

Did you contact your ISP and ask them why your DHCP is behaving this way? They ultimately have control at their end and it sounds like something isn't configured correctly there. If you get someone reading from a script when you call them, ask them to elevate the issue.

Haven't heard back from them unfortunately. I guess I'll have to contact them again. It does sound like a problem on their side because I always had the same settings before and this never happened.

[LaLiLuLeLo]

On 11/6/2017 at 1:07 AM, johnukguy said:

Did you contact your ISP and ask them why your DHCP is behaving this way? They ultimately have control at their end and it sounds like something isn't configured correctly there. If you get someone reading from a script when you call them, ask them to elevate the issue.

Problem seems to have been fixed now. I tested again with my default setting of 12h  DHCP lease time and now it works properly, like it used to. Like @0x1e said, an ISP update probably caused this and I'm guessing another silent update from my ISP fixed it. 

[johnukguy]

Good to know. Thanks for letting the group know.