2. Ensure \u201cAutomatically detect intranet network\u201d is checked and click\u00a0Advanced<\/strong><\/p>\n 3. Add your SharePoint server\u2019s fully qualified domain name. In my case, I chose to use an asterisk as a wildcard (*.companyname.com) to represents all hosts in my local intranet.<\/p>\n WARNING: Be very careful when using a wildcard on this setting to ensure your credentials are only used to connect to trusted servers on your \u201cinternal\u201d network and not on the Internet. As an example, you would never want to use *companyname.com which can be easily spoofed and lead to passing internal domain credentials to a non-trusted external system.<\/em><\/p>\n 4. In addition, when back on the Security tab, Click\u00a0Custom Level<\/strong> and scroll down to the bottom of the Local Intranet Zone settings and ensure \u201cAutomatic logon only in Intranet zone\u201d is checked.<\/p>\n 5. Close and re-open your browser. You should no longer be prompted when accessing your local domain\u2019s SharePoint server.<\/p>\n Well, that took care of issue number one but I was still getting prompted when opening an Office 2007 document from a SharePoint Document Repository. However, once the credentials are entered, the prompt goes away\u2026 for a while. Actually, I believe the credentials are simply not cached between logons and return when I access the document repository following logons or reboots. Anyway, this turned out to be due to the fact Microsoft changed the way online documents are accessed via Web Distributed Authoring and Versioning (WebDav). According to\u00a0KB 943280<\/a>, a windows Vista Client will be prompted for a username and password under the following conditions:<\/p>\n Well, I can tell you that I did not have a proxy server configured and my SharePoint document repository was certainly a WebDav site accessed via FQDN<\/p>\n Although the KB article is meant for Vista, Windows 7 is essentially Vista version 2 so I figured it would hold the key. However, the hotfix listed in the article would not be applicable as it was included way back with Vista SP1 anyway and Windows 7 was bound to include that functionality.<\/p>\n Anyway, the fix for this is as follows:<\/p>\n 1. Open Registry Editor to: HKLMSYSTEMCurrentControlSetServicesWebClientParameters<\/p>\n 2. Add a new key using Multi-String Value<\/p>\n 3. Enter AuthForwardServerList\u00a0 for the new key name<\/p>\n 4. Edit the new key and enter the FQDN of the SharePoint or WebDav Server.<\/p>\n (In my case, I used *.companyname.com again. )<\/p>\n 5. Close Registry editor, go to services in Computer Management and restart the WebClient service.<\/p>\n Alternatively, you can simply open a command prompt with elevated permissions and enter the following line (edited with your server info of course):<\/p>\n reg add HKLMSYSTEMCurrentControlSetServicesWebClientParameters \/v AuthForwardServerList \/t REG_MULTI_SZ \/d *.companyname.com<\/em><\/p>\n You can restart WebClient in the same command prompt, type: Net Stop WebClient && Net Start WebClient<\/p>\n That\u2019s it, seamless passthrough authentication to SharePoint!<\/p>\n![\"image\"](\"http:\/\/www.quantumofgeek.com\/blog\/wp-content\/uploads\/2010\/02\/image5.png\" "\\"image\\"")
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n\n