cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This page is no longer active

close

   

For up-to-date information and comments, search the EE Community or start a new topic.

Port forwarding/NAT problem

Bobby1214181
Investigator
Investigator

Hi,

I have placed a Netgear router after the EE smartHub (SH) and before a Synology NAS. The SH is configured with DHCP and wifis set to off. Further the Netgear router is on a different subnet to SH. 

 

I have port forwarded a number of ports on both routers to connect Http and other services to the NAS. In order to avoid double NAT I have placed the SH in DMZ mode with IP tunneling to the Netgear router.

 

The problem I have is that I cannot access my NAS using its DDNS domain address from within the LAN, but I can from outside. In addition, I cannot ping or tracert ( in CMD) to the domain address, but I can to other sites like BBC or CNN.

 

I realise its tough to explain the exact configuration, but I wonder if anyone has any suggestions because I am running out of ideas to try.

 

Many thanks 

1 REPLY 1
XRaySpeX
EE Community Star
EE Community Star

From within your LAN you cannot access your server using your DDNS domain address cuz the the DDNS evaluates the DDNS domain address & gives it back as your current public IP addy. Then you run into the problem of loopback. The router won't go on the Net to access it as it knows it's its own IP addy but it isn't coming in on the WAN & so it won't be applying Port Forwarding to it..

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP