If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
DFS Namespace issue with domain alias vs full domain name
The issue is that for some users, when they login, their H:\ drive is not mapping. It is supposed to map to \\mydomain\files\home$\use
When I test it from my computers, I’m seeing very strange results. From one of my DFS namespace servers, if I go to \\mydomain.com\files (FQDN namespace), I see all of the folders under the namespace just fine. If I go to the domain alias from the same server (\\mydomain\files), same result...I see all of the folders under the namespace just fine.
However, when I go to the FQDN namespace (\\mydomain.com\files) from my domain PC (which is a VM running on an ESXi host), I see all of the namespace folders EXCEPT for one, which is the Home$ folder. If I go to the alias namespace from the same computer (\\mydomain\files), I see all of the folders including Home$ just fine. What is the issue? What should we be using when accessing the DFS path...the fully qualified domain path or the alias or should it be seamless?
DFS is running on Server 2008 R2 servers.
When I test it from my computers, I’m seeing very strange results. From one of my DFS namespace servers, if I go to \\mydomain.com\files (FQDN namespace), I see all of the folders under the namespace just fine. If I go to the domain alias from the same server (\\mydomain\files), same result...I see all of the folders under the namespace just fine.
However, when I go to the FQDN namespace (\\mydomain.com\files) from my domain PC (which is a VM running on an ESXi host), I see all of the namespace folders EXCEPT for one, which is the Home$ folder. If I go to the alias namespace from the same computer (\\mydomain\files), I see all of the folders including Home$ just fine. What is the issue? What should we be using when accessing the DFS path...the fully qualified domain path or the alias or should it be seamless?
DFS is running on Server 2008 R2 servers.
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
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.
Thanks for the response. Here's what I'm seeing now. I have 6 namespace servers listed. On 3 of them, I can access the namespace share and all folders show up both when accessing via \\servername\files and \\servername.mydomain.com\
This is really strange. Any other ideas? I've ran a full replication on my domain but it will not complete because one of my DC's in a remote location (Holland, Netherlands) is down...this server really has nothing to do with DFS.
This is really strange. Any other ideas? I've ran a full replication on my domain but it will not complete because one of my DC's in a remote location (Holland, Netherlands) is down...this server really has nothing to do with DFS.
Well I think I have this fixed. Found an forum post here: http://arstechnica.com/civis/viewtopic.php?f=17&t=1186469.
This basically is saying that all your DC's need to namespace servers in the site where you are using domain DFS. I added all of my local DC's an viola...home$ folder is now showing everywhere.
Thanks for the help and suggestions.
This basically is saying that all your DC's need to namespace servers in the site where you are using domain DFS. I added all of my local DC's an viola...home$ folder is now showing everywhere.
Thanks for the help and suggestions.
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 trialIt'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
Windows Server 2008
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
You should be able to get same results when accessing dfs with \\domain\files OR \\domain.com\files
Please check if Home$ dfs folder is replicated to all name space servers under C:\DFSRoot folder
If home$ is not replicated to any name space server, then it will not show up when \\domain.com\files OR \\domain\files resolves to that particular server
In that case you need to delete home$ dfs folder and try recreating it and ensure that it is getting replicated to all name space servers