Greetings! This is probably basic stuff. However, I had no OnTap training and no experience with DFS systems...
We have two main offices. The NetApp FAS cabinets are in the New York office, and many of us needing access are in the mid-west office (central Illinois, USA).
Our network is Microsoft Windows 2003 (Native) Active Directory. I am not sure as to the OnTap version, but I believe it is 7.3. Client machines are mostly Windows XP SP3, Professional. However, we see the same problem from other Windows 2003 servers...
When we in Illinois attempt to connect to the departmental drive through its DFS address, we receive the following:
\\aspca.local\nyc\Info Technology is not accessible. You might not have permission to use this network resource.
Contact the administrator of this server to find out if you have access permissions.
The network path was not found.
We get this response regardless of whether we try to access with least privileged user credentials or with domain administrator credentials.
If we simply enter the address "\\aspca.local\nyc", we see numerous folders (including Info Technology). With two exceptions, we receive the same message if we click on the folders.
If instead of entering the DFS address and instead enter the fully qualified domain name (FQDN) of the NetApp filer and the folder name, we gain access to the folder with the appropriate read/write/modify rights.
Being curious, I went back to the DFS address (in Windows Explorer, \\aspca.local\nyc) and began right-clicking on folders to check "Properties". I saw a tab "DFS". For the two folders to which we do have access, the DFS tab said "Active: Yes". For our departmental folder, the DFS tab said "Active: No".
In that tab was a button to set DFS to "Active: Yes". I told this to the administrator in New York. I was told the following (probably as a learning experience?):
I was told that the department members in the New York office did not see the same errors we were seeing. I was also told there was the possibility of the system access "breaking" for the New York department members should I click this button. Finally, I was told to come to this forum and ask...
1. Is the lack of access to a folder via the DFS address by people at the remote location due to the DFS Active setting set to "No"?
2. What else could be causing the lack of access via this address? (Again, access via FQDN name is successful.)
3. What may or may not happen should I or someone else click the "Set to active" button in the "Properties - DFS" tab?