If I try to connect a device to the router via ethernet cable, whether it be a laptop or another device, I cannot connect to the internet using that wired device.
The Nighthawk app lists the wired device in the 'Device Manager' section, and shows a connection with a green light.
Several minutes spent looking for this thing in Google throws up a messy set of links, but no clear result that tells me if this is a modem or a modem/router.
Does it have more than one LAN port?
If this is an Australian NBN thing, the source of more grief here than makes sense, you might get quicker help from a local source of wisdom.
The modem is an Australian NBN thing. However, when I use my old TP-Link router connected to the Modem, there is no problem with wired devices accessing the internet. It's all very strange. This suggests to me that there is an issue with the router.
and saying its a nbn thing is basically saying its an "australian internet thing". Its tells us nothing.
NBN is national broadcast network for austalian. It could be dsl, it could be fiber, it could be cable. the only thing it tells us is that you're in australia.
the Netcomm ndd-0300 has its own integrated wireless from what I could find. that'd indicate it has its own routing functions and puts you in a double nat.
> [...] I cannot connect to the internet using that wired device.
What's the IP address of "that wired device"? (Is "that wired device" using DHCP to get its IP parameters?) Of the WAN/Internet interface of the RAX120? (ADVANCED > ADVANCED Home : Internet Port : Internet IP Address)
"cannot" is not a useful problem description. It does not say what you did. It does not say what happened when you did it. As usual, showing actual actions (commands) with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations.
A bad (manual?) DNS configuration can cause various problems even when basic Internet connectivity is good, for example.
> tp-link tends to tolerate double nats better.
Or, there is no double-NAT here.
> the Netcomm ndd-0300 has its own integrated wireless from what I could > find.
Thanks for the helpful link. I know nothing, but I got a different impression from:
Look for "A compatible Wi-Fi gateway". But documentation does seem sparse.
> [...] That's a great suggestion.
Perhaps. My money would be elsewhere. (But what do I know?)
> [...] how can I easily work out what the new IP address of the router > will be [...]
When configured as a wireless access point, a typical Netgear router will, by default ("Get dynamically from existing router"), get its new/different LAN IP address using DHCP (typically from the DHCP server in the main router). If you want it to get some specific (memorable?) address, then you can normally reserve an address for it on that DHCP server.
Of course, if the NDD-300 does not include a router, then the RAX120-as-WAP would try to get its address (et al.) from your ISP, which would be unlikely to work well.
Visit http://netgear.com/support , put in your model number, and look for Documentation. Get the User Manual (at least). Read. Look for "Set Up the Router as a WiFi Access Point".
> [...] (so I can login and change the settings back if it doesn't > work)?
The Reset button can be useful in such situations.
I have attempted to set up the RAX120 router as an access point and it was unsuccessful as none of my devices could connect to the router. I ended up having to do a hard reset of the router.
I have attempted to set up the RAX120 router as an access point and it was unsuccessful as none of my devices could connect to the router. I ended up having to do a hard reset of the router.
There's a lot of flailing around going on here. I'd go back to basics.
How about talking to people who are deep into NBN things?
> I have attempted to set up the RAX120 router as an access point and it > was unsuccessful [...]
At least one of us is not amazed. Still a bunch of pending questions. Look for "?", above. (But, regarding "attempted" and "unsuccessful", see "not a useful problem description [...]", above.)
> [...] I cannot connect to the internet using that wired device.
Does that mean that wireless devices _can_ get Internet access, or that you haven't tried a wireless device, or what? Vague problem descriptions tempt readers to make assumptions. Often poor ones.
If wireless devices work, and a wired device does not, but the wired device is shown in the router's Attached Devices report, then I'd tend to blame the client device rather than the router.
> There's a lot of flailing around going on here. I'd go back to basics.
There is, and so would I, but my definition of "basics" starts with a less ambiguous problem description, and answers to the pending questions. Taking the same sloppy problem description to different forums is not how I would proceed.
All devices, when connected wirelessly to the router, are able to connect to the internet.
Any device connected to the router through ethernet is not able to access the interent through a browser. Each of the wired devices are shown in the router's Attached Devices report.
I have tried an ethernet connection with my iMac, Macbook, Macbook Pro, and Dell laptop (each of which have no problem when connected wirelessly).
Each of these devices are able to access the internet when they are connected via ethernet to my old TP-Link Archer VR1600v router.
There's a lot of flailing around going on here. I'd go back to basics.
How about talking to people who are deep into NBN things?
How is it an NBN thing when another cheaper and inferior router works just fine?
I came here to seek the assistance of Netgear equipment experts.
Your call, but that's not always the best approach.
These issues are often a subtle mixture of the equipment (Netgear in this case) and the (unknown) Internet service provider.
In this case, we are talking about NBN. That is a rat's nest of many ISPs with different network technologies.
From the message traffic here, we get plenty of problems from NBN users. But they vanish as soon as they get their problems sorted. Or maybe they just give up and jump ship.
I'd guess that a decent NBN forum would have more Netgear knowledgeable users that there are NBN experts here. Let's face, you are in Oz and seem to have gaps in your understanding of how NBN works.
And as you can see, even the "Netgear experts" are at odds when it comes to different brands of router. I linked to an information source about all things NBN.
But by all means feel free to continue to flail around.
Or do as suggested and deal with outstanding questions.
> If wireless devices work, and a wired device does not, but the wired > device is shown in the router's Attached Devices report, then I'd tend > to blame the client device rather than the router.
Still true. With my weak psychic powers, I still can't see the network configuration on any of those wired devices.
> [...] Each of these devices are able [...]
Can't see the network configuration on any of those wired devices when they're connected to that router, either.
> [...] Still a bunch of pending questions. Look for "?", above. [...]
Still waiting on that.
There could be a problem with the router, but without more information than "not able", there's little which anyone can do beyond blind guessing. (Or worse.)
