I am having a hard time understanding what is needed from D5 to set a Synology quickconnect folder address for an Team asset or project folder.
I have used the D5 Synology guidelines in the user manual to setup a shared folder within our synology listed here, and have our other users able to connect and sync over WAN via the Synology Drive Client on Windows.
However, there is no information in the user manual on what D5 look for in a WAN address. I have setup the Synology quickconnect to be accessed from remote users, and have tested it successfully over multiple use-cases with a web browser and Windows file explorer via the Synology Drive client.
This is all the User Manual mentions:
*3. If you need to use the team asset library in a WAN environment, there are three ways to achieve it: *
a. Use the VPN provided by the company’s IT department to access the internal network. *
b. Apply for a public IP address from the ISP. *
c. Use a network proxy provider, such as Synology NAS Quick Connect.*
Is there any info somewhere on what specifically to use as the folder address for a Teams asset or project library?
Only the owner or administrator of the team version can configure shared folders. To avoid errors, please use the owner or administrator account for the configuration.
If the shared folder is password-protected, others can only access when the password protection is turned off.
I have setup the Synology NAS QuickConnect, and have tried multiple variations of the folder address into the Team setup, and none of them are allowing the other team member to access.
My team member can access the QuickConnect location over WAN in outside scenarios, but D5 doesn’t seem to register the address, nor allow other Team members to access it through the D5 system.
So the QuickConnect has been tested and is setup correctly, I just need assistance in translating the address to a format where D5 will provide access
Could you double-check the permissions for the user and any relevant groups to ensure they are set correctly? When you encounter privilege conflicts, the privilege priority is as follows: User > Group.
I know that, which is why I said “I have setup the Synology NAS QuickConnect, and have tried multiple variations of the folder address into the Team setup, and none of them are allowing the other team member to access.”
Hi @wellebracht Could you please share a screenshot of the Team Library setup so we can confirm your shared folder address format. Apologies for the inconvenience.
Here’s what I currently have set, but i don’t believe this is correct, as it works for me but not the other teammate. I’m sure this is the LAN address, as it doesn’t have any quickconnect addressing associated with it
No, they cannot. I have that path in there, because it is the LAN path that works so that I may, at least, use the library. I also removed the username and password.
A Quickconnect address looks something like this (the example below is not real, as I’m not posting server access on the forum, just as an example)
However, the D5 Team library does not support an address like that, as far as I can tell. Since the User Manual says it supports Synology QuickConnect as a server over WAN, what kind of address format does it need?
Just as a clarifying point, all of these addresses we have been testing and that you guys have requested are a File Explorer address. My primary question has been regarding the format of the Synology Quick connect, which creates an HTTP or HTTPS address for WAN connection and is not SMB compatible.
It is looking to me like any HTTP or HTTPS address is incompatible with the Team library directory, is that correct?
Just to share the information that I was able to provide to you via Direct Message:
Different network proxy providers offer varying services. Only services that provide public IP access can meet this requirement. Some network proxy providers do not offer this functionality, and it may also involve additional paid services for public penetration access, etc.
D5 just provides an entrance to put in the path for sharing the team library folder, provided that this path is already shared—team members can access it normally&directly (as shown in my video, the address I copied from NAS was accessible to others before being deployed into D5, even if the members WERE NOT LAN users).
You may need to contact your ISP provider to convert this nameoftheserver.quickconnect.to into something similar to this \MDF_2-bay\D5Team\Projects (which can be used to input in D5 Settings for team sharing)
Our users who are using this setup usually contact their IT, and IT would interface with their ISP since usually contact with their IT, and IT would interface with their ISP. We just provide an entrance to put in the path for sharing the team library folder.
It is looking to me like any HTTP or HTTPS address is incompatible with the Team library directory, is that correct?
Indeed, HTTP or HTTPS can not be used as an address for the Team Library Location. Some ISPs would provide that public IP Address hence the reason why other teams can use the Synology Quickconnect.
Ok, I got it working on my end by bypassing the QuickConnect system entirely due to incompatibilities and just used Tailscale. I also ran into a few issues while trying your suggestions:
My ISP told me that they cannot change an IP address to mimic a file path. Also, the Synology quickconnect tunnels out of your network and uses the Synology servers as a proxy, so an ISP has no control over that anyway.
The Synology Quickconnect service, to my understanding, only outputs access to the NAS and file station via HTTP or HTTPS links (info found on Synology’s Knowledge Base)
So, for the fix, I installed Tailscale on the Synology NAS (you can download it for free in the Synology’s Package Center).
Once it’s installed, clicking on it will take you to create an account (for free) and it will add the NAS as a device. Once added, it will give you a public IP for that device only, which you can use to navigate to inside the Windows file explorer.
This is the same address you will put into the Team Library Deployment Folder Address
To share this Tailscale IP out, the other users need to create an account, then the owner sends them a link via email from the Tailscale account online. Sharing the IP before doing this will not allow them access.
Once that is done, they just follow the same protocol of adding a file path with the Tailscale public IP in their file explorer, and you’re good to go!
Hope this helps anyone else that doesn’t have an IT department to farm this out to!
Thank you for sharing your detailed Tailscale workaround to bypass QuickConnect. We recognize the challenges posed by ISP incompatibilities regarding IP address-to-file path conversions. Your information is crucial. We will immediately share this with our team and update our User Manual to reflect this alternative approach.
