This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Re: My Nighthawk 8300 does not display an ASUS switch as an attached device
Antinode's answers here did not get me all the way to a solution, but investigating my network, I found I'd plugged part of it into an Ooma VoIP device which, it turns out, is a mini-DHCP server! Who knew?
Anyway, my wiring closet is corrected now, and a lot neater. Thanks for the patience and guidance.
Re: My Nighthawk 8300 does not display an ASUS switch as an attached device
OK, so the switch is "transparent" and doesn't show up as a device. Why do the devices behind the switch not appear? And why (when I check them) does their IP address begin with 172...etc. rather than like the rest of my network which begins with 198...?
And how do I get to ping or see (or list in the router) the devices beyond the switch from devices within the LAN or the router management screen?
Incidentally, I've tried manually setting the IPv4 addresses. That doesn't work. Ping requests to the devices when their addresses are DHCP don't work ("Request timed out"). Net view doesn't display the switch or anything behind it. As a consequence, I can't remotely display the security cameras which feed the DVR. ... But! I do have internet access on the PC and DVD player (Netflix works fine). Addresses plugged directly into the router look like 192.168.1.4 (etc.) Addresses (DHCP) behind the switch look like 172.27.35.25 (the DVR).
There are some more devices plugged into the router directly (a PC, Ooma VOIP, printer, another smart DVD player, a Pentair pool equipment controller), but the devices behind the switch are the only ones "invisible."
Re: My Nighthawk 8300 does not display an ASUS switch as an attached device
One thing more: I can't configure port forwarding on the 172.27.35.25 DVR. The management interface to the router invalidates that IP as "Must be in LAN" (saying it's not)
Re: My Nighthawk 8300 does not display an ASUS switch as an attached device
Yes, I swapped out a slightly newer switch which gave me the same result. That switch was a Trendnet TE100-55/A. These are both super-simple (super cheap) switches. I suppose I could upgrade to a nicer switch, but given the circumstances, I think you can understand my reluctance.
Re: My Nighthawk 8300 does not display an ASUS switch as an attached device
> [...] Why do the devices behind the switch not appear? And why (when I > check them) does their IP address begin with 172...etc. rather than like > the rest of my network which begins with 198...?
The easy explanation would be that there's some other router (or similar device, or, at least, another DHCP server) in your network which you're not disclosing.
Your (text) connection diagram did not survive its rendering by the forum software, so what's connected to what is still not clear. The "</>" ("Insert Code") tool might help with that.
> [...] Addresses (DHCP) behind the switch look like 172.27.35.25 (the > DVR).
I suspect that either there's some other router-like gizmo between the R8300 and the switch, or else there's some other DHCP server running on your network which is dispensing those "172.27.a.b" addresses.
You need to do some detective work. For example, disconnect the switch from the cable leading to the R8300, and connect your "a PC" to the R8300 using that cable. Does your "a PC" get a "172.27.a.b" address that way? If so, then the (disconnected) switch is not causing the problem.
If the PC gets a "192.168.1.x" address, then insert the switch again, but with only the PC (and the R8300) connected to it. I'd expect adding the switch to make no difference. But, adding your other gizmos (one at a time) to the switch might.
Blame assignment is Job One.
> [...] I can't configure port forwarding on the 172.27.35.25 DVR. The > management interface to the router invalidates that IP as "Must be in > LAN" (saying it's not)
Right. Port forwarding works only for a device on the router's LAN subnet ("192.168.1.*"). The mystery here is how anything gets an address on a different subnet.
> [...] I swapped out a slightly newer switch which gave me the same > result. [...]
I'm not amazed. An unmanaged switch is too stupid to cause this kind of trouble.
Re: My Nighthawk 8300 does not display an ASUS switch as an attached device
First of all, thanks for your patience. As you implied, another DHCP server was between the router and the switch (the Ooma VoIP device). All I can say is "D'oh!" [smacks forehead with palm].
Once that was removed as the intervening device, everything worked perfectly.
My apologies for the user error, and thanks for giving me the hint about how to diagnose a problem I'd caused myself.
Re: My Nighthawk 8300 does not display an ASUS switch as an attached device
> My apologies for the user error, [...]
No need. Glad to hear that you identified the culprit.
> [...] a problem I'd caused myself.
Someone has to cause them, and you can't always rely on others.
Similar problems have popped up here a few times, typically with wireless gizmos. Many modern Internet-of-Junk devices have a hotspot mode (including a DHCP server) which is used during its configuration. Occasionally one manages to join the LAN without disabling its own DHCP server.
General advice: Given a confusing problem in a complex arrangement, try a simpler arrangement. Divide and conquer.
Re: My Nighthawk 8300 does not display an ASUS switch as an attached device
Antinode's answers here did not get me all the way to a solution, but investigating my network, I found I'd plugged part of it into an Ooma VoIP device which, it turns out, is a mini-DHCP server! Who knew?
Anyway, my wiring closet is corrected now, and a lot neater. Thanks for the patience and guidance.
