Installed new Router ASUS RT-AX58U, lost Synology Drive-connection

[oRBIT]

Since I upgraded my router I can't access my Synology Drive anymore. I've portforwarded 6690 just as before but Drive Client on my PCs can't connect. I've tried creating the link once again and it can't connect.
I've portforwarded a bounce of other stuff in my router and that seems to work but Drive has given up it seems.
I can connect locally to my servers IP-address but not remotely.
Hints here are appreciated.

 

[Telos]

I can connect locally to my servers IP-address but not remotely.

Unclear. You would not use the same IP address to connect remotely. Are you using a domain addy, or DDNS? Or?

 

[oRBIT]

Yes, sorry I forgot to mention that. I suspect my router is involved in some way here, but it's strange that some ports seem to be forwarded and other not.

 

[WST16]

Use a port tester to check if the port is open as a first step.
Something like:

Open Port Check Tool - Test Port Forwarding on Your Router

Port checker is a utility used to identify your external IP address and detect open ports on your connection. This tool is useful for finding out if your port forwarding is setup correctly or if your server applications are being blocked by a firewall.

www.yougetsignal.com

Try this one. Might be more reliable. You can define ports at the bottom of the page.

Port Scanners / WhatsMyIP.org

These port scanners let you check if any internet programs are running on your computer and/or check to see if port mappings in your routers are functioning properly.

www.whatsmyip.org

 

[fredbert]

1. Double check that the NAT/port forward rule is set to send TCP/6690 to your NAS's LAN IP
2. Double check the firewall rule also directs inbound (and local loopback) TCP/6690 to your NAS's LAN IP ... unless your firewall participates in packet mediation before NAT in which case rule to allow TCP/6690 to the router.
3. Check certificates assigned to Drive Server: are they valid for the connectivity method you are using?
4. Check DSM firewall, if enabled, and any rule for allowing inbound TCP/6690 from the Internet (and local loopback).
5. Does QuickConnect work?

Some thoughts.

Drive mobile app uses HTTP/HTTPS only so that's the DSM ports. Likewise Drive web portal. The desktop sync clients use TCP/6690. If you have setup an Application Portal unique URL for Drive (portal) then this will also work for Drive sync because it should all land at the NAS. The only difference is if you use different certificates for Synology Drive (portal and mobile app access) and Synology Drive Server (sync access) where the access URL should be in the relevant certificate's subject alternative names list.

 

[oRBIT]

Really stupid, I had entered the wrong ip-address in the forwarding table (one figure was wrong). Sorry for taking up your time.

 

[WST16]

Hey! That’s not very SynoFormy of you
Just kidding. Glad you found it

Don‘t change this router for as long as you can please