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.
ASKER
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.
U have missing only home$ folder, right?
are you able to locate rest of the folders?
are you able to locate rest of the folders?
ASKER
@Mahesh
Yes that's correct...all other folders are showing up.
Yes that's correct...all other folders are showing up.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I found the fix for this on my own.
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