Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Mozilla サポートの検索

サポート詐欺に注意してください。 私たちはあなたに通話やショートメッセージの送信、個人情報の共有を求めることはありません。疑わしい行為を見つけたら「迷惑行為を報告」からご報告ください。

詳しく学ぶ
このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。
アーカイブに保管済み

NTLM authentication information - there is never any prompt or place to enter credentials

Android 版 Firefox プライバシーとセキュリティ
guigs replied 12 年前
SMSC
SMSC

We are testing using Android tablets in our current IT infrastructure and we're running into a few snags. We can join the network, we have the proxy set in the Wi-Fi settings, and we are able to navigate to internal resources by their IP address, however we cannot navigate through the proxy (Smoothwall) using NTLM authentication.

Trying to navigate via the stock browser lands us on our proxies default NTLM Authentication Failed page (as to be expected, as there is no support for NTLM on the stock browser) however via Firefox I simply get the stock 'Unable to Connect' page.

I have tried multiple options in the about:config page (network.automatic-ntml-auth.allow-non-fqdn, network.automatic-ntml-auth.allow-proxies, network.automatic-ntml-auth.trusted-uris, network.ntlm.send-Im-response, network.negotiate-auth.delegation-uris) but have had no success.

There seems to be nowhere in Firefox's settings to input proxy authentication credentials, and there is never any prompt to do so when trying to browse the internet. I have deleted the cache (and all other settings) to ensure I am not returning a cached copy and still it does not work. What settings do I need to set in order to navigate through the proxy with NTLM authentication?

Samsung Galaxy Tab (GT-P1000), Android 2.3.3 (Gingerbread), Firefox 25.0.1

We are testing using Android tablets in our current IT infrastructure and we're running into a few snags. We can join the network, we have the proxy set in the Wi-Fi settings, and we are able to navigate to internal resources by their IP address, however we cannot navigate through the proxy (Smoothwall) using NTLM authentication. Trying to navigate via the stock browser lands us on our proxies default NTLM Authentication Failed page (as to be expected, as there is no support for NTLM on the stock browser) however via Firefox I simply get the stock 'Unable to Connect' page. I have tried multiple options in the about:config page (network.automatic-ntml-auth.allow-non-fqdn, network.automatic-ntml-auth.allow-proxies, network.automatic-ntml-auth.trusted-uris, network.ntlm.send-Im-response, network.negotiate-auth.delegation-uris) but have had no success. There seems to be nowhere in Firefox's settings to input proxy authentication credentials, and there is never any prompt to do so when trying to browse the internet. I have deleted the cache (and all other settings) to ensure I am not returning a cached copy and still it does not work. What settings do I need to set in order to navigate through the proxy with NTLM authentication? Samsung Galaxy Tab (GT-P1000), Android 2.3.3 (Gingerbread), Firefox 25.0.1

すべての返信 (5)

philipp
philipp
  • モデレーター

does it make a difference when you set the proxy again in firefox?

https://support.mozilla.org/en-US/questions/954078#answer-419305

guigs
guigs

Hi, In Firefox Beta version 26, at the moment there is:

network.proxy.no_proxies_on

that requires a string for a dns or ip address.


Or other solutions:

If you try beta, let us know if that works, I do not have an environment to test this.

SMSC
SMSC 質問者

phillipp, I have set network.proxy.http, network.proxy.http_port, network.proxy.ssl and network.proxy.ssl_port (both to the ip address and port of the proxy server as all of our traffic heading to the outside web has to navigate through the proxy, no matter its destination. Unfortunately this still hasn't worked.

I also have both the proxy ip address and the domain set in network.automatic-ntlm-auth.trusted-uris. Any idea what I'm doing wrong?

この投稿は SMSC により に変更されました

guigs
guigs

Does Smoothwall have a rule blocking traffic from Firefox? It may be a good idea to run the issue by them as well if you have tried all the firefox options and other browsers work.

この投稿は guigs により に変更されました

guigs
guigs

I also found this: 

// (bug 535193) For NTLM, just use the uri host, do not do canonical host lookups.
       // The incoming serviceName is in the format: "protocol@hostname", SSPI expects
       // "<service class>/<hostname>", so swap the '@' for a '/'.

ref: http://dxr.mozilla.org/mozilla-centra.../nsAuthSSPI.cpp