One of my machines was giving me a headache. I could not connect to my Synology file shares. All my other machines in my could just fine except this machine. Even after a reinstall it didn't work. I kept getting the error:
If the Networking setting is DHCP and DHCP server has WINS server service, DS-106 will not remove the WINS server setting. The reason is the existence of WINS server will make the DS-106 functions work in Windows network environment smoother, so as long as there is a method to get the WINS server information, DS-106 will not delete the. Powered by Synology Surveillance Station. Add functionality to your device with powerful collaboration, backup, communication, and management tools. Download and install Synology-developed and third-party packages directly from Package Center. Synology Directory Server provides Active Directory (AD) domain service powered by Samba. Synology Wins Server Setup Posted on 8/3/2018 by admin For those of you using a NAS for storage and mapping your drives it is important to note that in the November update for Windows 10, Microsoft has somehow changed their supported SMB protocol to 3.1.1 preventing one from mapping their NAS drives. This tutorial goes over how to use your Synology NAS as a DNS server! This allows you to not only speed up your networks internet access by caching DNS reque. Window users will locate the system more easily on TCP/IP networks if the system has been configured to register with a WINS server. Maximum SMB protocol: Depending on your network configuration, set the latest SMB protocol that will be supported by your Synology NAS. SMB1: SMB1 (also called CIFS) has been supported since Windows NT.
The specified server cannot perform the requested operation.
The difference between the machines working and not working was the machine not working was Azure Active Directory Joined. The other machines weren't. The strange thing was, my work machines are AADJ as well but to a different Azure Active Directory (from my work). I have my personal directory since I host my families O365 mailboxes. Apparently it has to do how Windows tries to connect to shares with different methods, and after 2 it fails. It happened to be the wrong ones it tried first. I also checked if the SMB versions where setup correctly on my Synology, make sure it's not set to SMB1 since that's very insecure.
After reaching out on twitter one of my colleagues (Barry Dovans) had the simple solution. I'll link to the twitter thread so you can read why it's not working. (I have no clue what pku2u is but it was part of the issue)
- Search for credential manager
- Open it
- Click on Windows Credentials
- Click on Add a Windows Credential
Synology Media Server
The difference between the machines working and not working was the machine not working was Azure Active Directory Joined. The other machines weren't. The strange thing was, my work machines are AADJ as well but to a different Azure Active Directory (from my work). I have my personal directory since I host my families O365 mailboxes. Apparently it has to do how Windows tries to connect to shares with different methods, and after 2 it fails. It happened to be the wrong ones it tried first. I also checked if the SMB versions where setup correctly on my Synology, make sure it's not set to SMB1 since that's very insecure.
After reaching out on twitter one of my colleagues (Barry Dovans) had the simple solution. I'll link to the twitter thread so you can read why it's not working. (I have no clue what pku2u is but it was part of the issue)
- Search for credential manager
- Open it
- Click on Windows Credentials
- Click on Add a Windows Credential
Synology Media Server
- Add your diskstation network path and share, add your username (I used diskstationusername) and password.
Can't Find Synology On Network
- Click OK, and now browsing to your share should just work.
