Windows authentication failing on one machine only

Question

I have a windows machine trying to access the IIS server that has windows authentication turned on. I know this works on the server side as I had logged into my domain account on one other machine, and others in my unit are able to access the url in question without the need to log in (browser does that automatically).

I'm stumped as to my my own development machine is unable to log in that way (and still displays a login box) and would like some assistance, or at least a few ideas of what else to check.

I have checked tools -> internet options -> security -> local intranet -> advanced options -> user authentication, where it is set to provide username and password automatically.

My workstation is windows 7 enterprise, like the others in the office, though as a developer I don't doubt I changed some setting on the client I didn't need to.

Any ideas?

Update: If it matters any, it also fails in Chrome without the login box at all, just a simple "Error 10 (net::ERR_ACCESS_DENIED): Unknown error"

Answer 1

I have faced similar problem with the chrome and was not able to open any intranet websites . I did everything to solve it but nothing worked got really frustrated. Finally came across to the above post. By looking at the lines

I have checked tools -> internet options -> security -> local intranet -> advanced options -> user authentication, where it is set to provide username and password automatically.

got some clue. I was curious what is the username and password used if we check the 'automatic username and password' box and exactly this was what was the solution.

The automatic username and password is taken from Windows Vault(Search for "Manage Network Password" inside Control Panel). In my case there was an entry in the Windows Credentials category. This was the username and password which was used in case we have checked the 'automatic username and password' box in the tools -> internet options -> security -> local intranet -> advanced options -> user authentication.

So the solution is either correct that entry or remove that entry altogether if you are sure that you don't require it elsewhere.