This could be to do with Domain authentication. I would double check the settings in your DNS and NTP. Also check that you can ping your DNS server from the interfaces that you are trying to configure the shared folder on.
I was also seeing this error when attempting to apply changes after ticking windows shares (CIFS) from the shared folder server details tab:
The changes could not be applied, the following error was encountered:
The system failed to add a CIFS shared folder server. Record the error code and go to the Product Support Page for all your support options. (Error Code:0x60008ad)
I looked in my logs and there was an error referring to the NETBIOS name length. The NETBIOS name must be 15 bytes or less. There was also a warning that UTF characters can use more than 1 byte (e.g. you might only have 15 characters on the screen, but that could be more than 15 bytes long).
Basically - Create a new folder server with a short and simple name and try again. If it is still not working, check under the System Logs for an errors which will help troubleshoot (Click on System then Logs). If you post a copy of the error message from the log here somebody else might be able to help.
This is our first experience with SAN products at our location, so forgive my complete noobness.
We just got our first pair of 3100 units racked up and the CIFS server creation was giving me fits at first.
I was also getting Error Code 0x60008ad as mentioned by Ben.
Two things we discovered along the way:
- I had mistakenly asked our Network Admin to setup LAG for port aggregation on our core switches (Foundry), which had the effect of causing the VNXe to go bonkers once I created a second CIFS server on the same unit, with lockups, no way to ping anything, and general frustration. Once LAG was removed on the switch, everything smoothed out. Once we thought it through a little, we realized that we were basically presenting the switch LAG group with multiple MACs by having more than one CIFS on the same SP, and that was a "duh" kind of moment.
- A little more tricky of a thing was with the domain join in CIFS. We are not domain admins (only having admin rights over our own OU), and we discovered that we HAVE to include our OU structure where we wanted the server to land (ou=blah:ou=blah) or else the join from the VNXe fails to create the server. The dialogue box for specifying OU seems to be optional, so I believe this has something specific to do with our domain policies that I don't have control over. We do not have to specify an exact OU when we join a PC or Windows server to our domain (they end up in the root Computers OU and then we can move them later to our own OU), so it took awhile to figure that bit out.
In the end my issue was related to MAC address issues and HP adapter teaming on my AD servers. EMC support made some adjustments to the VNXE3100 and after that it started working.
LRP1
2 Posts
0
December 5th, 2011 02:00
I finally solved this problem.
The issue was in the configuration process.
In the Organization Unit i was writing the LDAP URL using the "," and not the ":" such as the example shows:
***ou=Computers***:***ou=EMC Celerra***
My mistake... or EMC new LDAP settings...
Johnny_Bravo
63 Posts
0
November 4th, 2011 01:00
Hi LRP,
This could be to do with Domain authentication. I would double check the settings in your DNS and NTP. Also check that you can ping your DNS server from the interfaces that you are trying to configure the shared folder on.
JB
BenRuefli
2 Posts
1
November 30th, 2011 22:00
I was also seeing this error when attempting to apply changes after ticking windows shares (CIFS) from the shared folder server details tab:
The changes could not be applied, the following error was encountered:
The system failed to add a CIFS shared folder server. Record the error code and go to the Product Support Page for all your support options. (Error Code:0x60008ad)
I looked in my logs and there was an error referring to the NETBIOS name length. The NETBIOS name must be 15 bytes or less. There was also a warning that UTF characters can use more than 1 byte (e.g. you might only have 15 characters on the screen, but that could be more than 15 bytes long).
Basically - Create a new folder server with a short and simple name and try again. If it is still not working, check under the System Logs for an errors which will help troubleshoot (Click on System then Logs). If you post a copy of the error message from the log here somebody else might be able to help.
DaveFoley
6 Posts
1
December 2nd, 2011 08:00
This is our first experience with SAN products at our location, so forgive my complete noobness.
We just got our first pair of 3100 units racked up and the CIFS server creation was giving me fits at first.
I was also getting Error Code 0x60008ad as mentioned by Ben.
Two things we discovered along the way:
- I had mistakenly asked our Network Admin to setup LAG for port aggregation on our core switches (Foundry), which had the effect of causing the VNXe to go bonkers once I created a second CIFS server on the same unit, with lockups, no way to ping anything, and general frustration. Once LAG was removed on the switch, everything smoothed out. Once we thought it through a little, we realized that we were basically presenting the switch LAG group with multiple MACs by having more than one CIFS on the same SP, and that was a "duh" kind of moment.
- A little more tricky of a thing was with the domain join in CIFS. We are not domain admins (only having admin rights over our own OU), and we discovered that we HAVE to include our OU structure where we wanted the server to land (ou=blah:ou=blah) or else the join from the VNXe fails to create the server. The dialogue box for specifying OU seems to be optional, so I believe this has something specific to do with our domain policies that I don't have control over. We do not have to specify an exact OU when we join a PC or Windows server to our domain (they end up in the root Computers OU and then we can move them later to our own OU), so it took awhile to figure that bit out.
Hope those things can help someone.
BenRuefli
2 Posts
0
December 4th, 2011 13:00
In the end my issue was related to MAC address issues and HP adapter teaming on my AD servers. EMC support made some adjustments to the VNXE3100 and after that it started working.