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

Smart Hub 7 Plus Port Forwarding Issue

jsviper77
Contributor
Contributor

Hi All,

Another Issue with the Hub 7 Plus, probably on others too.

When i create a Port forwarding rule, it always comes up with an error and doesn't save or eventually when it does save, it has created duplicate rules. Try to remove one and it removes both, aaarrrgghh! These EE hub are very frustrating.

I hope someone who can help sees this and my other post, to help fix these issues.

98 REPLIES 98
SamyM
Established Contributor
Established Contributor

Hi, where do I go to turn off the advanced web protect. It must be something that is only active with the EE Hub 7 Plus, as it does not seem to have any affect when on the EE Hub 2. Tried to go to the EE app then Broadband and each time I just get this screen. I get no further each time.

Screenshot_20260326-070910.jpg

Something wrong somewhere. 

 

Samy

Pecbeck
Established Contributor
Established Contributor

In the ee app, broadband-> manage > WiFi security.  Mines off

You will need to pair app with hub first, if you've changed name the qr code on the hub won't work,  need to select manually. 

bobpullen
Star Contributor
Star Contributor

@SamyM wrote:

Hi, where do I go to turn off the advanced web protect. It must be something that is only active with the EE Hub 7 Plus...


Correct, it's only available on the newer hubs. I think there's a stripped down alternative for the Hub 2 but it's not quite the same thing. I could be wrong, but I imagine the app is expecting you to have a newer hub on the line and may well be throwing its toys out of the pram if you're using something else.

SamyM
Established Contributor
Established Contributor

Hi, I phoned EE and we went through connecting Hub 7 Plus going through the app to setup the device.  It then gave me the option for the advanced web protection.  So I disabled it with EE on the phone line and then did some testing for port forwarding.  She talked me through what to do and port forwarding did not work.  Tested the port and still closed.  She then said she has not worked withe the RE Hub 7 plus before and she raised it withe her supervisor and then they agreed to raise a complaint and said they would call back when there was a resolution.  After ending the call 30mins ish later I got a message that my complaint has been closed.  This is what happens each time.

Screenshot_20260327-094652_Messages.jpg

Samy

bobpullen
Star Contributor
Star Contributor

@SamyM - is the 7 Plus online? I'm assuming it will need to be for the helpdesk to be able to do anything remotely, especially as the problem seems to be unique to you. Based on mine and Pecbecks tests, I'd be surprised if they're able to easily replicate the problem.

I've scanned back through the thread and there are a number of questions/suggestions that I don't think have been answered...

  1. Exactly how are you trying to access the NAS i.e. step by step, what app/software are you using, what device is it installed on, what Internet address/IP address is it trying to access?
  2. When the port forwarding rule is in place. Check the device list in the Hub Manager. Is the little shield icon present next to the NAS?
  3. On the device list, is the MAC address accurate for the NAS and does the IP address match the one you have used for the port forwarding rule? If you click the NAS in the list, do you see an IPv6 address assigned?
  4. Have you tried temproarily removing the switch from the equation so the NAS is connected directly to a LAN port on the router?
  5. Have you tried a port check on the 49592 UPnP rule that is appearing? i.e. does it show open on yougetsignal.com
  6. Have you tried disabling UPnP in the Hub Manager (Advanced > Firewall > Configuration), rebooting the hub and seeing if it makes any difference?
  7. Have you tried connecting to the FTP server across your local network i.e. FTP to the 192.168.1.155 address from another machine on your network - Does that work?
  8. On the NAS how are things configured under WD Dashboard -> Settings -> Network - can you provide a screenshot?

Whilst the answer to these questions might not necessarily fix the problem, it might help narrow down where it lies.

Pecbeck
Established Contributor
Established Contributor

Spot on Bob, I was about to ask similar, as none has been really answered as yet

I would add my earlier question

As not using ddns how are you ensuring your external domain is pointing to the hubs external ip address? When you run the port open checker, have you double checked it shows the current hub external ip? 

I just do not understand the end to end config. It makes no sense that port 21 is open when enabling  dmz, but not when using port forwarding. 

SamyM
Established Contributor
Established Contributor

Hi, I will try and answer all your questions.

 

  1. I’m accessing my NAS WD EX2 Ultra via the internal IP address and have been using it via the Broadband IP address with port forwarding (21).  I know that this can change when the router is rebooted so I just modify my IP cameras via the Ctronics App and they start FTPing again.  My NAS drive is also accessible via the WD OS5 cloud App.
  2. The device has the Shield, and the FTP definition is against the device ending in 155

SamyM_0-1774625237516.png

 

SamyM_1-1774625237521.png

 

  1. The MAC address and the IP address match
  2. I have tried putting the NAS WD EX2 Ulta direct into the router and no difference. The port is closedSamyM_2-1774625237528.png

     

  3. Mysteriously Port 49592 is open and that is also for IP address 192.168.1.155.  That was not defined by me but happened between the Hub and the NAS cloud automatically. So, what is so different with my definition (port 21)?
  4. I have disabled UPnP and rebooted the rooter and port 21 is still closed.
  5. Connecting to the NAS drive locally it all works and my Ctronics IP cameras are successfully FTPing into the NAS drive using ID and Password.
  6. On the NAS WD I have enabled FTP and selected port 21 for FTP options.  For FTP I only get port 20 and 21 to select.
SamyM
Established Contributor
Established Contributor

7. Connecting to the NAS drive locally it all works and my Ctronics IP cameras are successfully FTPing into the NAS drive using ID and Password.

8. On the NAS WD I have enabled FTP and selected port 21 for FTP options.  For FTP I only get port 20 and 21 to select.

SamyM
Established Contributor
Established Contributor

 

Hi something drastically went wrong updating the reply.  I will try again.

  1. I access the NAS drive via the web/google chrome, via the network definition on windows 11 for the NAS drive (MYCLOUDEX2ULTR2) and the WD App on my Smart devices. The IP address is 192.168.1.155
  2. The device has the Shield against it.  Plus has the FTP definition too.

 

Screenshot (154).png

 

Screenshot (153).png

3. The MAC address is accurate and matches the IP address

4.I have plugged the NAS drive direct into the EE Hub 7 Plus and no change

5. I have done a port check against 49592 and mysteriously it is open so why is port 21 not!  Confused.  Port 49592 was done automatically between the router and the NAS drive.

 

 

 

 

 

Screenshot (155).png

6.  I have tried disabling UPnP and no difference.  Port is still closed.

7.  Connecting to the NAS drive locally it all works and my Ctronics IP cameras are successfully FTPing into the NAS drive using ID and Password.

8. On the NAS WD I have enabled FTP and selected port 21 for FTP options.  For FTP I only get port 20 and 21 to select.