Link to home
Start Free TrialLog in
Avatar of Dgreenbaum
Dgreenbaum

asked on

Sharepoint 2007 in a newly merged organization

We have just merged with another company. We have a Two-Way Forest trust established successfully between us, Domain A and them, Domain B. We are trying to give users in Domain B access to Sharepoint.  

The issue is that users from Domain B are being challenged for a username and password when connecting to a site on Sharepoint at Domain A.     Once they login, there are little anomalies  that have to do with permission (see description below).   We, Domain A, are a Windows 2003 domain with Sharepoint 2007 running.  Domain B, is a Windows 2008R2 domain running at Windows 2003 functional level.

 In Sharepoint we have gone into Shared Services Administration> User Profiles and Properties>View Import Connections and created a new connection to Domain B's Active Directory.  The Domain B's users now appear in View User Profiles.

Besides being challenged for the un/pw, when they get to the site, the little attachement paperclip icon does not appear, replaced with a generic red X as if the folder permissions in IIS are not correct (the clip is in _images folder).

Any advice on what we have done wrong or left out would be appreciated.  Talk slowly, we aren't Sharepoint people.
Avatar of Rainer Jeschor
Rainer Jeschor
Flag of Germany image

Hi,
for the username/password prompt. Can you verify if the SharePoint url is added to the "Local Intranet Zone" of the users of domain B?
You could verify this by letting a user of domain B just open the SharePoint site. IE should show in the bottom status bar its zone (for IE>=8 - for IE>8 its under menu "File" -> "Properties").
By default IE sends the current credentials only to sites listed in the local intranet zone - not in the Trusted sites zone. But please remember - depending on the IT configurations it might be that they are using Group Policies to push IE configurations and can even block changes on the client side.

For the image issue - you should never directly change anything in IIS manager because this can cause issues afterwards as SharePoints internal config could now be out of sync.

The question is, why does it show the red X: due to a 404 not found or due to a 401 permission denied. To track that you might use either a proxy tool like Fiddler or use IE built-in dev tools (shortcut is F12). You will find a tab "Network", then "Start capturing" and now open the page. Images are normally stored under "_layouts/images" (but thats my local SP2010 - I would have to verify this afternoon when I have access to a running MOSS 2007 instance).

HTH
Rainer
Avatar of Dgreenbaum
Dgreenbaum

ASKER

Hi Rainier... I wil pursue your suggestions and report back.   Thanks so much.

David
Hi.

I'm excited to say adding the site to the Intranet worked!

regarding the apparent broken link, on the iIE Dev tools page I found no Network tab.  We are still on IE8.  Is that only available in later versions?
I neglected to say that our domains are connected through a point to point IpSec tunnel.
ASKER CERTIFIED SOLUTION
Avatar of Rainer Jeschor
Rainer Jeschor
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi Rainier.  I got it to work!   Your suggestion to copy the url was exactly the clue I needed.

When I saw it I knew the problem.   In our two way forest trust we have not yet created a forward lookup zone in dns in each other's domains.  The Sharepoint site was being accessed from Domain B with the FQDN:  http://sharepointserver.domainA.local/website/default.aspx.  

That worked for the Sharepoint site but the .gif in question, once they got to the site, was just  http://sharepointserver/website/_layouts/images/attach.gif; no FQDN.

I created a A record in DNS on Domain B to point to Sharepointserver.   The little attachment paper clip .gif could then be found with just the Sharepointserver name.

Thanks for the guidance,
David
Once Rainier heard the whole story he knew just where to look for the answer.  With his help it was clear as a bell.