The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
Via Twitter I've seen that a recent Windows 10 Update was causing problems for some Windows 10 users - this was good timing for me!
The Update introduced a bug with DHCP (Dynamic Host Configuration Protocol) which meant some PCs couldn't connect to the internet.
I visited a client today (for other things) who was pleased to see me as two out of his three W10 PCs couldn't get online.
There was an exclamation mark over the network icon denoting that their local network may work but there was no internet access.
Thanks to the info I had read earlier I was able to quickly get them online by adding some manual IP/DNS settings.
Microsoft's official advice is to try Restarting (not Shutting Down) the PC. There is a fix (via Windows Update) doing the rounds if you can get online to get it!
Here's a Microsoft forum post Problems connecting to the internet. It's been viewed around 90,000 times as I write this so I guess it's hitting a lot of people!
[s]Hmmm...[/s]
Via Twitter I've seen that a recent Windows 10 Update was causing problems for some Windows 10 users - this was good timing for me!
The Update introduced a bug with DHCP (Dynamic Host Configuration Protocol) which meant some PCs couldn't connect to the internet.
I visited a client today (for other things) who was pleased to see me as two out of his three W10 PCs couldn't get online.
There was an exclamation mark over the network icon denoting that their local network may work but there was no internet access.
Thanks to the info I had read earlier I was able to quickly get them online by adding some manual IP/DNS settings.
Microsoft's official advice is to try Restarting (not Shutting Down) the PC. There is a fix (via Windows Update) doing the rounds if you can get online to get it!
Here's a Microsoft forum post Problems connecting to the internet. It's been viewed around 90,000 times as I write this so I guess it's hitting a lot of people!
[s]Hmmm...[/s]
Haven't had any calls that relate to this either, so it does seem to be rather few out of a potentially large group that were affected.
Yup, saw roughly the same report a day or two ago on a different news feed, and our systems team circulated the details yesterday. It reads as if the majority should be at least seeing some problems, either temporarily or permanently, nevertheless, we actually don't seem to be seeing a whole lot of issues here, and I personally have not seen any at all.
Four machines and a tablet in my house, all updated fully, none with problems. Dozens of others around my family, also no issues (I'd know 'cos I always get a call!).
Beginning to think I am Mr. Lucky after all...
chasfh wrote:
Yup, saw roughly the same report a day or two ago on a different news feed, and our systems team circulated the details yesterday. It reads as if the majority should be at least seeing some problems, either temporarily or permanently, nevertheless, we actually don't seem to be seeing a whole lot of issues here, and I personally have not seen any at all.
Four machines and a tablet in my house, all updated fully, none with problems. Dozens of others around my family, also no issues (I'd know 'cos I always get a call!).
Beginning to think I am Mr. Lucky after all...
Guess you didn't read this post then
Yup, saw it, read it, and as I said, we are not seeing a whole lot of issues here (so... just you then, posting on here...) and I haven't seen any at all (so none of my machines, none of our work machines, none of my family - you get the idea).
Thought I was fairly clear on that:-)
Also many PCs have manually set IP/DNS, these wouldn't be affected.
But as it's a bug some see it some don't - MS were saying a Restart (or two) should recover things if the service (CDPSVC) doesn't crash.
I'm currently downloading today's fix: KB3206632
[s]Hmmm...[/s]
Hmmm... wrote:
It all depends on which build machines are currently on as to whether they saw the issue or got the buggy update. I still see PCs that haven't had the Anniversary Update yet!
Also many PCs have manually set IP/DNS, these wouldn't be affected.
But as it's a bug some see it some don't - MS were saying a Restart (or two) should recover things if the service (CDPSVC) doesn't crash.
I'm currently downloading today's fix: KB3206632
[s]Hmmm...[/s]
All of mine are latest build, all fully up to date, as are the ones at work. Entirely why I mentioned it. Plus, working here, you'd have thought we'd be getting at least a few calls relating to the problem, but so far, none...
chasfh wrote:
All of mine are latest build, all fully up to date, as are the ones at work. Entirely why I mentioned it. Plus, working here, you'd have thought we'd be getting at least a few calls relating to the problem, but so far, none...
Yep - as we've mentioned it doesn't get everyone.
If a household has a few internet devices and only a W10 PC stops connecting with this error (no IP) then it wouldn't be my first thought to contact the ISP. If the router, phones, tablets, other PCs etc. were all fine then most people would be right in thinking it's not their ISP but a local problem as in this case. So would either troubleshoot it themselves or get their IT man/girl in!
[s]Hmmm...[/s]
Hmmm... wrote:
Yep - as we've mentioned it doesn't get everyone.
If a household has a few internet devices and only a W10 PC stops connecting with this error (no IP) then it wouldn't be my first thought to contact the ISP. If the router, phones, tablets, other PCs etc. were all fine then most people would be right in thinking it's not their ISP but a local problem as in this case. So would either troubleshoot it themselves or get their IT man/girl in!
[s]Hmmm...[/s]
That'd be a first in my experience, you'd be surprised what people call us about...
Get your point, although it does seem a little odd that we've had literally no calls relating to this.