![synology wins server setup synology wins server setup](https://kb.synology.com/_images/tutorials/Access_Shared_Folders_within_LAN_Windows_50/image1.png)
Nucleus - Discrepancies with instructions. By the way, fellow medic? Windows 10 newest updateSMB 3. Based on the info from other users on this site, one can indeed just define the path.
SYNOLOGY WINS SERVER SETUP UPDATE
It did in the past, not sure when it disappeared I assume with the problem update you are talking about. Maybe l, as you said just entering the network pathway will do the trick. I am using link aggregation on the Synology as I have a Windows Server also set up with link aggregation. Encryption is set to auto and smb set to 3 on the synology everything else is the default values. Same workgroup name on the synology that all my windows machines are in. The only package I have enabled on my synology is cloud station. This has been all over the NET of people trying to figure out what happened, waiting for a fix from Microsoft, but in the meantime, as the link I posted in the OP reveals, a way around it by shutting down SMB 3 on the machine you are working with. If you did that latest huge fix I would be curious if you did anything to enable your computer to see the NAS. Need to disable smb3 on the win machine should fix it. The temporary fix I found, after driving myself crazy for days, resides on the Synology Forum. I am not sure if this strictly a Microsoft issue or an issue for the NAS companies to address in firmware.
![synology wins server setup synology wins server setup](https://www.ask-corp.jp/products/images/synology/ds220plus_05.jpg)
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.