<?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 Port Forwarding issues with Smarthub SH35A in Broadband &amp; Landline</title>
    <link>https://community.ee.co.uk/t5/Broadband-Landline/Port-Forwarding-issues-with-Smarthub-SH35A/m-p/1619554#M138013</link>
    <description>&lt;P&gt;I'm having a few issues with port forwarding on a new SmartHub SH35A.&lt;BR /&gt;I've recently moved from BT where I had on old BT Smart hub with some rules to give me external access to couple of machines on my home network. These worked!&lt;BR /&gt;Swapping over to EE - none of the same rules seem to work - except for few rules that have been added via uPNP.&lt;/P&gt;&lt;P&gt;For exmple, my Emby server has created a rule to forward port 8096 through to the server and this works and is seen as open via 'canyouseeme'&lt;BR /&gt;I've added rules to forward ports 80,443,8444,5000,5001 and a few others&amp;nbsp; (all via TCP) to my synology server - which is actively listening on these ports. Internally from my home network I can use these ports, but when I test via 'canyouseeme' - all the ports appear closed.&lt;BR /&gt;&lt;BR /&gt;I've even tried a rule to forward external port 8099 to internal port 8096 (Emby Server) and even that is showing a closed - whilst the uPNP rule 8096 to 8096 is fine.&lt;BR /&gt;&lt;BR /&gt;Any suggestion or fixes would be appreciated&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 23 May 2026 08:40:15 GMT</pubDate>
    <dc:creator>Smudger1971</dc:creator>
    <dc:date>2026-05-23T08:40:15Z</dc:date>
    <item>
      <title>Port Forwarding issues with Smarthub SH35A</title>
      <link>https://community.ee.co.uk/t5/Broadband-Landline/Port-Forwarding-issues-with-Smarthub-SH35A/m-p/1619554#M138013</link>
      <description>&lt;P&gt;I'm having a few issues with port forwarding on a new SmartHub SH35A.&lt;BR /&gt;I've recently moved from BT where I had on old BT Smart hub with some rules to give me external access to couple of machines on my home network. These worked!&lt;BR /&gt;Swapping over to EE - none of the same rules seem to work - except for few rules that have been added via uPNP.&lt;/P&gt;&lt;P&gt;For exmple, my Emby server has created a rule to forward port 8096 through to the server and this works and is seen as open via 'canyouseeme'&lt;BR /&gt;I've added rules to forward ports 80,443,8444,5000,5001 and a few others&amp;nbsp; (all via TCP) to my synology server - which is actively listening on these ports. Internally from my home network I can use these ports, but when I test via 'canyouseeme' - all the ports appear closed.&lt;BR /&gt;&lt;BR /&gt;I've even tried a rule to forward external port 8099 to internal port 8096 (Emby Server) and even that is showing a closed - whilst the uPNP rule 8096 to 8096 is fine.&lt;BR /&gt;&lt;BR /&gt;Any suggestion or fixes would be appreciated&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 23 May 2026 08:40:15 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Broadband-Landline/Port-Forwarding-issues-with-Smarthub-SH35A/m-p/1619554#M138013</guid>
      <dc:creator>Smudger1971</dc:creator>
      <dc:date>2026-05-23T08:40:15Z</dc:date>
    </item>
    <item>
      <title>Re: Port Forwarding issues with Smarthub SH35A</title>
      <link>https://community.ee.co.uk/t5/Broadband-Landline/Port-Forwarding-issues-with-Smarthub-SH35A/m-p/1619561#M138017</link>
      <description>&lt;P&gt;&lt;a href="https://community.ee.co.uk/t5/user/viewprofilepage/user-id/4998496"&gt;@Smudger1971&lt;/a&gt;&amp;nbsp;See the very end off the link below.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.ee.co.uk/t5/Broadband-Landline/Smart-Hub-7-Plus-Port-Forwarding-Issue/td-p/1594284/page/11" target="_blank"&gt;Smart Hub 7 Plus Port Forwarding Issue - Page 11 - The EE Community&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 23 May 2026 08:54:06 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Broadband-Landline/Port-Forwarding-issues-with-Smarthub-SH35A/m-p/1619561#M138017</guid>
      <dc:creator>JimM11</dc:creator>
      <dc:date>2026-05-23T08:54:06Z</dc:date>
    </item>
    <item>
      <title>Re: Port Forwarding issues with Smarthub SH35A</title>
      <link>https://community.ee.co.uk/t5/Broadband-Landline/Port-Forwarding-issues-with-Smarthub-SH35A/m-p/1619564#M138018</link>
      <description>&lt;P&gt;&lt;a href="https://community.ee.co.uk/t5/user/viewprofilepage/user-id/4314848"&gt;@JimM11&lt;/a&gt;&amp;nbsp;Thanks for this.&lt;BR /&gt;&lt;BR /&gt;I think I'll try:&lt;BR /&gt;- using MinUPnP to remove the uPNP rules first , then switch off uPnP and then add them manually&amp;nbsp;&lt;/P&gt;&lt;P&gt;OR&lt;/P&gt;&lt;P&gt;-&amp;nbsp;&amp;nbsp;Add all my rules via MinUPnP&lt;BR /&gt;Anything to avoid a factory reset on the Hub - but if requires it , then so be it.&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 23 May 2026 09:15:59 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Broadband-Landline/Port-Forwarding-issues-with-Smarthub-SH35A/m-p/1619564#M138018</guid>
      <dc:creator>Smudger1971</dc:creator>
      <dc:date>2026-05-23T09:15:59Z</dc:date>
    </item>
    <item>
      <title>Re: Port Forwarding issues with Smarthub SH35A</title>
      <link>https://community.ee.co.uk/t5/Broadband-Landline/Port-Forwarding-issues-with-Smarthub-SH35A/m-p/1619565#M138019</link>
      <description>&lt;P&gt;&lt;a href="https://community.ee.co.uk/t5/user/viewprofilepage/user-id/4998496"&gt;@Smudger1971&lt;/a&gt;&amp;nbsp;Link also shows what the 7 Plus is on FW updates, normally happens when unit is first connected, but worth a quick check that yours is up and on the latest, will save you a bit of fighting the 7 Plus hub as the OOB FW is very suspect.&lt;/P&gt;</description>
      <pubDate>Sat, 23 May 2026 09:22:10 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Broadband-Landline/Port-Forwarding-issues-with-Smarthub-SH35A/m-p/1619565#M138019</guid>
      <dc:creator>JimM11</dc:creator>
      <dc:date>2026-05-23T09:22:10Z</dc:date>
    </item>
    <item>
      <title>Re: Port Forwarding issues with Smarthub SH35A</title>
      <link>https://community.ee.co.uk/t5/Broadband-Landline/Port-Forwarding-issues-with-Smarthub-SH35A/m-p/1619614#M138034</link>
      <description>&lt;P&gt;&lt;a href="https://community.ee.co.uk/t5/user/viewprofilepage/user-id/4314848"&gt;@JimM11&lt;/a&gt;&amp;nbsp;Thanks for all you help with this issue. As promised a brief update&lt;BR /&gt;&lt;BR /&gt;After a few failed attempt at mimicking a uPNP client across various devices on my network, I gave in and reset the Router.&lt;BR /&gt;&lt;BR /&gt;The uPNP client repeatedly failed with error 606 (action not authorised) when trying to add or delete a port - regardless of the machine I used.&amp;nbsp;&lt;BR /&gt;The only command that would work was 'upnpc -l'&amp;nbsp; to list the ports - BUT that only found port 8096. Port 8920 was also added by my Emby server, but never listed with the upnp client.&amp;nbsp;&lt;BR /&gt;As for the firmware - I'm on&amp;nbsp;&lt;SPAN&gt;r3.35.24-R-1648110-PROD-84001&amp;nbsp; with app version&amp;nbsp;3.11.3 - which accoriding to the aforementioned thread, is the latest. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;As I've had the router for approx 3 months, I suspect it came with a lower FW version initially and updated after the Emby server had written its port rules.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;For now uPNP has been switched off.&amp;nbsp;&lt;BR /&gt;Again - many thanks for pointing me in the right direction&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 23 May 2026 14:57:45 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Broadband-Landline/Port-Forwarding-issues-with-Smarthub-SH35A/m-p/1619614#M138034</guid>
      <dc:creator>Smudger1971</dc:creator>
      <dc:date>2026-05-23T14:57:45Z</dc:date>
    </item>
  </channel>
</rss>

