Reply

Issue with connecting to admin with a Broadcom network device

mpedigo1
Aspirant

Issue with connecting to admin with a Broadcom network device

I have a R7000 Nighthawk router which I have had for a little over 2 years.   After initial setup I can't connect to administrate from one computer.  The connection is refused (

ERR_CONNECTION_REFUSED). With first setup it works fine.  I've reimaged the router several times and recently tried dd-wrt and have gotten the same issue.     The motherboard in that computer (ASUS) uses Broadcom chips for both wireless and wired networks.  It seems there may be a bug in the codebase that both Netgear and dd-wrt uses that somehow causes broadcom chipped network adapters to be rejected from administrating the R7000 in this case.  Has anybody else expereinced this?   I'm not paying for support for their bug, I'll just buy a competitive device and never use NetGear again.  This is a last ditched effort to resolve this issue.  dd-wrt is horrible with my Sony Bravia Smart TV so I'm moving back to the most current Netgear software (1.0.9.26) which played much nicer with the TV.   Ideas? 
Model: R7000|AC1900 Smart WIFI Router
Message 1 of 5
antinode
Guru

Re: Issue with connecting to admin with a Broadcom network device

> After initial setup I can't connect to administrate from one computer.
> The connection is refused (ERR_CONNECTION_REFUSED).

   You're talking about a web browser?  "[You] can't connect" from what,
exactly, connected to the R7000 how, exactly, using what, exactly, as a
URL?  When that happens, can any other client connect successfully?  Can
the (unspecified) client device where the problem is observed connect to
any other server anywhere (wnen it can't connect to the R7000)?

> [...] It seems there may be a bug in the codebase that both Netgear
> and dd-wrt uses that somehow causes broadcom chipped network adapters to
> be rejected from administrating the R7000 in this case. [...]

   Whatever that means, it wouldn't be my first guess.

> Ideas?

   Do more actual testing, and less wild speculation about a cause?

   "Connection refused" normally means that you've contacted the target
server, but no program (web server?) is listening at the target port.
It may not be likely, but it is possible that the web server in the
R7000 is dying for some reason.  That can be explored.  It's also
possible that some firewall somewhere is blocking the connection.  As
usual, many things are possible, so some actual investigation may be
needed to determine what's actually happening.

> [...] I'm moving back to the most current Netgear software (1.0.9.26)
> [...]

   Have you tried anything older, like, say, "V1.0.7.12_1.2.5"?

Message 2 of 5
mpedigo1
Aspirant

Re: Issue with connecting to admin with a Broadcom network device

Thanks for responding.  I reailzed something else.  If I leave the default subnet, it works fine.  I was using my own subnet....a class A address, but I was using a class C subnet configuraton (255.255.255.0).  I changed the network subnet configuraton to 255.0.0.0 and things are still working.  Maybe I'm a little weak on networking, so I don't understand why, but at least I can administer from all my systems now.  My last router had no issues with that configuraton.  And this one works with some of my systems with no issues.  I would consider this issue resolved.  Only took 2 years and 4 rebuilds to figure it out.

Message 3 of 5
mpedigo1
Aspirant

Re: Issue with connecting to admin with a Broadcom network device

I didn't answer your question.  I'm attaching to the gateway to administer the router.  

Message 4 of 5
antinode
Guru

Re: Issue with connecting to admin with a Broadcom network device

> [...] I was using my own subnet....a class A address, but I was using
> a class C subnet configuraton (255.255.255.0).  I changed the network
> subnet configuraton to 255.0.0.0 and things are still working. [...'

   If you're doing odd-ball stuff, then it might help if you mentioned
it.  What are/were the IP addresses of the devices which can't/couldn't
communicate?

   If you have different devices with different subnet masks, then you
can expect problems.  Unless you have more than 200 devices, I see no
reason to fool with subnet masks other than 255.255.255.0 (/24).  If I
wanted to use something else, I'd want to make very sure that the router
functions (DHCP server, and so on) handle it properly.  I'd also make
sure that every device on the LAN agrees on the (common) subnet.

> [...] Maybe I'm a little weak on networking, so I don't understand
> why, but [...]

   You're well ahead of me.  With my weak psychic powers, I have no real
idea of what your equipment is, how it's configured, how it's connected,
or what you're doing with it.

> [...] I was using my own subnet....a class A address, but I was using
> a class C subnet configuraton (255.255.255.0).  [...] My last router
> had no issues with that configuraton.

   My D7000 (V1.0.1.64_1.0.1) uses "10.0.0.*" (10.0.0.0/24), with no
trouble.  I suspect that you're misplacing blame for your problems.


> I didn't answer your question.  I'm attaching to the gateway to
> administer the router.

   You lost me.  What was the question?  You're "attaching" _what_ "to
the gateway"?  What _is_ "the gateway"?  What is "the router"?  I can
see some unanswered questions, but how this applies to them is a mystery
to me.

Message 5 of 5
Top Contributors
Discussion stats
  • 4 replies
  • 502 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 6E