![]() ![]() You should see your NAS listed here with its status showing as Connected. ![]() Tailscale doesn't use its own authentication system instead, it works with leading SSO identity providers including Google, Microsoft, GitHub, and more.Īll you need to do is authenticate with your Google or Microsoft account, and do the same on any of the client devices where you want to use Tailscale.Īfter logging in, you'll get to the admin interface where you can see the machines that are connected to your Tailscale network (Tailnet). Navigate to the Synology Package Center.Īfter Tailscale has been installed on your NAS - I have it running on my DiskStation DS1522+ - you will need to log in to the service.The Tailscale client is available natively on DiskStation Manager, and installing it on your NAS takes a few minutes at most. The key differentiator for Tailscale (other than the security) is just how easy it is to set up and use. Tailscale and Synology: How to set up and use Let's take a look at how you can set up Tailscale on your NAS. All traffic is encrypted by default, so you're guaranteed a secure connection. The service is based on the Wireguard protocol, uses hourly key rotation, and doesn't have any traffic going through Tailscale's servers. The best part about Tailscale is the fact that it takes less than 10 minutes to set it up. Unlike a traditional VPN that relies on a central server, Tailscale uses a peer-to-peer mesh network to facilitate connections. Tailscale is a zero-config VPN that lets you securely connect to devices over the internet. Tailscale: Access your Synology NAS from anywhere So I disabled QuickConnect, and made the transition to Tailscale. While I used QuickConnect for a long time, I wanted to use a Wireguard-based tunneling solution for increased security. In short, QuickConnect delivers the easiest way to access your NAS remotely, and it works seamlessly with Synology's first-party utilities like DS audio, DS video, DS file, and so on. Synology has easy-to-understand documentation that talks about how QuickConnect works, and it also goes into detail about the service's security. Unfortunately, the error message generated doesn't really tell you where to start looking.When that isn't feasible, the service leverages Synology's relay server to establish a connection between the client device you're using and your NAS. With all that said, the issue seems to be associated with the 'more secure environment' created with DSM 7. I have reversed the regedit change & it is now back to where it was prior to the change. To say I'm a little disappointed with DSM 7 would be an understatement. I intentionally delayed upgrading to DSM 7 to allow time for the upgrade to settle down. Unfortunately, these are production PC's/NAS devices with established processes & users that are accustomed to accomplishing tasks in certain ways. ![]() What was once an easy task, has now become an exercise in WTF is going on? Both the NAS & the PC were rebooted, but, still did not work.Ĭoincidentally, we use WebDrive as a tool in mapping drives on the NAS devices & they too have ceased to function with DSM 7. The fix they provided involved changing some of the SMB settings in File Services within the Control Panel. I did talk to Synology support yesterday & mapping the drives via Synology Assistant has been an issue. Gerard, I have no problem mapping the drives via Windows as you described from any of the PC's. Thanks for all your suggestions and comments. In any event, I can now map a drive on my laptop to either of my Synology systems running DMS 7. My son then edited the registry on my laptop, basically (as I understand it) enabling Windows 10 to accept NTLMv2. Anyway, when DMS 7 rejected my NTLMv1 request, my laptop running Windows 10 just gave up trying to connect. It seems that my laptop wanted to use NTLMv1 and DMS 7 will not accept it. " As I understand it, NTLMv1 is a security protocol used when two computers are connecting to each other. He logged onto my laptop, did some fiddling, and discovered the following log error: "User xxx from yyy failed to log in via do to. Last night I explained the problem to him. My son is a network security guru for a very large hospital system. Finally found the solution to the problem (actually my son found the solution.) Turns out it was an issue with my Lenovo P52, Windows 10, and Synology DMS 7. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |