Aswinkumar,  More often than not, this is an issue when the user trying to connect in the manner you are attempting to is not a Domain Administrator.  By default, they are the only group when the CIFS server is joined to the domain that is added to the local/BuiltIn Administrators group.  When you followed the steps in the KB article, specifically the modifying the option:  server_param server_x -f cifs -modify djAddAdminToLg -value 1  this is a way to auto-assign more than just the Domain Administrators to the local Administrators group.  For instance, sometimes the user have been granted the permissions to add objects to AD; however, they aren't Domain Administrators.  *Upon join*, the account used to join the CIFS server to the domain will also be added. This then lets you manage via the MMC plugins.  So just to be clear, and I will agree that the KB article doesn't necessarily clearly state this for an existing environment, the parameter djAddAdminToLg only applies to future joins.  So for an existing CIFS server this would mean unjoining and rejoining the CIFS server which of course means downtime.  Simply enabling the option won't do resolve it.   Therefore, if your account isn't a Domain Administrator, then you have the following options:  1) With the parameter enabled on the data mover, unjoin and rejoin the CIFS server to the domain; of course this means downtime  or...  2) Have a Domain Administrator connect to the CIFS server via compmgmt.msc a) Right-click on "Computer Management (Local)" and select: "Connect to another computer..."  b) System Tools > Local Users and Groups > Groups  c) Open up Administrators, then add your domain account   Then you will be able to do the same from that point on.  Does this account for it?
Ho  to resolv bellow error   How to to enable Windows event log archive?  Celerra:NS-120/480 Nascode :6.x
The Windows event log Security of the vdm vdm0 is full.