Wifi doesn't have a valid IP configuration
Discussion
Quick numbskull PC question, I have googled but not found a solution I can follow
My Windows 8 laptop PC won't connect to wifi.
It was working just fine yesterday.
Router is fine as other devices connected.
I am getting the error message per title.
After googling this solution works temporarily but only until I turn PC off, have to do it each time I turn PC on
go to command prompt
type ipconfig /release
type ipconfig /renew
can someone please recommend a permanent solution
My Windows 8 laptop PC won't connect to wifi.
It was working just fine yesterday.
Router is fine as other devices connected.
I am getting the error message per title.
After googling this solution works temporarily but only until I turn PC off, have to do it each time I turn PC on
go to command prompt
type ipconfig /release
type ipconfig /renew
can someone please recommend a permanent solution
That it works when renewed suggests the DCHP server is working OK on the router so it sounds like the laptop isn't looking for a DCHP server on first boot.
Never used Win8 but assuming its similar to the rest, right click on the wifi connection, select properties, select IPv4 protocol, select properties and ensure "automatically obtain IP address" is selected. Also untick IPv6 from the wifi connection properties as it sometimes causes problems.
Never used Win8 but assuming its similar to the rest, right click on the wifi connection, select properties, select IPv4 protocol, select properties and ensure "automatically obtain IP address" is selected. Also untick IPv6 from the wifi connection properties as it sometimes causes problems.
Fore Left said:
That it works when renewed suggests the DCHP server is working OK on the router so it sounds like the laptop isn't looking for a DCHP server on first boot.
Never used Win8 but assuming its similar to the rest, right click on the wifi connection, select properties, select IPv4 protocol, select properties and ensure "automatically obtain IP address" is selected. Also untick IPv6 from the wifi connection properties as it sometimes causes problems.
Thanks - reckon I can understand that suggestion (bats?)Never used Win8 but assuming its similar to the rest, right click on the wifi connection, select properties, select IPv4 protocol, select properties and ensure "automatically obtain IP address" is selected. Also untick IPv6 from the wifi connection properties as it sometimes causes problems.
Although the PC did some timetabled switch off and refresh and seems to be working now. Bloody odd
By any chance is your router a BT Home Hub 6?
I have just swapped from Sky to BT and the HH6 is awfully erratic with the wifi and DHCP handling, despite the fact that I should be able to dangle from a helicopter 400 m above my house and still get a "reliable signal".
Am going to turn off the DHCP and wifi on the HH6 and re-instate my Asus.
I have just swapped from Sky to BT and the HH6 is awfully erratic with the wifi and DHCP handling, despite the fact that I should be able to dangle from a helicopter 400 m above my house and still get a "reliable signal".
Am going to turn off the DHCP and wifi on the HH6 and re-instate my Asus.
If your router is set up for DHCP then it will assign devices on your network an IP address, something like 192.168.0.24. if your machine cannot get an IP address from the network it usually assigns itself one along the lines of 169.xxx.xxx.x - so its fairly easy to tell whats happening.
Most routers can be configured to assign a range of IP addresses, since the router is usually 192.168.0.1 they will be from something like 192.168.0.2 to 192.168.0.256 say.
Now, its possible to restrict what IP addresses are available from the router, say 192.168.0.2 to 192.168.0.50 in which case only 49 IP addresses are available, then the router runs out. Depending on how long your router reserves that IP address (the lease period) you may find that you run out.
eEVERY device has a separate IP address, every phone, every computer, apple watch,, sky box, anything that uses your network, so you'll be surprised how quickly they run out. If you have more than 255 devices (unlikey) then you can expand the subnet which should default to 255.255.255.0 - but I wouldn't worry about that for now.
Log in to your router and dig around for the DHCP settings and put up a screenshot.
Most routers can be configured to assign a range of IP addresses, since the router is usually 192.168.0.1 they will be from something like 192.168.0.2 to 192.168.0.256 say.
Now, its possible to restrict what IP addresses are available from the router, say 192.168.0.2 to 192.168.0.50 in which case only 49 IP addresses are available, then the router runs out. Depending on how long your router reserves that IP address (the lease period) you may find that you run out.
eEVERY device has a separate IP address, every phone, every computer, apple watch,, sky box, anything that uses your network, so you'll be surprised how quickly they run out. If you have more than 255 devices (unlikey) then you can expand the subnet which should default to 255.255.255.0 - but I wouldn't worry about that for now.
Log in to your router and dig around for the DHCP settings and put up a screenshot.
if the dhcp settings were at fault, it would be unlikely to affect just one device, and an renewing dhcp would be unlikely to resolve it consistently.
It may be a issue with the wifi hardware or drivers resulting in it being unable to successfully transmit or receive the initial dhcp request / response while initially connecting.
Properly diagnosing the issue would be a pain, and a fix might not even be available, but a script to release and renew is dirty.
It may be a issue with the wifi hardware or drivers resulting in it being unable to successfully transmit or receive the initial dhcp request / response while initially connecting.
Properly diagnosing the issue would be a pain, and a fix might not even be available, but a script to release and renew is dirty.
LotusMartin said:
If your router is set up for DHCP then it will assign devices on your network an IP address, something like 192.168.0.24. if your machine cannot get an IP address from the network it usually assigns itself one along the lines of 169.xxx.xxx.x - so its fairly easy to tell whats happening.
Most routers can be configured to assign a range of IP addresses, since the router is usually 192.168.0.1 they will be from something like 192.168.0.2 to 192.168.0.256 say.
Now, its possible to restrict what IP addresses are available from the router, say 192.168.0.2 to 192.168.0.50 in which case only 49 IP addresses are available, then the router runs out. Depending on how long your router reserves that IP address (the lease period) you may find that you run out.
Every device has a separate IP address, every phone, every computer, apple watch,, sky box, anything that uses your network, so you'll be surprised how quickly they run out. If you have more than 255 devices (unlikely) then you can expand the subnet which should default to 255.255.255.0 - but I wouldn't worry about that for now.
Log in to your router and dig around for the DHCP settings and put up a screenshot.
Thanks for the explanation, probably have 20+ devices including friends who have used my wifi in the pastMost routers can be configured to assign a range of IP addresses, since the router is usually 192.168.0.1 they will be from something like 192.168.0.2 to 192.168.0.256 say.
Now, its possible to restrict what IP addresses are available from the router, say 192.168.0.2 to 192.168.0.50 in which case only 49 IP addresses are available, then the router runs out. Depending on how long your router reserves that IP address (the lease period) you may find that you run out.
Every device has a separate IP address, every phone, every computer, apple watch,, sky box, anything that uses your network, so you'll be surprised how quickly they run out. If you have more than 255 devices (unlikely) then you can expand the subnet which should default to 255.255.255.0 - but I wouldn't worry about that for now.
Log in to your router and dig around for the DHCP settings and put up a screenshot.
It seems the PC has sorted itself out following the timed reboot - not sure if this occurred as a result of playing around or it fixed itself finally.
But would be interested in what you would recommend as ideal router settings for reliability - device count shouldn't exceed 255 in my lifetime (even assuming every time I get a new phone the router sees it as a new device)
Wow resurrection!
He said the his pc did a scheduled restart and it was fine. So I'd say it was mid update.
If you arent getting an IP address just make sure all your network settings are on default to get an address automatically.
Reboot your router and try again.
This is the kind of simple problem that easily gets out of hand on a forum as people chip in with lots of suggestions.
If other devices are ok, it is your pc that is at fault and just needs to be reset to default settings.
Remember though also, by "trying lots of solutions" quite often people on here make things worse.
He said the his pc did a scheduled restart and it was fine. So I'd say it was mid update.
If you arent getting an IP address just make sure all your network settings are on default to get an address automatically.
Reboot your router and try again.
This is the kind of simple problem that easily gets out of hand on a forum as people chip in with lots of suggestions.
If other devices are ok, it is your pc that is at fault and just needs to be reset to default settings.
Remember though also, by "trying lots of solutions" quite often people on here make things worse.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff