<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Port forwarding/NAT problem in Archived Posts</title>
    <link>https://community.ee.co.uk/t5/Archived-Posts/Port-forwarding-NAT-problem/m-p/1102716#M267816</link>
    <description>&lt;P&gt;From within your LAN you cannot access your server using your&amp;nbsp;&lt;SPAN&gt;DDNS domain address cuz the the DDNS evaluates the&amp;nbsp;DDNS domain address &amp;amp; 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 &amp;amp; so it won't be applying&amp;nbsp;Port Forwarding to it..&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 29 Nov 2021 23:11:23 GMT</pubDate>
    <dc:creator>XRaySpeX</dc:creator>
    <dc:date>2021-11-29T23:11:23Z</dc:date>
    <item>
      <title>Port forwarding/NAT problem</title>
      <link>https://community.ee.co.uk/t5/Archived-Posts/Port-forwarding-NAT-problem/m-p/1102713#M267815</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Nov 2021 22:55:26 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Archived-Posts/Port-forwarding-NAT-problem/m-p/1102713#M267815</guid>
      <dc:creator>Bobby1214181</dc:creator>
      <dc:date>2021-11-29T22:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: Port forwarding/NAT problem</title>
      <link>https://community.ee.co.uk/t5/Archived-Posts/Port-forwarding-NAT-problem/m-p/1102716#M267816</link>
      <description>&lt;P&gt;From within your LAN you cannot access your server using your&amp;nbsp;&lt;SPAN&gt;DDNS domain address cuz the the DDNS evaluates the&amp;nbsp;DDNS domain address &amp;amp; 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 &amp;amp; so it won't be applying&amp;nbsp;Port Forwarding to it..&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Nov 2021 23:11:23 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Archived-Posts/Port-forwarding-NAT-problem/m-p/1102716#M267816</guid>
      <dc:creator>XRaySpeX</dc:creator>
      <dc:date>2021-11-29T23:11:23Z</dc:date>
    </item>
  </channel>
</rss>

