can not map drive [merged thread]

[EricSch]

It seems that nobody has a clue, what the real reason is.

In my case, I can only tell that the problems started with the DM 3.0 update.
Is used before Vista, Win7 64Bit, Win2008, all worked fine until update to DM 3.0.

So the problem are changes in the DM.
Would be nice when Synology address all these issues.

My solution is to restart the DS.

[HJW]

Hello SteenHess,

nice to hear that your problems have gone but...
For a good understanding: I do not have any problems creating shares on my Synology DS1010+ and accessing them via drive mapping from a running Windows Xp, Vista or 7. But accessing those shares by a certain service that was set up to run with the same user name and password as the interactive user is not possible on most of the different Windows installations I have come across. Only on a few I succeeded although the service installation set-up was the same.
No access via drive mappings and no access via a url, just repeated requests for the user name-password combination.

Best regards,
Henk

[piccioni]

Hello,

putting my Sonology DS1010+ to work was a piece of cake but getting the shares to function under all circumstances...

Starting with Vista, Microsoft has changed the way Windows identifies itself over the network. The new default way is said to be more secure. However, many non-Microsoft operating systems used on nas systems do not support that way of identification. In the manual of my older Conceptronic CH3SNAS two-bay nas there is this info:

----- Begin manual info -----
! Windows Vista Network Note !
The security policies which are being used by Windows Vista are not supported by the Samba software in the CH3SNAS.
Therefore, to use file shares/folders of the CH3SNAS, you need to change this the security policies of Windows Vista.
Changing the security settings.
1. Click "Start" -> "All Programs" -> "Accessories" -> "Run".
2. Type "secpol.msc" and click "OK".
3. Allow Windows to open the Security Policies window by clicking "Continue".
4. Click "Local Policies" and choose "Security options".
5. Right click on "Network security: LAN Manager authentication level" and select "Properties".
6. Change the value "Sent NTLMv2 response only" to "Send LM&NTLM - use NTLMv2 session security if negotiated".
7. Click "Apply" and "OK" and close the Security Policies screen.
8. Reboot your computer.

You can now map a network drive to your computer with the steps below:
1. Right click on "Computer" and select "Map network drive...".
2. Select the drive letter you want to use (for example "Z:").
3. Type the folder which you want to map (for example "\\CH3SNAS\Volume_1").
4. Click "Different user name" and type the username "Guest" (or another username) and the password which is configured for the CH3SNAS share.
5. Click "OK" and Click "Finish".

Your CH3SNAS share is now mapped to a driveletter on your computer.
----- End of manual info -----

Note that not all Windows versions have that secpol.msc. However, using RegEdit for group 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa' and giving key 'LmCompatibilityLevel’ value ‘1’ should also get you there.

I have succeeded defining shares after the above mentioned change on a few systems whereas other Vista/Windows 7 systems did still not succeed in accessing the shares. So it looks to me that this is not a final solution for the problem.

Under certain circumstances, I cannot use shares on my Synology DS1010+ too like you all, neither from XP nor Vista nor Windows 7. As reported by others I also get the user/password error continuously.
Does someone have additional info to try?

Rgards,
Henk Wissink.

Thank you thank you thank you! Now I finally managed to Map network drives from my DS202j, and can happily use Total Commander (wonderful program) to upload and download files in high speed in Windows 7 to/from my DS212j.

Oh, and I really recomment people to try out Total Commander when transfering files to and from their NAS, its "safer" than just drag-and-drop (safer in this case meaning the files are being checked while transfering, resulting in no corrupt or incomplete files).

Cheers!