On theses folders, what hapens if you list it on the terminal ?
Just type "ls -laed@ " (don't forget the space)
and then drag the folder in the terminal windows.
In a general sense, you shouldn't use Finder to solve permissions problems as it's a simplified interface that don't allow you to corectly set things. Server.app or cli are more efficient.
Now, is theses shares working as expected ?
If I tell you to try it whith an other account, it's just to be sure it's not a finder plist problem.
So I think it should be interesting to create an other admin account, just to exclude this way.
If you have the same problem whith the other account, except if it's the Finder itself that is corrup (it's probably not the problem) you'll have to check on the folder itself and it's the parent folder. Check hfs tags (getfileinfo) and resources (xattr), and compare ACL whith working folders.
Check the owner too, is it accessible from the finder ? (for example if you change the owner of a file)
You're not meant to use the Finder at all to verify or (even less so) manage permissions in OS X Server.
Use the Server.app (prior to 10.8 & 10.7, Server Admin) or the Terminal. This has always (and forever) been the case.
Especially from a client machine that is not bound to OD (or a common directory eg AD that the server is also bound to), with a mounted sharepoint where one is seeing the result of permisssion(s) mapping.
Been working with OS X Server since it first existed, FWIW.
Yes, I understand the limitations of Finder, means should I ignore those irregularities?
The group was created using Workgroup Manager, so are the users.
The folder and permissioning was done thru Server app.
It's functioning properly unless Finder is a display issue.
Seriously, my great concern is that it has nothing to do with Open Directory, since Finder is able to display local users properly.