NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Question about Changing Remote Management Address
Guys, I got a Question about changing Remote Management Address
I got Nighthawk Rax120 and when I trying to change the remote management setting I got a problem.
The problem is I use Nighthawk Rax120 router only for wireless network. which means nighthawk rax120 is the second level router connected to my main router. I am using Rax120 Only for wireless customer in store. I got my powerful business router which is 6 core Cpu and 8GB Ram and 500gb flash storage so I can not use Rax120 as my main router because it's performace is not enough for me. .... Ok this is the background.
Now the problem is . After I setup the nighthawk rax 120 and connect it's wan port to my main router's Lan port it got the ip: 192.168.1.204 at WAN port. So the Remote Management Address is Locked at 192.168.1.204.
I got my domain bind to my main router's WAN port so I could asscess and management my main router from Internet remotely. I forwarding the 8800 port from the main router to Nighthawk Rax120's port and set the same port on Rax 120 (port 8800) as remote access port. But I could not access the router other than the address : 192.168.1.204:8800 . I wanna to setup the Remote Management Address to my domain which is XXXXXXX.Com:8800 . Is that possible to set it up without changing the Nighthawk Rax120 to first level?
5 Replies
> Now the problem is . After I setup the nighthawk rax 120 [...]
The fundamental problem may be that you configured the RAX120 as a
full-function router, instead of as a wireless access point.> [...] So the Remote Management Address is Locked at 192.168.1.204.
How "Locked" is it? Did you reserve that address for it in the DHCP
server in your (unspecified) "my main router"? Or configure the RAX120
WAN/Internet interface with a static address? Or what?> [...] I forwarding the 8800 port from the main router to Nighthawk
> Rax120's port [...]What is the actual port-forwarding rule? What is the exact URL which
the RAX120 says that you should use for Remote Management?
> [...] But I could not access the router other than the address :
> 192.168.1.204:8800 . [...]How, exactly, did you try to "access the router"? Actual URL? From
where? "could not" 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.> Is that possible to set it up without changing the Nighthawk Rax120 to
> first level?I'd expect port forwarding on the main router (done correctly) to do
the job.
However, I'd also recommend configuring the RAX120 as a wireless
access point, in which case, you'd use a suitable port-forwarding rule
on your (unspecified) "my main router", and you'd access the RAX120
management web site as if it were local, not remote ("http://", not
"https://").- First of all ~ thank you for your reply.i called customer service and they tell me this (what I said )is actually a BUG that he reported already and send it to evaluation team.
I need to setup as full-function router, instead of as a wireless access point because that I wanna manage wireless user with netgear router. And this is a router about 500 bucks. I don’t need an 500 dollars Ap . Right? lol
The address is locked means locked on rax120. The “public address “ (which is actually my main router’s address ) is used for web access and not changeable . So if I wanna access the router through 73.167.XXX.XXX: 8800 is automatically blocked by router. I could only access the web access through address. 192.168.1.204:8800 .
And yes my port forwarding setup has not problem. Main router 8800 port forwarding to rax120 8800 port.> [...] The address is locked means locked on rax120. [...]
I don't know what that means. I'll try again:
> [...] Did you reserve that address for it in the DHCP
> server in your (unspecified) "my main router"? Or configure the RAX120
> WAN/Internet interface with a static address? Or what?> [...] if I wanna access the router through 73.167.XXX.XXX: 8800 is
> automatically blocked by router. [...]"automatically blocked by" _which_ "router"? Your (unspecified) "my
main router" would need a port-forwarding rule to allow an incoming
connection from the outside world to get to your RAX120 at
"192.168.1.204:8800".> And yes my port forwarding setup has not problem. [...]
It's nice that you're happy with it, but I can't see it from here.
> [...] i called customer service and they tell me this (what I said )is
> actually a BUG [...]_What_ is the bug?
> [...] I could only access the web access through address.
> 192.168.1.204:8800 .Previous questions still unanswered:
> How, exactly, did you try to "access the router"? Actual URL?
> From where?Also, what is the actual error message which you get when you try?
If you can access your RAX120 at "192.168.1.204:8800" from a system
on the LAN of your (unspecified) "my main router", and if the port
forwarding were working properly on that (unspecified) "my main router",
then it's hard to see how you could fail to access it from the outside
world. And it's even harder to see how a bug in the RAX120 could make
it fail.Does the WAN/Internet address of your (unspecified) "my main router"
match your public address ("73.167.XXX.XXX")? Can you verify that its
port forwarding works with any other device?