Fixed IP address not responding

[#1]

port forward on router

[#2]

@bryanuk looks good.

Can you access your synology box using internal ip address:100

[#3]

currently in conversation with Go Daddy, god its hard.

[#4]

@bryanuk  Go Daddy's set up, though unusual,  looks OK,  the problem seems to be your end as that is where the traffic stops.

[#5]

yes back to my router again.  It all went wrong when I changed the wi fi setting

[#6]

hat i really want to know is how far the message gets. Does it get to my router or not?  IS it stopping at the DNS stage?  is it stopping at the aws thingy suggested earlier?

[#7]

I know I said I'd just have a watching brief on here, but changing Wi-Fi channels doesn't change any routing, which appears to be what has happened here. What exactly did you change?

[#8]

@bryanuk The traffic is geting through to your router, so the DNS entry is good and the AWS is a red herring.

If you can say which router you're using then we'll wait for a more knowledgeable router person to help.

In the meantime I'll join @jab1 on the sideline....

[#9]

the mystery deepens.  My NAS is on 192.168.1.69 when I type 192.168.1.68:90  i get an error.  When I type 192.168.1.68:100 i get my web site.

I presume i get the error because I am ion the same internal network as the NAS

[#10]

it is a plusnet router.  donbt know which one hub 1 or hub 2?  there is no identification on it

[#11]

Are the lights at the bottom, or on the front panel?

[#12]

it looks like the router forwarding is not working

[#13]

They are under the Plusnet logo on the from panel .  One long (blue) light with a red wi fi light below (because 5g is off).

[#14]

Sounds like a Hub1 - the Hub2 light is in the centre of the front panel.

[#15]

@jab1  Are there any logs in the router showing external access or attempted access ?