Port forwarding seems to have stopped

[#1]

Hi,
I port forward into my house for my Qnap NAS.
I use a no-ip,org address which is still current and correct.
Worked fine for years, but topped in this past few weeks.
I've messed around with all sorts and this is all I have:-
Firewall in plus.net is off. I've tried toggling it incase it was "stuck" but no change.
I've replicated the setup at work, port forwarding is ok.
I've replicated the setup at my sisters house - plus.net - same problem as me
A tracert from work, gets into plus.net then times out, here's the plus net part of it.
  8    88 ms    20 ms    20 ms  linx-gw1.plus.net [195.66.224.164]
  9    28 ms    21 ms    21 ms  ae2.ptw-cr02.plus.net [195.166.129.5]
10    20 ms    20 ms    49 ms  ae1.pcl-cr02.plus.net [195.166.129.3]
11  107 ms    21 ms    21 ms  te-2-3.pcl-gw02.plus.net [212.159.1.3]
12    27 ms    45 ms    38 ms  link12-central10.pcl-ag01.plus.net [84.93.249.23]
13    *        *        *    Request timed out.
14    *        *        *    Request timed out.
15    *        *        *    Request timed out.
16    *        *        *    Request timed out.
17    *        *        *    Request timed out.
18    *        *        *    Request timed out.
19    *        *        *    Request timed out.
20    *        *        *    Request timed out.
21    *        *        *    Request timed out.
22    *        *        *    Request timed out.
23    *        *        *    Request timed out.
24    *        *        *    Request timed out.
25    *        *        *    Request timed out.
26    *        *        *    Request timed out.
27    *        *        *    Request timed out.
28    *        *        *    Request timed out.
29    *        *        *    Request timed out.
30    *        *        *    Request timed out.
Kinda stuck, any ideas?
Jeff

[#2]

The hop after the last one there should be your router so looks like its ping responder is disabled?

[#3]

Yes, I did have ping disabled, but re-enabled it - I wasn't aware a ping response affected a tracert.
Anyhow, it responds to a ping, with the correct address.
However, a tracert though, still stops in plus net and not at my house, (from the wifes phone with a tracert installed)
last 2 steps with plusnet
212.159.1.17    te-9-1.ptw-gw01.plus.net
212.159.1.19    te-9-1.ptw-gw02.plus.net
the last one is not my IP address 😞 which is 146.90.*.* without giving too much away. I've also tried tracert to the number rather than the name
If I tracert to work right now, I get the last hop as being the correct IP address of work
Sorry if I'm missing something, but it does look like it's getting "stuck" in plus.net somewhere?
Thanks
Jeff

[#4]

What trace result does the Usertools gateway diagnostic give?
http://users.plus.net/@gateway_custom?debug-ip=1

[#5]

Hi,
I asked my abled bodied assistant who is at home today to do that for me 😉
Here is the result
You are using a debugging mode - and checking IP 87.115.89.***
Array
(
   [0] =>  1  vl7.sec.ptb-gw4.plus.net (212.159.3.**)  0.551 ms
   [1] =>  2  vl421.pih-gw3.plus.net (212.159.1.171)  0.565 ms
   [2] =>  3  gi1-1.ptn-gw01.plus.net (212.159.1.178)  113.918 ms
   [3] =>  4  ae3.ptw-cr01.plus.net (195.166.129.32)  12.429 ms
   [4] =>  5  te-4-1.ptw-gw01.plus.net (212.159.1.41)  12.963 ms
   [5] =>  6  link9-central10.ptw-ag04.plus.net (84.93.248.113)  13.593 ms
   [6] =>  7  *
   [7] =>  8  *
   [8] =>  9  *
)
You are currently connected to the gateway known as ptw-ag04.
This is located in Telehouse West.
I'm on a dynamic address, and I keep it with a named DNS address for me updated via a dynamic dns supplier. This address is correct for the name
Does this help?
Remember my brother in law/sister, also on plus.net was setup for port forwarding as it allowed me to offer remote assistance, this has also stopped working.
[Moderator's note by Jim (Oldjim)  part of IP address munged ]

[#6]

The trace gets to your gateway; your router should be next but doesn't respond. Has the router ping responder been re-enabled?

[#7]

I did re-enable it for a test earlier on as per your comments, it responded correctly to a ping then.
However it didn't fix port forwarding, so I switched it off again - that's how you saw in in this test.
The port forwarding had worked prior to all this, with ping disabled.
J

[#8]

Enabling ping will have no bearing on port forwarding,  but it can be used to determine if the router is reachable.
To check the forwarding rules, you should be able to connect to the forwarded ports using your external address from within your network;  this should eliminate any external variables.
Also,  running GRCs ShieldsUp should show what ports are open.