I have some more info about this issue.  Found that trying to use a "variable named share" is causing this problem.  The Isilon supports the ability to use a share named "%U" and when a user connects they connect to that share using their username.  So the share appears as \\isilon\Bob to user Bob and \\isilon\Joe to user Joe.  While that share exists on the Isilon MMC Shared Folders shows the Error 67.  As soon as the share "%U" is removed MMC Shared Folders no longer shows the error.  Opened a case with EMC on this issue.
All,  Recently we have tried to connect to our Isilon cluster using MMC Shared Folders and when clicking on the Shares in MMC the error "Error 67: The network name cannot be found" is shown.  Clicking on Sessions and Open Files does not give any errors and displays the open files and sessions just fine.  OneFS 8.0.0.0.  The user logged into the Windows 2012 server running MMC is in the Domain Admins group and the Domain Admins group is in the local administrators group on the Isilon.  I followed the steps from the video: Technical Demo: SMB Share Provisioning and Administration in EMC Isilon OneFS 7.1.1 | ID.TV - YouTube As mentioned above Open Files and Sessions is working.  Accessing the shares on the isilon works:  \\clustername\share and \\clustername in Windows Explorer Using "net view clustername" shows all the shares. "net use x: \\clustername\sharename" maps to a drive and is accessible as well.  Pinging short and FQDN clustername is cycling through the node IP addresses as round robin should.  Nslookup is doing the same.  Also tried connecting through MMC to the IP address.  Same behavior as the clustername.  Open Files and Sessions work but Shares give Error 67.  Any ideas why ONLY Shares in MMC is showing Error 67?
Isilon shares are not visible in MMC due to error