Link to home
Start Free TrialLog in
Avatar of robclarke41
robclarke41

asked on

DFS share not working as Active Directory profile path

Hi All,

I have setup up DFS which replicates between 2 fileservers which works fine.

Practically everything is now redirected to the DFS network path now so that we have failover capabilities should we lose a server.

The only problem is that when I change the users profile path in Active Directory to reflect DFS it is completely ignored.  The users are logged on with temorary profiles - like the path cannot be seen.  Does anyone know why this would happen?

The path is \\adroot.AD.co.uk\AD_namespace\users\user1\profile which is basically a share called users that sits on Server A with a folder for each individual user inside it.

Thanks for any help.
Avatar of Adrian Cantrill
Adrian Cantrill
Flag of Australia image

Can you access the patch manually from one of the user workstations ? i.e login as the user, start -> run -> \\ad............ does it load ?
Avatar of robclarke41
robclarke41

ASKER

Yes I can - it works perfectly
and the user has the appropriate rights to the actual share on the server ? and the folder where there profile is pointing at is either empty, or has a valid profile in.

Does this effect all users or just 1 ?
The user does have the correct permissions to the share and their profile path.

It seems to be every user that its not working for.  If I enter a path directly to ther server i.e. \\ServerA\Users it works fine but not using the DFS path to the share.
when you change the profile path, is it pointing at a blank share, or is there a profile already in the DFS share location ? if so, try a blank share and let windows create the profile.
There is a profile in the directory already - which is picke up fine with a straight UNC path to the server but is ignored under DFS.
I'm just wondering if the DFS replication is 100% synced, and has it synced all the system files etc, are the clients being referred to the server you know to work 100% or the other server ?

Have you tried direct connections to both the servers in the replication arrangement.
As far as I can see replication is synced 100% and the prefferred server is the one hosting the profile.  This profile definitely works via a non-DFS UNC path so I don't think its that.  Is there any other reason why it shouldn't see this path.
> As far as I can see replication is synced 100% and the prefferred server is the one hosting the profile

but you have two servers which are targets for this DFS item... are you 100% sure that the clients aren't being referred to the second server ? and is this 100% working, and been tested directly ?
Yep 100% sure, they are definitely being referred to the primary server & this has all been tested.  If I map a drive to the path and right click then properties the primary server has a tick next to active server.
what event log entries do you have on the clients when they fail to read their profile over DFS?
I don't seem to get any profile related errors at all - it seems to be using the cached profile on the C: drive
ASKER CERTIFIED SOLUTION
Avatar of Adrian Cantrill
Adrian Cantrill
Flag of Australia 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