Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 13565

DFS Namespace losing link

$
0
0

Hi Gang,

  I have an environment with a domain-based Namespace on two 2008 R2 servers.  The users are all on Apple computers running OS 10.8.5 or (only two) on 10.9.

  Within the Namespace, I have 7 shared folders that are all on the same server and drive.  Several of the users have noted that one of the shares disappear from the folder list in their "Finder" and I have confirmed the fact.

So, the Namespace is \\ourcorp.com\admin, and in there are links to IMAGES, ADMIN, USERS, COUNTER, OBJECTS, UNIVERSE and COMMERCIAL

The users will often notice that the link to IMAGES has disappeared, and they will re-connect to the Namespace, re-establishing IMAGES in their list.

 All of these shares except IMAGES are folders within the same existing share on this server; i.e.  \\server\oldshare\COMMERCIAL or \\server\oldshare\OBJECTS

The IMAGES folder is itself, an existing share (by that I mean it was a share before I built the DFS Namespace); i.e. \\server\Images.  That is the only difference I can see from the other shares, which were created by adding  a new Folder Target and browsing to the folder within \\server\oldshare.

Some users also complain that they get 'disconnected' from the Namespace (they call it a 'server' because of how it's displayed in the Apple Finder).  A problem arises when they open the Finder/Server Connections and click Connect on the Namespace a second time; i.e. smb://ourcorp.com/admin - they then have a mounted drive called admin-1 which has IMAGES in it and a mounted drive called admin which doesn't.

 Might seem trivial, but a common operation they use is to right-click copy a link to the file for email to a coworker. So the recipient gets a link to a file which looks like //volumes/admin-1/objects/small/ones/anobject.png, when it should be //volumes/admin/objects/small/ones/anobject.png

When the recipient clicks on the link it's hit-or-miss whether or not they get an error.  If they have re-connected to the Namespace as the sender did, all is okay - because they have a mounted drive called admin-1. If they haven't, then they can't open the link and assume there's a problem with the system and open a service desk ticket.

Would someone here have an idea of where to look for the cause?

Your suggestions are appreciated!

- a -


Viewing all articles
Browse latest Browse all 13565

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>