Note sure, my customer was fixed just by doing an ipconfig /renew, A
restart didn't fix it.
On 12/27/2016 2:07 PM, That One Guy /sarcasm wrote:
im wondering if it didnt boil down to them pulling an apple and
forcing old encryptions to go away. i get a kick out of it, it freaks
out like jesus has cancer if you have wpa or wep but its cool with
connecting to random open wifi
microsoft should stop trying to be like apple, not being like apple is
the last thing microsoft has going for them to not suck as bad as apple
On Tue, Dec 27, 2016 at 2:04 PM, Nate Burke <[email protected]
<mailto:[email protected]>> wrote:
The first time i ran into this, it just happened I had a 951 at
the cutomers house, so I could see the device connect via Wifi,
but never obtain an IP Address. Weird thing was the customer said
that it was worked fine on his office wifi, so it must be
something with the way the mikrotik router is handing out DHCP?
Maybe only a handful of routers/PC combinations have the issue?
On 12/27/2016 1:59 PM, Adam Moffett wrote:
This stuff makes me want to be a jerk and eliminate tech
support. I'd install an SS as a demarc and if they think
internet doesn't work, swing by and plug laptop into the demarc.
If it works for me then I don't really care what
windows/iOS/Linksys problem they're having.
On other days I feel more altruistic.
Sorry, Ken no I have no constructive input on the problem. :)
------ Original Message ------
From: "Ken Hohhof" <[email protected] <mailto:[email protected]>>
To: [email protected] <mailto:[email protected]>
Sent: 12/27/2016 2:46:49 PM
Subject: [AFMUG] Windows 10 DHCP bug still?
Is anyone still running into customers with Windows 10 computers
that boot up with an autoconfiguration address but will get a
valid address if you Restart them? I got yet another call today
about this. Of course, customers think it’s our problem because
the symptom is “no Internet” on the affected computer.
I would have thought all computers would have the patch by now.
But I guess if the symptom is “no Internet”, the computer might
not get the update.
Annoying that this has not been better publicized. Somewhere
customers actually read, not this:
http://arstechnica.com/business/2016/12/microsoft-windows-10-dhcp-broken-update/
<http://arstechnica.com/business/2016/12/microsoft-windows-10-dhcp-broken-update/>
--
If you only see yourself as part of the team but you don't see your
team as part of yourself you have already failed as part of the team.
