![]() ![]() I have tried generic “fix” attempts like “sfc /scannow” and the Network Troubleshooter, but these found nothing and made no difference. You can select any drive letter, it doesn’t matter which. It seems like something is trashed in the SMB (v3) and/or NTLMv2 password encoding, but the “broken” Windows machine can still connect to the laptop running Windows, so somehow it’s only broken when talking to the WD My Cloud Mirror devices … BOTH of them! And this was all working a week ago!Īny suggestions for how to debug this? I am wondering if I need to do a packet trace in WireShark and read SMB/NTLMv2 documentation to figure it out. From the Map Network Drive window, use the dropdown menu to select a drive letter. ![]() Source: Windows Central (Image credit: Source: Windows Central) Click on This Computer. I created a new user (“test”) on one of the NAS devices with password “test1234” and this fails to connect as well. On your Windows 10 PC, open Synology Assistant. We made changes to network/sharing discovery, and we changed our login. We tried repeatedly mapping the drive via Synology Assistant and the system repeatedly times out. The laptop connects fine, in both Windows and macOS, using the same user name and password. We have a Syno 1019 that we mapped in Win 7 () and somehow cannot manage mapping a drive in Win 10 for another Synology NAS ( 220 ). The specified network password is not correct. SYNOLOGYNAMEuser You can map the server using the hostname too, like SYNOLOGYNAMESharedFolder Good luck LivingOther 1 yr. ![]() After, map the network drive using the domain format in the username, i.e. How To Map a Drive with Synology and Windows 10 BrenTeck IT Support 1. Net use M: \NAS8TB\MacBookFileHistory /pers:yes /user:tadĮnter the password for ‘tad’ to connect to ‘NAS8TB’: In Synology, go to Control Panel > File Services > SMB > Advanced Settings Then, sent minimum SMB to SMB2 and maximum to SMB3. The failures are always “incorrect password”, and happen for both command line and Windows GUI (File Explorer “Map Network Drive”) attempts. The Windows machine has no problem accessing the NAS devices over the web (admin UI), and a dual-boot MacBook Pro (macOS Big Sur and Windows 10) can mount drives on both devices just fine. I am at a complete loss for what went wrong, but a Windows 10 box that was working well with both of my WD My Cloud Mirror servers (both now running OS5) has lost the ability to mount drives (shares) on either NAS device. DS 718 upgraded from 6.x to DSM 7.1.1 now cant map drive in Windows 10 using Synology Assistant : r/synology by Subharmonicgroove DS 718 upgraded from 6.x to DSM 7.1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |