CAX30 Port Forwarding Issues with NOIP

[DonaldD]

Just installed a CAX30 Modem/Router device to replace separate Motorola SM7420 and Netgear WNDR3700v4 on a Windows 10 Pro machine.  I changed my RDP port for security purposes. I am a regular RDP user.

When attempting to access my host computer using Remote Desktop Protocol (RDP) and No-IP DDNS service, RDP would only accept my computer name with the port number appended, i.e. [name].mynetgear.com:[port]. When attempting to connect without the port number appended, I was unable to achieve a connection using my No-IP credentials.

A connection could be achieved using the IP address of the router with port number appended, i.e. 172.33.188.140:[port] but this defeats the purpose of having a DDNS service.

This would seem to suggest that Port Forwarding function on the CAX30 router is not functioning properly.

This issue was never previously encoutered when using the Motorola/Netgear WNDR3700v4 combo hardware above.

A screenshot of my Port Forwarding settings is attached.

[DonaldD · Accepted solution]

Update:

After changing the Remote Desktop Protocol on my remote PC, I discovered that the new port number must be also added to the NO-IP PC/Computer entry in Remote Desktop Client.

After adding the new port number to my NO-IP hostname , i.e., "[name].mynetgear.com:[port]" and entering it the "PC/Computer" field in the Remote Desktop Client, the connection was successful.

[michaelkenward]

---

@DonaldD wrote:

Just installed a CAX30 Modem/Router device ...

---

While many questions about routers are generic and could be answered anywhere, some things need specialist knowledge.

You might get more help, and find earlier questions and answers specific to your device, in the appropriate section for your hardware. That's probably here:

Cable Modems & Routers

I will ask the Netgear moderator to move your message.

In the meantime you could visit the support pages:

Support | NETGEAR

Feed in your model number and check the documentation for your hardware. Look at the label on the device for the model number.

Check for various troubleshooting tips.

You may have done this already. I can't tell from your message.

I mention it because Netgear stopped supplying printed manuals and CD versions some years ago and people sometimes miss the downloads.

[DonaldD]

Thank you.  I have spent countless hours attempting to remedy this issue, including much KB information and many Community topical threads.  I would now appreciate some assistance from Netgear Technical Support.

[michaelkenward]

---

@DonaldD wrote:

I would now appreciate some assistance from Netgear Technical Support.

---

In that case, you need to talk to them.

This is essentially a user-to-user forum, with some input from a small band of Netgear techies. You can try the official channels for support, but be warned that after 90 days they will want money before talking to you. Much easier to try to sort it out here before you open your wallet.

Contact Us | MyNETGEAR

[DonaldD · Accepted solution]

Update:

After changing the Remote Desktop Protocol on my remote PC, I discovered that the new port number must be also added to the NO-IP PC/Computer entry in Remote Desktop Client.

After adding the new port number to my NO-IP hostname , i.e., "[name].mynetgear.com:[port]" and entering it the "PC/Computer" field in the Remote Desktop Client, the connection was successful.

[michaelkenward]

Good one. Needs to go into the collective memory.

Nice bit of research.