Friday, 13 March 2015

Windows Share - Error - The mapped network drive could not be created because the following error has occurred: The account is not authorized to login from this station


Symptoms:
Suddenly unable to map a drive to a network drive which previously you were able to map to fine on a particular workstation/server. Curiously, you can map to the share fine from other servers/workstations but this one particular machine won't play ball.

Error Message:

"The mapped network drive could not be created because the following error has occurred:  The account is not authorized to login from this station"

Potential Fixes:

Check permissions on share - have they changed at all? 

If the permissions look ok it's time for some compare and contrast - between some settings on a machine which will allow the drive to be mapped and the problem machine. 

First off, on each machine open the Local Security Policy console (secpol.msc). Check the following settings on both machines:



Are they the same? If not then it may be worth having a look at what group policies are being applied to the respective machines. If the way in which the two machines are attempting to sign their communications is different this may well explain the drive mapping issue. 

Next port of call, assuming the difference isn't the Local Security Policy, is the registry.  Generally, you'll want the following registry settings to be the same on both and, most likely, you'll want them to look like this:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters
  • enablesecuritysignature = 1
  • requiresecuritysignature = 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
  • enablesecuritysignature = 1
  • requiresecuritysignature = 0
In my experience this last point is the one which tends to resolve the issue but since tweaking the registry can be a bit dicey, this option is best left till last!

No comments:

Post a Comment