Windows authentication failed on only one machine

I have a Windows machine trying to access an IIS server on which Windows authentication is enabled. I know this works on the server side, since I logged into my domain account on another machine, and others in my block can access the specified URL without having to log in (the browser does this automatically).

I am stumped because my own development machine cannot log in (and still displays a login window), and I need some help, or at least a few ideas on what else needs to be checked.

I checked tools -> Internet settings -> security -> local intranet -> advanced settings -> user authentication, where it is configured to automatically provide a username and password.

My workstation is Windows 7, like the others in the office, but as a developer, I have no doubt that I changed some settings on a client that I do not need.

Any ideas?

Update: if that matters, it also fails in Chrome without a registration window, just "Error 10 (net :: ERR_ACCESS_DENIED): Unknown error"

+6
source share
5 answers

I ran into a similar issue with chrome and was unable to open any intranet websites. I did everything to solve this problem, but nothing came out very upset. Finally came across the aforementioned post. Looking at the lines

I checked tools -> Internet settings -> security -> local intranet -> advanced settings -> user authentication, where it is configured to automatically provide a username and password.

got some clue. I was curious what the username and password are if we check the "automatic username and password" field, and that was the solution.

The automatic username and password are taken from Windows Vault (find "Network Password Management" inside the control panel). In my case, there was an entry in the Windows credential category. It was the username and password that were used if we checked the "automatic username and password" field in tools -> Internet settings -> security -> local intranet -> advanced settings -> user authentication.

Thus, the decision is either correct that recording or deleting this record at all, if you are sure that you do not require it elsewhere.

+20
source

Chrome sharing security settings in IE. Open your page in IE, go to tools → Internet settings → security tab → Local intranet → Sites → Advanced → Add this site to the zone field → Enter the website you are trying to visit on which throws ERR_ACCESS_DENIED error, including the correct protocol that you use, for example, http or https, and click the "Add" button. In the "Security" section, continue to make sure that the intranet zone is highlighted and click the user level button in the (last) section of the "Auth" section user authentication "make sure you select the following option: Automatically log on only to the intranet zone

If you are logged into a domain and your website uses integrated Windows authentication, this permission will work and you can get rid of ERR_ACCESS_DENIED.

After that, if it does not work, clear your browser of the elements from the browser cache: Cookies and other site data and the plugin Cached images and files

Restart your browser.

If it does not work, restart the computer.

"For me, a restyled car helped"

If it still doesn’t work, change “Automatically login only in the intranet zone”, return “Request username and password” in IE settings and restart the browser and try again.

Good luck

+3
source

Just leaving this here for posterity, I had the same problem after visiting the site using NTLM and accidentally using the old password. clearing cache / cookies, etc. didn’t affect, restarting Chrome didn’t, I was at a dead end.

Then I realized that due to the Chrome launch, I had processes running in the background, so I killed them, and after that everything worked as expected.

+1
source

Save Chrome credentials in Windows Vault (start searching in Windows Vault), you will see your credentials. possibly outdated.

+1
source

I had this problem.

The solution was to close all instances of Chrome.

Yesterday I changed my Windows password. Chrome may have had caching associated with this old password.

0
source

Source: https://habr.com/ru/post/920378/


All Articles