Hello everyone, At our company we created a portal.It was build partly and the proper url was added after a while. We then hadthe standard zone still using the machine name and we added the URL for the Intranet zoneusing the Alternate Access Mappings page. We have Integrated Authentication turned on and it works for the standard zone. So when a user types http://<machinename> the user gets to the portal without having to logon. However, when a user connects using http://portal.somedomain.comthat user has to give his credentials again. Does anybody know how to fix this so thata user does not have to logon using either url? Cheers, Vincent.

This is relevant to my interests as well.

Alrighty, I read your thread and used the ideas people wrote about and it worked, so thank you very much for letting me know:-) Now we are wondering though why the URL (which is an alias for the machine in our DNS) is not an intranetsite for IE. But this could already be good enough so I'm happy! Cheers, Vinz.

MrVince, I am experiencing the same problem. I see that you "used the ideas people wrote about and it worked" but I do not see what ideas you are talking about. Please let me know what ideas worked for you. I am ready to pull my hair out! Thank you, Austin

Hi Austin, The solution was in the thread started by Jacksie's question. The solution (or workaround might be more appropriate) was to add the URL to the list of sites in your intranet. You can do this by opening the security settings of Internet Explorer and then selecting: - Local Intranet - Sites - Advanced Here you add your URL. To my surprise even opening office documents now works without a password. I don't know if that's a silly side-effect but I like it! The downside of this is that every user needs to do this, maybe the setting can be forced by using a policy or something (ask your sys admin). Good luck, Vinz.

Ah, I have already done that, and I am still having the problem. We have tried adding the site to Intranet Sites, as well as Secure Sites, and niehter seems to completely eliminate the problem. Most users can browse MOST of the site without issue, but there are a few sites that prompt everyone for login. I cannot find any difference in the permission settings on these pages, and am at a loss! Thanks for responding, though! Austin

Austin- Do the pages that still require authentication have any web-parts on them that need to authenticate to another server in your organization? Line Exchange/OWA or CRM or something similar? This will cause your users to need to re-authenticate against the 'second-hop' resource if kerberos is not enabled and working properly in your domain.

Hello - After our migration, users get a prompt to log in when they access any of their sharepoint sites. We can prevent this by adding the site to the list of trusted sites in the intranet zone. Is there an easier way to achieve this? It's not feasible to walk all users through this step. thanks

Docman, Depending how your company network is set up, you may be able to add your SharePoint site as a network policy (e.g. push this to all of the users). Some of our users were still had to go through the manual set up, but this approached worked well for about 90% of our people. Best regards

You will need to add the URLs to the 'Local Intranet' zone for all users web browsers, either manually or via group policy. This is jsut how IE works, it will not automatically authenticate to any site with a FQDN or an IP address unless it is set in the Local Intranet zone.

thanks for the update

This is Great! For SharePoint 2007 it seems the solution was to just add the URL into trusted sites, but that doesn't work anymore unless you also put the URL into Local Intranet sites. I've noticed that some websites will prompt to have approve adding their application URL into the trusted sites. Is there a way to do that from a SharePoint site in order to add it to the local zone? I can also see why maybe that would be a bad idea