This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox version 40 will no longer log into IIS 2003

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by cecche100

more options

Logging into IIS (with integrated windows authentication and basic authentication) on a windows 2003 server used to work with all versions of Firefox. Clients updated to version 40 and Firefox no longer displays the windows authentication log in box.

After updating to Firefox 40.0 , when they tried logging into the site they get this message : You are not authorized to view this page You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept.

Please try the following:

   Contact the Web site administrator if you believe you should be able to view this directory or page.
   Click the Refresh button to try again with different credentials.

HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration. Internet Information Services (IIS)

Three others are having the same problem. They have been using Firefox for years and did not have any problems. Last Week Firefox upgraded to version 40 and now none of the Firefox users can log into the server. They all had to switch over to Internet Explorer or Opera.

Is there a fix for this? I assume it has something to do with windows Server 2003 Kerberos Authentication. Has something been removed from Firefox 40.0 ?

As I test I logged in using an earlier version of Firefox (something around version 36). I started upgrading Firefox. Everything worked fine until Firefox reached version 40. Then the same problem occurred. The logon box disappeared and I received the error above.

Any thoughts on how to fix this?

Thanks

Al


Thanks

Al

Logging into IIS (with integrated windows authentication and basic authentication) on a windows 2003 server used to work with all versions of Firefox. Clients updated to version 40 and Firefox no longer displays the windows authentication log in box. After updating to Firefox 40.0 , when they tried logging into the site they get this message : You are not authorized to view this page You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept. Please try the following: Contact the Web site administrator if you believe you should be able to view this directory or page. Click the Refresh button to try again with different credentials. HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration. Internet Information Services (IIS) Three others are having the same problem. They have been using Firefox for years and did not have any problems. Last Week Firefox upgraded to version 40 and now none of the Firefox users can log into the server. They all had to switch over to Internet Explorer or Opera. Is there a fix for this? I assume it has something to do with windows Server 2003 Kerberos Authentication. Has something been removed from Firefox 40.0 ? As I test I logged in using an earlier version of Firefox (something around version 36). I started upgrading Firefox. Everything worked fine until Firefox reached version 40. Then the same problem occurred. The logon box disappeared and I received the error above. Any thoughts on how to fix this? Thanks Al Thanks Al

Chosen solution

Thank you very much for your response.

The problem was with FireFox Version 40 and I was able to find a solution, that worked for me, located here, https://support.mozilla.org/en-US/questions/1079506 , in a response by jscher2000 on August 25, 2015 , but I will partially repeat the important points at this location also.


(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.


(2) In the search box above the list, type or paste auth and pause while the list is filtered


(3) Double-click the network.auth.allow-subresource-auth preference and edit the 1 to a 2 and click OK


Does that change anything with your OWA server? If not, you can restore that setting to its default value; it must be something else.

Read this answer in context 👍 0

All Replies (2)

more options

Hi Al, I do not know what version the affected users are updating from, however after version 30 there was a change that affected the less secure ntlm. To continue to use it, you can re-enable it in Firefox from the about:config page. In order to change your Firefox Configuration please do the following steps :

  1. In the Location bar, type about:config and press Enter. The about:config "This might void your warranty!" warning page may appear.
  2. Click I'll be careful, I promise! to continue to the about:config page.
  3. Double-click the network.negotiate-auth.allow-insecure-ntlm-v1 preference to switch it from false to true
more options

Chosen Solution

Thank you very much for your response.

The problem was with FireFox Version 40 and I was able to find a solution, that worked for me, located here, https://support.mozilla.org/en-US/questions/1079506 , in a response by jscher2000 on August 25, 2015 , but I will partially repeat the important points at this location also.


(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.


(2) In the search box above the list, type or paste auth and pause while the list is filtered


(3) Double-click the network.auth.allow-subresource-auth preference and edit the 1 to a 2 and click OK


Does that change anything with your OWA server? If not, you can restore that setting to its default value; it must be something else.