NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Web Publishing Service on Zuxel NAS326 and Port Forwarding on Netgear Router
Hello,
I am on uncharted waters - I only know how to setup wireless: set password, naming the flag and enable encryption. I have no experince in Port Forwarding and what it does. According to Zyxel NAS support; in order to make the Service: Web Publishing function on my Zyxel NAS326, I need to port forward on the Netgear router: Port no. 5000 must be open and set this up with upd and tcp protocol on the router.
How do I do this ?
Right now, I have access to the files on the shared folder I have web Published, from all the PC which are on the LAN - The address format which the NAS has created looks like this: http://[server-name:5000]/MyWeb/Public ....where the folder; 'Public' is shared. On that address; files are visible in a browser and they can open and be saved if need be on the LAN. I need them to be accessable for the rest of the world !! If I try the same URL from an 'external' internet based PC, there are no web-page to be seen.
Hope you can help out here :O) Lars
Hello Antinode,
I just want to thank you for all your help - It has been most pleasant and a great leaner for me.
Best regards Lars
22 Replies
> [...] I have no experince in Port Forwarding and what it does. [...]
That will need to change. Port forwarding is what the router does to
deal with a message which arrives at its WAN/Internet port from the
outside world. Your ISP has assigned one (external) IP address to your
whole installation; either you or your router has assigned an entirely
different (LAN) IP address to each device on your LAN.If someone in the outside world wants to send a message to a device
on your LAN, all he can do is send it to your router. How, then, does
the router know what to do with that message? To which of your devices
(if any) should it forward that message?A port-forwarding rule is what tells the router what to do with such
a message.> [...] http://[server-name:5000]/MyWeb/Public [...]
More precisely:http://[server-name]:5000/MyWeb/Public [...]
Note that your "[server-name]" could also be your external IP
address instead of a DNS name.That "5000" is the relevant port number. You can think of it as like
an apartment number after a street address (IP address). In this case,
you'd want a port-forwarding rule like:Service Type: TCP+UDP
External port range: 5000
Internal port range: 5000
Server IP Address: <LAN_IP_address_of_NAS>That implies that the NAS device needs a fixed LAN IP address, which can
be arranged at ADVANCED > Setup LAN Setup : Address Reservation.
With such a rule in effect, when a message destined for port 5000
arrives at your router's WAN/Internet port, the router will forward it
to the device at <LAN_IP_address_of_NAS>. When that device sends a
reply to that message, the router will handle the reply, ensuring that
it returns to the outside-world device which sent the original message.It's important that the IP address of the WAN/Internet on your router
match your public (external) IP address. If there's another router
between yours and the Internet (which could be a second router at your
site, or at your ISP's site) then you can expect problems.
As you might guess, you could specify different external and internal
port numbers in your port-forwarding rule. The external port number is
what is used in the outside world; the internal port number is what is
used on your LAN. So, for example, if you had a second NAS device, you
could create a rule like:Service Type: TCP+UDP
External port range: 5001
Internal port range: 5000
Server IP Address: <LAN_IP_address_of_NAS-2>Then, a URL like the following would reach "NAS-2":
http://[server-name]:5001/MyWeb/Public [...]
On your LAN, NAS-2 would still use port 5000, but, because of that
port-forwarding rule, it would be seen at port 5001 from the outside
world.Hello, ...and thanks for the answer; Antinode, which open up some core issues:
You mention that the IP which my router receives from my ISP should be static and I have a suspision that is not the case !! In general, I check ip with IPCONFIG in CMD. If I unplug the router and plug in a PC on the wall it gets nearly the same ip (except for one digit) as what the router gets. Similarly another PC get another ip, 2 digits away from the router ip which tells me they are all assigned dynamically. The final straw is; if I try to ping the router IP address from a PC which connects to the internet over the mobilenetwork; USB-modem, it states; 'reply from 10.117.15.173: Distination net unreachable' ......Which I interpret; the router do not get a real external IP addresse and it matches the fact that my ISP advertise on their website that I can buy a fixed IP address for a minor one time payment.
Antinode, am I on the right path, you think ?
nUUK25 wrote:...if I try to ping the router IP address from a PC which connects to the internet over the mobilenetwork; USB-modem, it states; 'reply from 10.117.15.173: Distination net unreachable' ......Which I interpret; the router do not get a real external IP addresse ...
If your R7800 does show the same RFC1918 address on the Advanced -> Internet port IP address information, this is correct.
