Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

when connecting to website using sso, packet sniffing shows ntlm user is using {server name}\{user name} instead of {domain name}\{user name}

more options

I moved to windows 7 and firefox 12 and my internal website via the servername (not FQN) is now prompting me for the username and password in firefox. I do not get prompted for a username and password when using IE9 to access the site via servername (not FQN).

packet sniffing shows IE9 is using my windows domain as the windows domain. packet sniffing shows Firefox is using the web servers servername as the domain.

If I use the fully qualified server name then firefox authenticates successfully. this is not a problem on my winxp workstation with firefox 12.

I moved to windows 7 and firefox 12 and my internal website via the servername (not FQN) is now prompting me for the username and password in firefox. I do not get prompted for a username and password when using IE9 to access the site via servername (not FQN). packet sniffing shows IE9 is using my windows domain as the windows domain. packet sniffing shows Firefox is using the web servers servername as the domain. If I use the fully qualified server name then firefox authenticates successfully. this is not a problem on my winxp workstation with firefox 12.

由 punkdali 於 修改

所有回覆 (3)

more options

I'm not seeing a difference between Firefox 12 and earlier versions in my environment.

Are you logged in to the domain when this happens?

Are any proxy servers involved?

more options

The only time it fails is in windows 7 and the address used of HTTP://servername. I updated the above post to show it works in XP with ff12. There is no proxy server involved. I am logged into the domain. If I use the fully qualified servername as the address it works. Http://servername.domain.local

more options

On my Windows 7 machine, I have full administrator privileges. I wonder whether that is a factor? We are still using the short names, not FQDNs.

Unfortunately, I don't think I know enough about Windows authentication to troubleshoot this further.