Here is an interesting feature...
So, I got my system back up last night on the old version (Thanks again for the link), so I have some time to troubleshoot 3.0...
I installed another VM with 3.0 and, again, after creating users, groups, and shares, none of my groups can access the shares, however, the users can.
So, if I set up userA and put him into groupA and assign groupA read/write or domain admin on a share, userA will continually get prompted for a password. The logs say NT_AUTHENTICATION_ERROR or something along those lines...
However, if I set the users name, userA as read/write to the share, then they can access the share just fine.
So, it appears that the groups are not working in SAMBA.
I say this, because I can ssh into the machine as userA and all the filesystem ACLs that are in place for groups work for this user.
So, something is amiss with Samba. Perhaps an bad update?
Last week, I set up a working 3.0 box, and, by the grace of God, create a config backup.
You know what??? When I restored the previous config backup to the broken 3.0 install... it all started working as it should.
So, I am going to rebuild, set it up like I normally would, get a config backup of the broken setup, then, restore and compare last weeks config backup to the new one to see what changes.
Then, I will file bug reports on what I find.
I'm highly surprised more people have not chimed in on this over the week... I installed the system like 6 times last 2 days and every time it was broke, so it could not have been something I was doing wrong - I say this because I have a build doc that I use from the first time I was testing out 3.0 and that install worked fine!
Anyway, back to testing!
Joe