DFS referrals

I have a namespace with 2 shares on 2 DCs in 2 different sites
\\HQDC01\share7 in HQSITE
\\BRANCHDC02\share7 in BRANCHSITE

All user shortcuts access the files in the shares by UNC paths to the domain share
EG: \\DOMAIN\share7

I understand if the user types in \\hqdc01\share7 from a workstation in the BRANCHSITE it will refer to \\branchdc02.

Is it possible to stop this referral?
I only want the referring to work if the user types the \\domain\share7 path. Not if they type the fqdn path.

Cheers
antoniokingAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SommerblinkCommented:
Deleted.
0
Daniel HelgenbergerCommented:
If you use the static UNC path to the server you will always end up on that server.
Since you do not use DFS paths, DFS will be completely circumvented if you use server direct paths.

At least I can verify this on our site with or AWS VPC. The lag has to come from Oregon ;)

And I know of no way to stop the normal UNC path since DFS works ontop of that.
0
antoniokingAuthor Commented:
Hi helge000
Thanks for the reply, this doesn't seem to be the case for my domain.
When typing the unc path of the HQDC01 from the BRANCHSITE site it displays the folder contents of BRANCHDC02
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Daniel HelgenbergerCommented:
I am quite sure this is not the normal behavior.
Can this be a DNS issue? Do 'nslookup's of these servers point to the correct one at both sites?
0
antoniokingAuthor Commented:
No errors in DNS, and NSLOOKUPS to each DC from each site works fine.
0
Daniel HelgenbergerCommented:
Hm, ok - did not read your question completely. Your file servers are both DCs!

Since they are DC's they will always act as DFS root, they also point to \\yourdomain.

I know of no way to change this behavior*, since they basically 'are' the DFS. You can also access all your DFS folders by putting in a domain controllers name instead of \\yourdomain. This way you make sure to access that particular root.

--
* Not true, this works of course with fileservers that are domain members. But you may be unable to change this.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
antoniokingAuthor Commented:
Ok, thanks Helge000.
Makes sense to me!
0
Daniel HelgenbergerCommented:
And I just want to add:
Your DFS implementation is of course NOT recommended because of this behavior among other things. It might be your whole DFS is not working correctly.

Change this by deploying file servers that are not domain contollers
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.