Link to home
Start Free TrialLog in
Avatar of PaulADavis
PaulADavisFlag for United States of America

asked on

Drive mapping issues with DFS

Currently having an issue where users are being mapped to locations other than specified in a login script.

We have a DFS namespace setup, however we've elected to map users to specific locations using a login script. So, instead of \\DFSNamespace\share we would map to \\servername\share. What we've noticed is that instead of being mapped to the location specified, some users will be mapped to the other referral server that has a copy of the shared folder... as if DFS was deciding which referral server was the best to use. I'm not sure what is causing this.

Why would a specific mapping statement be overidden be DFS and how can this be fixed?
We're using a mix of Windows 2008 server SP2 and Windows 2008 R2.
Avatar of Bradley Fox
Bradley Fox
Flag of United States of America image

What's the benefit of DFS if you are just going to map users directly to the shares anyway?  That kind of defeats the purpose.

When mapping a drive always use the FQDN of the server or domain namespace to ensure you are using DNS to resolve the name.  Make sure you are using the FQDN in your referrals too.

\\servername.domainname.local\Share
\\domainname.local\DFSShare
Avatar of PaulADavis

ASKER

as a solution we removed that specific namespace... issue resolved.

Was hoping to find out why DFS would override a specific mapping and use referrals instead.
ASKER CERTIFIED SOLUTION
Avatar of compdigit44
compdigit44

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
thanks compdigit44... one of those reasons in the article is probably at play...