Skip to main content

Today's Problem (Updated: 5/1/2020): "My Netgear Extender Won't Work with My Xfinity Router Anymore!"



So I was tinkering in the Router settings of my Xfinity router, looking at the things that could be done. I do admit that I changed some settings (mainly the ones that release the DHCP every day instead of every week).


All this tinkering has somehow bricked my Wi-Fi extender, Netgear WN3000RPv3

  • It can connect to my main router (Xfinity), but Xfinity is no longer passing the data to it.
  • It can be pinged.
  • When I connect to it, I can ping other sites.
  • It loads my Bing splash page and the list of news articles, but not the actual articles when I click them. Maybe a cache issue there? 
  • The issue is actually with my personal laptop, the Lenovo ThinkPad. Other devices can use it as intended. Good to narrow it down that way. 
  • The LED indicating connectivity to the device is amber. The LED indicating connectivity to the Router is green.

What did I do before contacting Comcast?

I reset the extender back to factory settings.
I power cycled both devices.
I did ipconfig /release and ipconfig /renew, and felt like Cardcaptor Sakura.
I reset my machine.
ARP Flush (Thank you, Ren Beckford, for the suggestion!)

When we narrowed it down to my device, Comcast wiped their hands of the problem. No hate, I understand why.

Nothing has worked to solve it permanently. Does anyone have any suggestions?

UPDATE MARCH 22ND

I had to enable a rule in my Firewall;


The Domain version was not active. My guess is my computer registers the Extender as another domain connected in the same network.

UPDATE 4/16 -

After finding an old laptop and attempting to connect it to the hotspot, it said 'Nope. Not today. Not doing it.' and kicked off everybody, including my main machine as well.

That machine is a 2010-esque HP laptop.
It's been disconnected from hotspots.
I'm poking through firewall rules yet again.

 

5/1/2020

 

It works again, though I haven't tried to connect that dinosaur of a laptop back. No real need for it, I predict it's simply too outdated. I could find some more wireless card drivers, but I have other, newer computers to work with.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

 If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return.   In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an...

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that ...