[SOLVED] Zentyal 3.5 "Location is not availible" - User H: drive

[shadowfire]

So far everything is back to normal - save the users network directory on H:\  Some users show it... but when you try to access it you get "Location is not availible" windows that says "H:\  is not accessable and Access denied".  But I have check permissions and I have check to make sure the Drive Letter say H:. - no dice.   Then I have another user that I deleted and recreated that has no H: user network directory.  I am at a loss. 

Any help is appreciated.

Thanks,

-SF-

[shadowfire]

So I think I might have figured it out.   It may have been fixed already but check this out.  I was looking in the home directory where it places all the users H: personal directories.

I did the following:

root@zjsrv:/home# ls -l

total 44
drwx------   2 ann    domain users 4096 Jul 22 13:17 ann
drwx------   2 betty  domain users 4096 Jul 16 15:04 betty
drwx------   2 carol  domain users 4096 Jul  2 18:36 carol
drwx------   2 karen  domain users 4096 Jul  2 19:00 eleana
drwx------   2 eleana domain users 4096 Jul  2 18:40 inez
drwx------   2   2505 domain users 4096 Jul  2 19:02 karen
drwx------   2 ann    domain users 4096 Jul  3 00:05 kathy
drwx------   2 kathy  domain users 4096 Jul  3 00:03 melissa
drwxrwx---+  4 root   domain users 4096 Jul  2 18:23 samba
drwxr-xr-x  17 super  super        4096 Jul 22 12:01 super
drwx------   2 inez   domain users 4096 Jul  3 00:07 volunteer
root@zjsrv:/home#

If you look closely you will find that some of the users and user groups don't match up.  I believe somehow the configuration samba Zentyal scripts for samba must have had a glitch in them that allowed a switch up on the user and groups.  Any who.  I went back manually to recreate the folder, user, group and permissions and it worked fine.  So now I am going back to the others that I have not changed and only changing the group to be the same as the name.  This should fix my issue manually.  So one may want to check samba configuration to make sure its not still a glitch.  I have a feeling it is no longer a problem.  Just wanted to offer up my observations and a manual fix.

Thanks,

-SF-