NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
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.
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.
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
Huskynut20 wrote: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.
This is really strange. My Orbi has the "Enable Telnet" box checked. (When I check the box, I notice that the web page "refreshes".) There is no "Apply" button.
When I PuTTY telnet or use the Windows telnet into the Orbi I see this:
====================LOGIN=========================
Please enter account and password!!
==================================================PuTTY definitely has Port 23 defined. On Windows telnet, I do not put anything besides the IP address, i.e. 192.168.1.1.
I typically use a wired connection, but I just checked a WiFi connection (Linux PuTTY) and it worked as well.
If there is a session "timeout" that indicates to me that the IP address is incorrect. Is this being done by IP address or DNS name (i.e. orbilogin.net)? (Hint: as an "Old Fart", I use IP address 90% of the time.)
"Remote Management" has nothing to do with telnet access. Remote Management is only through the WAN port.
So it turns out:
- Both Orbi and my ISP router were configured as DHCP servers. The IP address I was trying on the Orbi for telnet was the address assigned to the Orbi by my ISP router. That address worked fine for everything... except Telnet.
- Orbi defaults to a local address of 192.168.1.1 This address was unreachable to my client, even when my client was plugged directly into the Orbi
- I disabled DHCP on the Orbi, then moved it's primary address onto an unused subnet. When I telnet to this new address - voila! Telnet springs into life
- I'm on the edge of my knowledge here, but suspect the way the subnets were being bound to the interfaces meant my telnet packets were being routed out a different i/f to the one I was on
tl;dr - telnet working. I changed the region to AU via command line and the web interface has sprung into life as the other threads indicated
Thanks very much for the moral support to fight through to getting it working. I would certainly have given up before sussing it out without it that help!
Andrew
