SOLVED Unable map network drive on PC. Logon failure the user has not been granted access


Joined
Oct 12, 2015
Messages
6
Reaction score
2
I have two PCs running windows 10, connected to the same network. The first PC has two drives. C:\ drive and S:\ drive: Under properties for the S:\ drive I have selected Share tab -> Advanced sharing -> check "Share this folder". Windows then says that the path of the shared drive is \\MyPC1\S

When I try to map the S:\ drive on second PC i'm uanbles to connect. I get the following warning

"Logon failure; the user has not been granted the requested logon type at this computer"

This is quite weird, because.
1.) It worked fine before updating to windows 10. I was running 8.1 on both machines
2.) The second PC also has a second drive. Let's call it P:\. When I try to mount \\MyPC2\P on the first PC there is absolutely no problem and it work like a charm.

So what fucked up setting, has magically been applied on PC1 and not PC2 during the update?
 
Ad

Advertisements

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
12,329
Reaction score
1,981
Likely a user account name and password with the proper access permissions exist on one and does not exist on the other.
OR you may have an issue with corrupt credentials, check credential manager in control panel and edit or delete the credentials associated with the computer you are having the issue with.
Use
MachineName\UserName
when prompted for authentication credentials.
MyPC1\UserName on MyPC1 who has proper permissions to the shared resources and that user's password.
 
Joined
Oct 12, 2015
Messages
6
Reaction score
2
Likely a user account name and password with the proper access permissions exist on one and does not exist on the other.
OR you may have an issue with corrupt credentials, check credential manager in control panel and edit or delete the credentials associated with the computer you are having the issue with.
Use
MachineName\UserName
when prompted for authentication credentials.
MyPC1\UserName on MyPC1 who has proper permissions to the shared resources and that user's password.
It was some old credentials in the Credential Manager, that caused the problem. Windows simply tried to access the shared folder with some old login-information
 
Ad

Advertisements

Trouble

Noob Whisperer
Moderator
Joined
Nov 19, 2013
Messages
12,329
Reaction score
1,981
Thank you for the follow-up. Glad you were able to resolve your issue.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top