NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN424 Can you change the https port number from 443 to another number to avoid conflict with server
I haven't yet setup my NAS RN424 as the new office isn't quite ready. However I have been reading through the documentation in preparation to do so I see in the documentation for setting up the H...
Hi.
Thanks for all your help. I'll set up the 2nd port and see how it goes
With regard to the MS server RWA, if I can't go directly to the NAS I can always piggyback from a workstation.
For your interest and anyone else that has looked at this, once I install the NAS in the Office (when BT put the new Broadband in) I will let you know my final solution
GrahamH20 wrote:
If it is correct then it conflicts with the servers remote access.
By "server" do you mean the ReadyNAS itself? If so, you can forward port 443 in the router either to the NAS primary port or to the secondary port.
GrahamH20 wrote:
If the NAS port cannot be changed would port 444 suffice or should I choose a much higher number
The internet folks (IANA/ICANN) have reserved port 49152-65535 for private use. So I always recommend assigning ports in this range.
Hi StephenD
Thanks for letting me know the recommended range of ports to use.
The server is a 2012 R2 Essentials server. The RWA (remote web access) is configured to use port 443 with port fowarding for that port directed to the MS server. I thought it would be easier to change the default https port on the NAS when installing rather than reconfigure both firewall and RWA on the MS server. However the NAS User manual says you can't change the default port 1 for https from 443, so unless this is wrong I guess I will need to reconfigure the MS server
GrahamH20 wrote:
Thanks for letting me know the recommended range of ports to use.
The server is a 2012 R2 Essentials server. The RWA (remote web access) is configured to use port 443 with port fowarding for that port directed to the MS server.
You have two other options:
- set the secondary port to a different value (say 49152), and then forward 49152 in the router to NAS port 49152.
- forward a different port (say 49152) to NAS port 443 in the router.
The challenge with either approach is that the port needs to be specified in the URL (e.g, https://routerdnsname:49152/admin/ ).
Are you planning on having normal users access the NAS remotely, or is this an administrative convenience?
Hi StephenB
Thanks for guiding me on this its really appreciated
I'm hoping that I can access the NAS (for admin only) via the Server 2012 remote access.
The NAS is connected to the LAN but is situated out of the office in the house next door. The house has a seperate Broadband line, which wont be connected to the NAS unless the Office broadband goes down. I wanted to prepare a DR solution in that in the event of the MS server going down/or the Office broadband failing then I could reconfigure the NAS for Users to remote in directly to the NAS (Using NAS accounts) to access the data via the 2nd Broadband
If I configure Port 2, is port 1 (with its default 443 port) still active. If so, wont it still conflict with the MS Servers RWA or wont it matter if there is no port forwarding set up to the NAS on 443
Thanks for your patience
GrahamH20 wrote:
If I configure Port 2, is port 1 (with its default 443 port) still active. If so, wont it still conflict with the MS Servers RWA or wont it matter if there is no port forwarding set up to the NAS on 443
The port forwarding doesn't matter, but I don't know enough about RWA to know if it has the features you need to let you access the NAS.
Microsoft Remote desktop certainly would work - you'd open the browser in the screen share, and then access the NAS as usual. Similarly, TeamViewer.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
