Questions

Help with configuring router and modem for http access to nas

+
0 Votes
Locked

Help with configuring router and modem for http access to nas

Philo138
Hello TR community, all day today I have been trying to reconfigure my home set up to make my NAS accessible via http/s. My current set up goes like this (IPs have been changed for security sake).

I have an comcast provided SMC router (model smcd3gnv) at 192.168.0.1 my router (dlink model dgl-4500) resides under it at 192.168.0.2 and then my NAS box (netgear readyNAS untra 4) sits under the router at 192.168.1.10. On both the modem and the router ports 80 and 443 are forwarded to as such: modem forwards ports 80 and 443 to the router which in turn forwards those ports to the NAS.

My external IP is linked via dlinkddns (which is affiliated with dyndns). Which settings look to be taking my external IP and linking it to my routers IP (to be honest I dont fully understand the settings here and there are no descriptions of what should go where on the site).

When I type in my url from within my network I am able to access my nas. However when I try the samething from outside my network the connection times out. I suspect port forwarding is to blame. I have tried placing the dlink router in the comcast SMC router/modem's DMZ and then placing the nas in the dlink's DMZ but still nothing changes.

Any help would be appreciated.
  • +
    0 Votes
    SmartAceW0LF

    One or the other of the 2 needs to be configured in bridge mode. Or at very least one should have NAT disabled. In addition there seem to be several problematic issues if your scenario is in fact as you portrayed it.
    First, I am not sure what the purpose is of having the second router on a different subnet than the rest of the network. Where you state that your dlink router is on 192.168.0.xxx ip as opposed to the others which are on a 192.168.1.xxx subnet.
    Second, as ports 80 and 443 are commonly used ports throughout all network devices, I am not sure it's a good idea to forward those particular ports to your NAS as I believe that will effectively route all incoming traffic on those ports to your NAS alone.
    So, here is what I would suggest given the information you have supplied.
    1.) Hook your D-Link router up to your PC via Ethernet and give it a static IP address which is OUTSIDE of the DHCP range that is set on the SMC Device. Its important to remember that DHCP assigns IP addresses only to those devices that do not already have one. Thus if your DHCP is set to issue IPs in the range of say 192.168.1.100 to 192.168.1.255 then you would set any devices that you wish to have a static IP, at an address ranging from 192.168.1.2 up to 192.168.1.99. This is all contingent upon the fact that your SMC Router operates at 192.168.1.1. You will have to check that out. If your SMC Router delivers DHCP addresses spanning the entire subnet of xxx.xxx.1.1 through xxx.xxx.1.255 then you should narrow that range down a bit as described above.
    2.) While still within the D-Link configuration, disable DHCP and also disable NAT on this device. These are not necessary as they are both being handled by the SMC device. Also, this means that you will basically be utilizing the D-Link device as a "Switch" rather than a router. This means that you will not be utilizing the WAN port on the D-Link router. Only the LAN ports. I presume your desire to use this additional device is due to the fact that your SMC router doesn't have Wireless capabilities? At any rate, you may still leave the Wifi function enabled on the D-Link as well.
    3.) Next, you will want to follow the NAS manufacturers instructions on setting the IP address of the NAS. When this is done, disconnect everything and hook the SMC Router back up. Assure that you can now connect to the Internet without any problems. Connect a LAN cable from one of the LAN ports of the SMC device to a LAN port on the D-Link router. Then connect your NAS via ethernet cable to any of the LAN ports on either of the 2 devices.
    4.) Verify your setup by opening a web browser and entering the IP address you assigned to the D-Link device into the browsers address field. If you get the d-link configuration page up your good to go with it. Then follow suit with the NAS device's IP address also entered into the web browsers address bar and make sure you are connecting there. If you are, great. If not, go back over these directions carefully to determine what you left out. Finally, given all is well thus far, determine what the IP address of the SMC Router is. If you do not know it, open a command prompt on your PC and invoke the command, "ipconfig /all" without the quotes. FInd the IPv4 address of Default Gateway. This will be the address necessary to enter into your browser in order to get to its configuration page.
    5.) Moving on to the configuration within the SMC Router. One within the configuration pages of the SMC device, check its DHCP range and configure it according to the instructions related above. Would probably be a good idea to simplify matters a bit by disabling IPv6 if you find a place to do so within the router. All of these things are done in order to more easily effect the Port Forwarding (sometimes called pinholes) of your network devices.
    I do hope that all of this has not confused you to the point of bewilderment. I have no doubt that you already have great time invested in this venture. That said, take it from someone who has been through the same, that upon realizing there were two devices on the network trying to do NAT (Network Address Translation), my experience with it was all easy sailing from then on.
    There is a site portforward.com that will have all of the information described above. As a matter of fact, upon checking the site, I see they offer an application to accomplish this very thing. I doubt anyone could deny their authority on the subject and at the quoted price it just might be a worthwhile venture for you. Still, I think I would give it a shot myself first. Good luck.

  • +
    0 Votes
    SmartAceW0LF

    One or the other of the 2 needs to be configured in bridge mode. Or at very least one should have NAT disabled. In addition there seem to be several problematic issues if your scenario is in fact as you portrayed it.
    First, I am not sure what the purpose is of having the second router on a different subnet than the rest of the network. Where you state that your dlink router is on 192.168.0.xxx ip as opposed to the others which are on a 192.168.1.xxx subnet.
    Second, as ports 80 and 443 are commonly used ports throughout all network devices, I am not sure it's a good idea to forward those particular ports to your NAS as I believe that will effectively route all incoming traffic on those ports to your NAS alone.
    So, here is what I would suggest given the information you have supplied.
    1.) Hook your D-Link router up to your PC via Ethernet and give it a static IP address which is OUTSIDE of the DHCP range that is set on the SMC Device. Its important to remember that DHCP assigns IP addresses only to those devices that do not already have one. Thus if your DHCP is set to issue IPs in the range of say 192.168.1.100 to 192.168.1.255 then you would set any devices that you wish to have a static IP, at an address ranging from 192.168.1.2 up to 192.168.1.99. This is all contingent upon the fact that your SMC Router operates at 192.168.1.1. You will have to check that out. If your SMC Router delivers DHCP addresses spanning the entire subnet of xxx.xxx.1.1 through xxx.xxx.1.255 then you should narrow that range down a bit as described above.
    2.) While still within the D-Link configuration, disable DHCP and also disable NAT on this device. These are not necessary as they are both being handled by the SMC device. Also, this means that you will basically be utilizing the D-Link device as a "Switch" rather than a router. This means that you will not be utilizing the WAN port on the D-Link router. Only the LAN ports. I presume your desire to use this additional device is due to the fact that your SMC router doesn't have Wireless capabilities? At any rate, you may still leave the Wifi function enabled on the D-Link as well.
    3.) Next, you will want to follow the NAS manufacturers instructions on setting the IP address of the NAS. When this is done, disconnect everything and hook the SMC Router back up. Assure that you can now connect to the Internet without any problems. Connect a LAN cable from one of the LAN ports of the SMC device to a LAN port on the D-Link router. Then connect your NAS via ethernet cable to any of the LAN ports on either of the 2 devices.
    4.) Verify your setup by opening a web browser and entering the IP address you assigned to the D-Link device into the browsers address field. If you get the d-link configuration page up your good to go with it. Then follow suit with the NAS device's IP address also entered into the web browsers address bar and make sure you are connecting there. If you are, great. If not, go back over these directions carefully to determine what you left out. Finally, given all is well thus far, determine what the IP address of the SMC Router is. If you do not know it, open a command prompt on your PC and invoke the command, "ipconfig /all" without the quotes. FInd the IPv4 address of Default Gateway. This will be the address necessary to enter into your browser in order to get to its configuration page.
    5.) Moving on to the configuration within the SMC Router. One within the configuration pages of the SMC device, check its DHCP range and configure it according to the instructions related above. Would probably be a good idea to simplify matters a bit by disabling IPv6 if you find a place to do so within the router. All of these things are done in order to more easily effect the Port Forwarding (sometimes called pinholes) of your network devices.
    I do hope that all of this has not confused you to the point of bewilderment. I have no doubt that you already have great time invested in this venture. That said, take it from someone who has been through the same, that upon realizing there were two devices on the network trying to do NAT (Network Address Translation), my experience with it was all easy sailing from then on.
    There is a site portforward.com that will have all of the information described above. As a matter of fact, upon checking the site, I see they offer an application to accomplish this very thing. I doubt anyone could deny their authority on the subject and at the quoted price it just might be a worthwhile venture for you. Still, I think I would give it a shot myself first. Good luck.