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

Yet another Port Forwarding Issue.....

alexthecamel
Investigator
Investigator

Hi, I've recently upgraded to a Smart Hub Pro (WiFI 7) having previously been using an ancient BT branded Router.

Internet and WiFi setup all went well, that part is working fine, however the Port Forwarding just doesn't seem to work at all.
I run a Raspberry Pi with various Internet facing servers for which I forward the ports individually, Nothing I can do seems to forward traffic to the appropriate device. 
I've tried using custom IP Ranges, the default IP Ranges with the target machine both in and outside of the DHCP IP range in both cases.
Even setting the DMZ to that machine doesn't do anything. I've read every post in here I can find and on the Internet.
As soon as I switch back to the old router everything works as expected but identical, and even greatly simplified versions of the Port Forwarding configurations just don't seem to do anything. The Ports appear open on a scan but no traffic arrives.
I'm still in my cool off period so will be returning the device and going elsewhere if I can't get this rather basic function to work.

Anything to try before I jump ship?

Thanks

6 REPLIES 6
XRaySpeX
EE Community Star
EE Community Star

If the ports a reported as open by a port scan it should be OK.

What does ShieldsUP! report the status of your ports when you use its All Service Ports & also your opened ports with User-Specified Custom Port Probe ? Are they shown as "Closed" or "Stealth"?

Let's see your Port Forwarding settings.

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 Home Broadband & Home Phone or Option 2 for Mobile Phone & Mobile Broadband

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
alexthecamel
Investigator
Investigator

Hey, thanks for coming back to me.

Firewall Settings in the Router:

alexthecamel_0-1776521706613.png

Shields Up:

alexthecamel_1-1776521828251.png

Appreciate it's unusual, but the ports appear open, the packets just don't seem to arrive. 

alexthecamel_2-1776521994395.png

Thanks again. 

Where is the client?

I can only think that remote client isn't sending to right port on right IP. Are you taking into account the dynamic public IP nature of your EE BB connection?

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 Home Broadband & Home Phone or Option 2 for Mobile Phone & Mobile Broadband

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

Yes, I use the Dynamic DNS service within the router but have also been manually verifying against the DNS record. 

Where is the client you are using?

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 Home Broadband & Home Phone or Option 2 for Mobile Phone & Mobile Broadband

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
alexthecamel
Investigator
Investigator

Not entirely sure what you mean.

The services are running on a RasPi and I am trying to connect from a different machine on the same network. 
In the case of the Plex Server, Plex are unable to connect to my server from a remote location either. It appears offline to them too. All services work within the Network using local addresses.