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.