Hi Veronica,
I think your issue is probably related to authentication using NTLM instead of Kerberos. I suspect using a computer account to access a share is not support.
For client access, to ensure kerberos is used when using a CName you need to ensure the service principle name property for the computer object is set for the DNS CName alias
https://technet.microsoft.com/en-au/library/cc731241.aspx
For example say i had computer account "VSERVER1" and wanted clients to be able to access it as "VS1" using kerberos instead of NTLM then you need to set the SPN for "VS1" on the "VSERVER1" computer account object. EG:
List the SPN's
C:\>setspn -L VSERVER1
Registered ServicePrincipalNames for CN=VSERVER1,OU=NetApp,DC=testlab,DC=local:
HOST/VSERVER1
HOST/vserver1.testlab.local
Register SPN’s:
C:\>setspn -A HOST/vs1.testlab.local TESTLAB\VSERVER1
Registering ServicePrincipalNames for CN=VSERVER1,OU=NetApp,DC=testlab,DC=local
HOST/vs1.testlab.local
Updated object
C:\>setspn -A HOST/VS1 TESTLAB\VSERVER1
Registering ServicePrincipalNames for CN=VSERVER1,OU=NetApp,DC=testlab,DC=local
HOST/VS1
Updated object
Check the SPN's have been updated:
C:\>setspn -l VSERVER1
Registered ServicePrincipalNames for CN=VSERVER1,OU=NetApp,DC=testlab,DC=local:
HOST/VS1
HOST/vs1.testlab.local
HOST/vserver1.testlab.local
HOST/VSERVER1
Note the additional SPN's for the computer object have been added.
/matt
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.