NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SW_
Apr 29, 2019Prodigy
ORBI RBK53 Region Change
If you'd like to save some bucks and buy Orbi from Costco and bring it home outside the US, but you want to make a region change from North America to your region, try this:
1. Login to Orbi/de...
Huskynut20
Mar 28, 2020Aspirant
I've been fighting to convert my RBK40 pair from US to NZ, and this looks like the right way to go about it!
I can access the debug screen and have enabled the telnet login, but:
- if I Telnet on the default port 23, I get the connection immediately dropped
- if I Telnet on port 8443 (default admin port), the connection doesn't immediately fail like above, but it just "hangs" ie no telnet response.
Any ideas on this? It feels like so close to a solution but not quite working - sooo frustrating!
Thanks in advance.
Andrew
- CrimpOnMar 28, 2020Guru - Experienced UserThe remote admin port 8443 is for https only on the WAN port, and is not what you want. Just ordinary Telnet. I use PuTTY. Works great.
- michaelkenwardMar 28, 2020Guru - Experienced User
CrimpOn wrote:
The remote admin port 8443 is for https only on the WAN port, and is not what you want. Just ordinary Telnet. I use PuTTY. Works great.Indeed. When I wanted to migrate some Orbi stuff I simply did it in Windows. No port management involved
This is the message that bailed me out:
Re: Orbi RKB53 global differences - NETGEAR Communities
This may be the thing you have been using, but it is easy to get lost in these long and rambling discussions that cover a lot of different topics.
- Huskynut20Mar 29, 2020Aspirant
Thanks for the prompt replies - much appreciated.
I think the issues is simpler (or possibly more complicated - I can't yet tell.. ;-)
Despite checking the Enable Telnet box on the debug web page, I can't get any response from the device on Telnet. I'd have expected to get a login challenge/response, or possibly if no login required then a command prompt response, but I'm getting nothing back at all (only a session timeout after ~20 seconds of no response). The same behaviour from both telnet command in cmd window and from Putty client, so it looks like a server-side issue to me.
I can't see any "Apply" button in the debug window, so I wondered if the Enable Telnet box check setting hadn't been applied, but the Start Capture and Save Debug Log buttons seem to work correctly on click. And I've tried accessing the debug window in multiple browsers, and there's no "Apply" button on the debug screen in any of them.
The only other things I can think of:
- does Telnet access need to be via a specific interface or port on the RBR40? I've tried putting my management device on both a separate physical port direct into the RBR40, and also via a physical port on the upstream router - no joy either way. Should I try via a wifi connection to the RBR40?
- are any other settings needed to enable management and/or telnet? I've enabled Remote Management by any IP address in the Orbi Advanced Setup, and can't any other settings that might be interfering
Thanks in advance.
Andrew