View Single Post
  #11  
Old January 19th 18, 10:18 PM posted to alt.windows7.general
Char Jackson
external usenet poster
 
Posts: 10,449
Default Win 8.1: DHCP no longer getting an IP address

On Fri, 19 Jan 2018 15:03:46 -0600, VanguardLH wrote:

NY wrote:

"Char Jackson" wrote in message
...
On Fri, 19 Jan 2018 12:31:07 -0600, VanguardLH wrote:

If did any other tweaking of the router beyond the wifi passwords, like
using MAC or IP filtering as to which devices are allowed to connect to
the router, or port forwarding, or changing the security level of its
firewall, you might want to reset the router, just reenter the same wifi
passwords in the router, and retest the IoTs that couldn't connect
before but would now use a default config in the router. Rebooting or
restarting the router is not the same as a reset of the router.

MAC filtering is a good tip. That would cause what they're seeing.


Fair point. But the user said everything was working perfectly until a few
days ago when it suddenly stopped, possibly after a Windows update. He
wouldn't know how to access the router to set up MAC filtering.


The point was to reset the router/modem back to factory defaults and
only reenter the wifi passwords back into the router (so the IoTs don't
have to each have their wifi password changed).


I believe he said he tried tethering to another access point, (a cell
phone?), so if the issue isn't limited to the router I'd be inclined to
rule out said router. If multiple AP's cause the issue, it's more likely
to be in the client.

--

Char Jackson
Ads