locked
Connect to site SharePoint from computer in externe AD RRS feed

  • Question

  • Hi, 

     

    i have a Site SharePoint 'sitedev' connected to my AD domain.dev.

    I want to connect to that site from a computer in another domain : domain.entreprise, when i write in the navigator http://sitedev.domain.dev the site can't be opened (no acces) but when i write : http://ip-adresse-server in my navigator the first page open, but when i connect to another page in my site it display the authentication popup but with a good user account (have access to site) can't authenticate and i can't acces to the site.

     

    how can i do to connect to this site from a computer in another AD ??

     

    NB: I use SharePoint 2007

     

     

    Thx

     

    Thursday, November 17, 2011 5:41 PM

Answers

  • You will need to look at the URL that you are using, I presume that normally users access the site as just http://sitedev ? In that case SharePoint doesn't recognise the URL http://sitedev.domain.dev so it doesn't know how to respond. To resolve this you can either have all users use the http://sitedev URL or you can add an Alternate Access Mapping (AAM) for http://sitedev.domain.dev so that SharePoint can recognise it and respond correctly.

    You can read more about AAM at http://technet.microsoft.com/en-us/library/cc263208(office.12).aspx

    In your case it should be quite simple, on the SharePoint server go to IIS administration, find the website hosting your SharePoint site and edit it's bindings. Add a binding for the new URL (on port 80). The in SharePoint Central Administration, go to Alternate Access Mappings on the Operations page. Edit public URLs, choose your site collection and then enter the new URL in one of the text fields ("Intranet" might make most sense, but it doesn't really matter which you use unless you extend your web application and want different authentication types for different zones).


    Edit: doing this much will let you browse to the site use the full URL, you may still need to resolve the domain trust issues etc mentioned in the above posts.
    Monday, November 21, 2011 2:28 PM

All replies

  • This is a domain trust issue. Connecting that Farm to another as it is, would be a bad idea. Work on your trusts and it'll be an easier option.
    Saturday, November 19, 2011 5:07 PM
  • As far as I understand you have DNS issues. sitedev.domain.dev needs to point to your server IP.

    When using a browser you are making an HTTP request. The computer running the browser doesn't need to be in any domain, you just need to authenticate with the credentials set on sitedev.

    Hope this helps.


    Independant SharePoint Consultant. Feel free to contact me. Blog: http://www.sharepoint.bg/radi Twitter: @RadiAtanassov
    Saturday, November 19, 2011 6:47 PM
  • You will need to look at the URL that you are using, I presume that normally users access the site as just http://sitedev ? In that case SharePoint doesn't recognise the URL http://sitedev.domain.dev so it doesn't know how to respond. To resolve this you can either have all users use the http://sitedev URL or you can add an Alternate Access Mapping (AAM) for http://sitedev.domain.dev so that SharePoint can recognise it and respond correctly.

    You can read more about AAM at http://technet.microsoft.com/en-us/library/cc263208(office.12).aspx

    In your case it should be quite simple, on the SharePoint server go to IIS administration, find the website hosting your SharePoint site and edit it's bindings. Add a binding for the new URL (on port 80). The in SharePoint Central Administration, go to Alternate Access Mappings on the Operations page. Edit public URLs, choose your site collection and then enter the new URL in one of the text fields ("Intranet" might make most sense, but it doesn't really matter which you use unless you extend your web application and want different authentication types for different zones).


    Edit: doing this much will let you browse to the site use the full URL, you may still need to resolve the domain trust issues etc mentioned in the above posts.
    Monday, November 21, 2011 2:28 PM