Skip to main content

The sign-in method you're trying to use isn't allowed. For more info, contact your network administrator

Above problem occur when you have not added a group (of which User try to login)  in your local policy login. To resolve the issue, follow the steps,

Log in as the administrator on the server, then start the Group Policy Management Editor by running the  gpmc.msc command from PowerShell or the Command Line window.
1. In the Group Policy Management window on the left hand side, select Group Policy Management.
2. Click to expand the  Forest tree node.
3. Click Domains.
4. Select your domain name.
5. Click Group Policy Objects.
6. In the right-hand window, double-click Default Domain Controllers Policy.
7. Right-click Default Domain Controllers Policy and Select Edit.
8. In the Group Policy Management Editor window, click Default Domain Controllers Policy.
9. Click Computer Configuration, and then click Policies.
10. Click Windows Settings, and then click Security Settings.
11. Click Local Policies and then click User Rights Assignments.
12. In the right pane, click Allow log on locally.
12. Click the Add User or Group button.
13. In the Add User or Group dialog,  enter the name to be added or click Browse.. to search for a name.
14. Click OK .
15. Repeat steps 12-14 if you want to add more users.
16. Click OK to Close the Allow log on locally Properties dialog, and then click Close several times to Close the remaining open Windows.
17. Run the following command in the Command Window to activate the policy changes:
gpupdate /force.
Kindly note that above content is originally copied from

In case if above solution resolve your problem then please comment on it to increase its credibility.


den Danny said…
Worked for me. Thanks
Tony Lodder said…
tried this method but didn't work for me. My problem is with one particular user where she can login to some network machine but not others. I found a work-around by adding the user to the AD group
Domain Admins. Not ideal but at least she can work. Still investigating why this works
Claudia Herrera said…
It Worked ! Thanks Zeeshan Ahmed Memon Blog :)
muhammad ahmed said…
its work man thanks a lot
Anonymous said…
worked for me, thank you
Anonymous said…
thank you its work

Popular posts from this blog

ORA-38104: Columns referenced in the ON Clause cannot be updated

In my case, this error pertains to Oracle Merge query. After 30 minutes of time wastage and a lot of hunting on different forums, I come to know that where and why was my merge query throwing exception.

I was giving multiple criteria in ON clause of merge query, and was also trying to update a column which I have mentioned in ON clause. Once I remove that column from update clause of merge query, it executed successfully.

I hope that this will also works for you.

In case if this post help you, then please comment on it.


Cannot use the special principal 'sa'. (Microsoft SQL Server, Error: 15405)

Yesterday, I start SQL Server 2005 and try to connect with sa user but was enable to connect with the 'sa' user and got this error:

Cannot use the special principal 'sa' (Microsoft SQL Server, Error: 15405)After doing some google, I found out the solution which I am sharing so that others can get all the possible solutions from this article.
The titled message mean that your sa user is disabled. To enable it, you have to follow below mentioned steps:1) you have to change the authentication mode: go to Management Studio and open Object Explorer. Connect to your server and right-click on the server name, then select Properties. Go to Security tab and under Server Authentication select "SQL Server and Windows Authentication Mode".2) Also, after you follow the directions above, you will also need to explicitly enable the sa account as well. Go to Security->Logins. Right-click on the "sa" account, select "Properties". In the list on the lef…