![]() NOTE!!! The WINDOWS CREDENTIALS is the SAME as the NAS Credentials!ħ) Tick "OPEN THE MAPPED DRIVE" Box in the Lower Left Corner of the Assistantĩ) Repeat Steps 2 thru 8 for Each Drive to be Mapped Tick Box "Reconnect at Logon" Located at Bottom Left Of Wizardĥb) A "Windows Security" Box will Open> Enter your NAS Name & Password & "Remember Your Credentials" > Click "OK". Highlight Shared Folder to Be Mapped with Drive Letter (Click Next)ĥ) Use Dropdown DRIVE Box to associate Drive Letter to correct share New Additional Drives cannot be added later and you will need to Start from the beginning and Map ALL the Drives.ģ) Enter Name + Password of NAS/Synology Login- "admin" + "password" NOTE: After the First Drive is Mapped, Each Additional Drive to Be Mapped will allow you initially Login with "Previous USER Name"Ĥ) Use Predetermined Drive Letter Assignments to Correctly Map the Drives desired Note: You must Map All Drives Desired in a single Session. Good luck!Ī) WIN 10> Control Panel> File Explorer Options> Advanced Settings> Hidden Files and Folders> Show Hidden Folders> Apply> Okay to Closeī) Control Panel> Network and Sharing Center> Advanced Sharing Settings> Change Sharing Options for Different Network Profiles> Guest Or Public> Network Discovery> "Turn On Network Discovery"> File and Printer Sharing> "Turn On File and Printer Sharing" > Save Changesġ) Install Synology Assistant - You will use the Map Drive Function within the Assistant for the below steps. Please Let me know if this resolves your issue. Just be aware that my procedure worked for me on a CLEAN install, not on one that had previous changes made to it that may interfere with the setup. ![]() Note: When I originally needed and learned about Mapped Drives and I could not get them to stop the dreaded RED X reoccurrence after Re-Boot, I must have tried at least 25+ Changes in the Registry, Security, and other locations. I've documented them as I use them as reference whenever I set up a new drive. I can't guarantee your success, but attached is the procedure I use. After switching to Synology and through nothing but trial and error, I finally resolved Mapping Drives, and they do not reoccur with Red X. Several years ago, the RED CROSS was an ongoing issue for me (and others) and I exhausted every possible solution that was suggested with no positive result. Since I didn't have that problem in the past, and due to the fact that Raspberry/Samba shares have no problem, I suspect it is a WIndows thing. > "Unavailable" -> click on icons -> "OK" Only the Synology drive show this behavior. The strange thing is that this problem does NOT occur with two drives I have mapped to shared folders on my Raspberry Pi running Samba. Then, when I go to Windows Explorer and click on the drives (which are showing red crosses) they will connect, change to green and the mappings can indeed be used as normal. Then, after an immediate restart of the laptop, I goto CMD again and 'net use' will show them as "Unavaliable". But after the latest update, my drives refuse to remap automatically after a cold start.Īfter powering up my laptop and issuing a 'net use' command in CMD, they show as "Disconnected". My Synology shares always remapped flawlessly after a shutdown and a restart of my Win10 laptop. This sounds very similar to a problem I'm experiencing since the latest Windows 10 update. Is there any way to do this? I'm running a DS918+ on ubquiti network gear if it matters. Basically I want it to act like a normal drive that is physically installed in the PC. I also don't want the drives to be losing the connection and essentially going dead all the time. Meaning, I want to be able to access a mapped drive anywhere I have internet access via file explorer and not having to use DSM or Drive and without having to re-login to the drive. I'd like a more robust system, and ideally, I'd like to be able to access the mapped drives even when I am not on my home network. ![]() If I disconnect the computer from the network or shut it down, I lose connection to the mapped drives and almost always end up disconnecting and re-mapping all of them and it is getting very old. I thought my problem was solved, but it was not.Ĭurrently I am always re-mapping the drives using Syno Assistant. I while back I posted this thread of my mapped network drives disconnecting: Solved - Why do my mapped network drives keep disconnecting?. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |