The Account Is Not Authorized to Login from This Station

[Celinagroup]

I have a 2000 Professional system that can no longer access a mapped drive on a windows 2000 server. The username and password work on other systems, but when you try to access the server from the workstation it says the account is not authorized to login from this station. The problem is for sure on the client, and it is a member of a workgroup as is the server it is trying to access.

 

[bcastner]

Add the following key to the Windows registry:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters]

"EnablePlainTextPassword" = 1 (DWORD)

 

[bcastner]

It is also likely that the username/password has not been added to the Workstation server as a local user account.

 

[Celinagroup]

It is already added. This was originally working and just recently stopped for this user only. I had come across the registry edit, but it was NT 4.0. There is no RPD directory on 2000 Professional, but I was able to find it in LANManager and will try that first. Thanks for the help

 

[Celinagroup]

Turns out that it was already set to 1 so that obviously didn't help. I have searched around but have yet to see anyone with this exact same issue. If anyone has any suggestions I would appreciate it.

 

[wolluf]

This isn't just a policy set on the server?

 

[bcastner]

This is purely a Windows authentication error, not a Permissions issue under NTFS or otherwise.

. If the user is recorded with a valid username/password on the Workstation server;

. If there is not an issue with encrption of passwords (the registry stuff earlier);

Then:

1. Create a new profile, or test from a different username profile that exists. If there is no issue there, your basic workstation connectivity and other potential hive oddness can be ruled out.

2. Create a new profile for the user. Do standard procedures to copy needed data from the old profile to the "new" user profile:

http://support.microsoft.com/?kbid=811151

3. Remove the local user under the old username from both workstation and workstation server. Add the "new" username and password to the Workstation server.

4. You could go through a process of renaming the new profile on both sites, but there is little point in doing so.

As I began this note, if a second or brand new profile does not exhibit the same issues, there is likely corruption in the HKEY_Current_User portion of the registry hives, and the best way to sort this is through the new profile discussed above.

If, an existing alternate user has the same issue; and/or a new user you create has the same issue, do a clean install.

I would not try to do a repair reinstallation in this circumstance. Get the user data copied off from all user profiles on the local workstation and start clean -- including before you zap everything a chdksk /r run on the box.

 

[Celinagroup]

Thank you everyone for your suggestions. The problem was an encryption issue it just wasn't in the registry. I went through the systems (The Client) local security policy and found it(One of the digitally signed encryption options was enabled). Thanks alot for the helpful advice.