Logon Failure: The user has not been granted the requested logon type at this computer.

Question

_{Monday, December 7, 2015 5:57 PM}

I have an existing network of computers that do not have any issues seeing and accessing each other's files.  They are all on the same homegroup and workgroup.  One of those computer have died and I have replaced it with a new system.  

The new computer is able to access all the computers on the existing network except for one computer (computer A).  No other computers on the network have problems accessing computer A.  As far as I am aware, they are all set up the same way and are all running Windows 10.  

When the new computer tries to access computer A, I receive the following error:

"\Computer-A is not accessible.  You might not have permission to use this network resource.  Contact the administrator of this server to find out if you have access permissions.

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

When I check computer A, sharing is enabled and access permission has been given to "Everyone".  I've also checked the group policy on computer A and network access is available to "Everyone".  It is accessible for all the existing computers on the network so I really don't understand why it is not accessible for the new computer, especially when the new computer is able to access all the other computers without any problems.  

I noticed that if I try to access computer A via its IP address (from the new computer), it will ask me for login credentials instead of giving me an error.  But no login information that I know of appears to be correct (including the user name and password used to login locally).  

Anyone have any suggestions?  Thank you.

All replies (14)

_{Wednesday, December 9, 2015 5:18 PM ✅Answered | 2 votes}

Do you have a goat tethered out back? oh never mind don't suppose that would work anyway.

So to me this is the new computer still presenting a username for the ComputerA (as you do not get prompted for details) but where or what this is appears to be questions.

From a command prompt (right click start choose Command Prompt). Enter;

net use

Any connections showing for ComputerA?

If not can only really think of a work-around of sorts, in the Credential Manager on the new Computer enter a username and password and for ComputerA. Under Windows Credentials enter the computer name of ComputerA and a username and password (if you do not have one than will need create one on ComputerA as a test, hopefully they will be included in 'Everyone' as opposed to the user currently being tried that is not)

_{Monday, December 7, 2015 7:49 PM}

Well no quick answer I think. First does the Homegroup work as expected (expand Homegroup and can you access that PC)? (that is different to Workgroup that I believe you are having this issue with)

On the new computer is there any credentials saved for ComputerA (search start for cred open Credential Manager). On the Windows Credentials side anything saved for ComputerA ? Do any of the working computers have saved credentials for ComputerA ?

On ComputerA is sounds like you want sharing files without a password, so open Network and Sharing Centre choose Change advanced sharing settings (on the left), scroll down and expand the All Network settings, is Turn off password-protected sharing selected?

Applicate it works from other machines but I am thinking a configuration settings has been overlooked on one of the machines perhaps rather than a fundamental issue.

_{Tuesday, December 8, 2015 4:19 AM}

Hello,

See if this helps you:

https://technet.microsoft.com/en-us/library/cc732593(v=ws.10).aspx

Hope this helps, Good luck :)

Windows Troubleshooting & How to guides - http://www.kapilarya.com

_{Tuesday, December 8, 2015 6:20 PM}

ComputerA is visible in the Homegroup, but it thinks it is asleep as it gives me the option to try to wake it.  I've tried clicking "Wake up" to see if I could get ComputerA to be accessible, but it did not seem to work.  

The new computer does not have credentials saved for ComputerA, presumably because it was never able to access it at any point.  All other working computers in the office have credentials for ComputerA.

 "Turn off password-protected sharing" is selected on ComputerA, as is every other computer on the network.  

Perhaps I've been looking at this issue for too long, but I've combed over all possible settings that may affect this.  I'm not exactly trying to do anything fancy either :/  Thank you for your assistance, any more suggestions would be great appreciated!

_{Tuesday, December 8, 2015 6:54 PM}

Gave it a try but did not appear to work.  I also checked to make sure the "allow access by network" and "deny access by network" permissions were set accordingly as well.  I'll try restarting computer A after making those permission changes.  The new computer was restarted.

_{Tuesday, December 8, 2015 8:31 PM}

Well seems to be a couple of issues here. For the Homegroup that does work, remove the new computer from the Homegroup and re-add it. The saved credentials should be there (with a computername\HomeGroupUser$) as far as I know when it is added and it does the check and sync.

So guessing for the other 'workgroup' error you opening the Network part of File Explorer. If so at what point does the error come up? The "Turn off password-protected sharing" should allow connections. So some more checking sorry, but on ComputerA right click start choose Computer Management (assuming Pro), expand Shared Folders, then Shares. Double click the name of the share you have check the Share Permissions tab for Everyone, and the Security tab for Everyone.

If that is good, in Computer Management still expand Local Users and Groups, Users and check Guest is enabled (double click and check Account is disabled is not ticked). If enabled trying selecting disabled and try accessing (as a test the error should change). Then re-enabling the Guest account and try again. Disabling the guest and re-enabling did help in another thread.

_{Tuesday, December 8, 2015 11:48 PM}

Removing and re-adding the new computer to the Homegroup created the credentials, but I was still unable to access ComputerA.  The same error was shown.

For the "workgroup" error, the error message shows up the moment I try to access ComputerA (ie: double clicking on the ComputerA icon under Networks).  All of the share permissions are good in Computer Management.  

Tried to disable and re-enable the Guest account, the error is still persistent.  I noticed that when the Guest account is disabled, there was no difference in error message.   I was also still able to access ComputerA from the other computers.  

Anything else I should check?  I'm just about ready to form a pentagram with candles on the floor of our office, and offer a sacrifice to ComputerA in hopes that it grants me mercy.  

_{Wednesday, December 9, 2015 6:04 PM}

the 'net use' command is only showing me all of the mapped drives on the local computer.  If I map a drive to computerA from the other working computers, the connection to computerA is shown.  Since the new computer can't make any sort of connection to computerA, I am unable to map a drive for it, and therefore, no connection to computerA is present.  

I will give that workaround a try.  Thank you!

_{Wednesday, December 9, 2015 6:18 PM}

Brilliant!  That work-around did the trick.  I suppose it's not ideal but at this point, I'll take whatever gets the job done.  Thank you again for your assistance!

_{Thursday, December 10, 2015 9:26 PM}

Well interestingly I have seen something similar on my machines since my last post in this thread. I was prompted for a username when trying for an open 'everyone' share (that others machines could access ok). So the first time I put MACHINE\Guest and got access. Today on a different machine with a open share (I keep open shares on a lot of my test machines) go prompted for username, so thought I will enter MACHINE\MadeUp, and got access (yes a non-existent account).

So what is the scoop of 'everyone' I wonder, means perhaps everyone the machine knows. So if you say I am ANOTHERMACHINE\someone perhaps the local MACHINE everyone says well no then. Still wonder what you new computer was telling ComputerA and that was just saying no, a flat no not a prompt for username. (could go for packet trace to try find that perhaps)

Someone once said 'Windows 10 is like a box of chocolates...'

_{Friday, December 11, 2015 5:47 PM}

I'm pretty sure I read that one of Windows 10's requirements is for the user to be at least a level 2 wizard.  

I wonder if it has anything to do with the difference between the windows 10 versions.  All of our workstations (including computerA) are running windows 10 pro.  The new computer, meant to be a cheapy machine strictly for printing production labels, shipped with windows 10 home.  

_{Friday, December 8, 2017 7:37 PM | 1 vote}

I had this same problem, but not with a new PC.  My LAN is 5 PCs (4 Win 10 & 1 Win 7).  Three of the Win 10s would connect with the Win 7, and the that wouldn't gave the "Logon Failure: The user has not been granted the requested logon type at this computer" diagnostic panel.  Following the advice above I went to the credentials manager on the non-connecting PC and found the credentials it was trying to use were wrong.  I edited these to what I know to be correct for the Win 7, and that fixed the issue giving a connection.  Can only say BIG Thanks to -Mr Happy-!

Pelcaro

_{Monday, May 28, 2018 7:57 AM}

In case anyone wants to know, this error just occurred for me as well.

What worked for me was:

Run the following command from the command prompt:
rundll32.exe keymgr.dll,KRShowKeyMgr

Then add in the credentials that you require.

While you are there, search the list for your greatness... and backup to a secure site. :)

_{Friday, September 28, 2018 9:21 PM}

Thank you, this worked for me.