Tips and common error messages for Windows when mapping a network drive

From SynologyWiki
Jump to: navigation, search


Please refer to the How to share data locally using the Synology server as a File Server for further background information about this article. This article will cover tips and common error messages for Windows-based systems with regards to mapping network drives.


Seamless integration between Windows and the Synology System

To allow for easy integration between Windows and the Synology system, it's recommended to use the same username and password on both the Windows computer and the Synology system. This way, users can access the Synology system without being prompted for a username or a password. This section will cover how to identify the username on a Windows System. To set the username on the Synology system please look here.


Clarification

Note in the following image that Synology Demo User is not a user name. This is a screen name (or the name of the user), which is used for a "friendlier" interface for users to select their profile. This is not what Windows uses as the username.

UserName1.jpg

Method 1

To identify the username, from the Administration-ranked profile, Go to

  • Control Panel
  • Administrative Tools
  • Computer Management
  • On the left hand pane, go to
    • Computer Management
    • System Tools
    • Local Users and Groups
    • Users


Under the Full Name category is where the screen name of the account can be found (Synology Demo User); under the Name column is the username of the account.

UserName2.jpg

Method 2

  • Go to Start/Windows Orb
  • Type cmd in the Run/Search box
  • Type set in the Command Prompt
  • The username is the third property from the bottom
UserName3.jpg


Start-up scripts

A start-up script is a batch file to automate the creation of map drives when a user beings a Windows Session. This method of mapping drives can be used instead of using the Windows Explorer or the Synology Assistant. This method of mapping drives is meant for experienced Windows Administrators in a multi-computing business environment.

Creating a Start-up Script

Create a plain text file, titled login.bat with the following code

net use * /d /y
net use z: \\synologybox\synodemo /user:synodemo password /persistent:yes

And place the file in the user's start-up directory, or assign it to start-up when the user logins to the Domain Controller

BatchScript.jpg

Notes

With regards to the file name login.bat, any file name can be used, however the extension must be .bat


Error 53

Before anything else, verify your network connection properties and make sure "Client for Microsoft Networks" item is installed and enabled. Otherwise, connecting to shares will fail with error 53 without much details.

A common error seen with Windows computers is Error53, or more ambiguously, user permission errors due to Windows caching permissions. This is seen when the Guest account is enabled on the Synology System, and a user attempts to access a private share on the Synology system. The user may not be able to see the prompt for asking credentials, or see a network path resolution error. The following steps are designed to purge Windows of any cached permission it remembers and set up the Synology system to verify the credentials of a user before giving access to a private share.


Step 1

  • Go to Start/Windows Orb
  • Type cmd in the Run/Search box
  • Type net use * /d /y in the command prompt and and press enter.
Error53.01.jpg

Step 2

  • Go to the Disk Station Manager of the Synology System
  • Proceed to Privileges -> Users
  • Double Click the Guest account and disable it.
Error53.02.jpg

Step 3

  • Verify that no network drives appear from Windows Explorer

Step 4

  • Launch Control Panel on the Windows Computer
  • Open the User Accounts Manager
Error53.03.jpg

Step 5

  • Select the account currently in use, or wished to clear the permissions of
  • Click Manage my network passwords
Error53.04.jpg

Step 6

  • Clear the entire list
  • Note
    • Here is where Windows can be program to remember a credential when it is asked to use a specific network resource
Error53.05.jpg

Step 7

  • Close all programs and restart the computer.
  • Proceed by mapping a drive for Windows
  • Windows should display a prompt for username and credentials if the permissions are purged correctly.

Another checking point, please ensure "Client for Microsoft Networks" is installed. Thank for Alexander's great help:

Windows network.jpg

Notes

For a faster method of performing step 4, 5, execute the following

  • Go to Start/Windows Orb
  • Type control userpasswords2 in the Run/Search box
  • Click Advanced
  • Click Manage Passwords
  • Purge (or add to) the list
ControlUserPasswords2.jpg

Error 67

Error 67, where The network name cannot be found is where the name of the path is incorrect or cannot be found. Please verify that...

  • The DNS Name Resolution is operating correctly
  • That there are no other devices on the network which are using the same DNS name
  • Please attempt to map the drive using the IP address of the Synology system


Error 85

Error 85, where The local device name is already in use is where more than one network connections is being mapped to a local drive letter. Please select a different drive letter to use.


Error 1231

Error 1231, where The network location cannot be reached is primarily caused when the File Sharing services are not enabled on the Windows computer, or is being blocked by a anti-malware security program, such as Windows Defender, Norton Internet Security, ZoneAlaram, to name a few examples. To resolve this error, make sure that File Sharing Services are enabled for Windows, more information about that can be found here. With regards to the software configuration, please consult with each manufacture's/developers support system, consult with the Synology Community Forum or a network consultant to resolve this error.

Personal tools
Community Resources