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$\user and we do that in the users' AD account.  I thought maybe we need to point it to \\mydomain.com instead of just "mydomain"…but that’s where I’m seeing some weirdness…

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.