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.
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.
I think we have run into this problem before with OneFS 7.0.2.1 and I have a previous post for this. We are now able to see the shares via MMC by deleting some of the existing shares.
In the past there was an issue in which one solution was a manual clean involving gconfig database. The past post is here:
mkuhns1
19 Posts
2260
0
Posted May 2nd, 2016 11:00
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.