10.7.4 has killed my SMB Shares

Question

I updated a server to 10.7.4 this weekend based on the release notes:
- Address an issue that may prevent files from being saved to an SMB server.
Instead, now my Windows users can't connect at all.
I've manually restarted the SMB service
- sudo launchctl unload -F /System/Library/LaunchDaemons/com.apple.smbd.plist
- sudo launchctl load -F /System/Library/LaunchDaemons/com.apple.smbd.plist
I've removed all my shares and recreated them.
I've restarted the server.
I've gone to Storage in Server.app and propagated the permissions on folders.
So far, none of the previous fixes I've used in the past have worked.
Additionally, my local Administrator can see all the shares, but my Open Directory Users cannot.
Anyone else have this problem or fix it yet?

Answer 1

Solution confirmed once again.  Stopped the SMB service, removed SMB from individual shares, started SMB service, then added the option back to the individual shares.  I was testing primarily from a Windows 7 client where the local Windows login does not match the Open Directory login being used to access the SMB share on my Lion server. 
Once I knew I had some working SMB shares, I tested some different username formats, since I originally suspected that I was using the wrong format:
These formats did not work:
OD_DOMAIN\ODUsername
OD_HOSTNAME\ODUsername
ODUsername@OD_DOMAIN
ODUsername@OD_IPADDRESS
ODUsername@OD_HOSTNAME
The only formats that worked for me were:
OD_IPADDRESS\ODUsername
ODUsername 
I find it strange that plain old ODUsername works, as this should pass the local machine name by default, thus my input would be changed to LOCALHOSTNAME\ODUsername.  My Windows hostname does not match up with OD, so this shouldn't technically work...
As a control in my testing, I did not change the SMB sharing option from some of my shares, then tested these after the smb restart.  Directories where I toggled the status off and back on again were working, while these "control" directories produce the following error when access is attempted (I tested from a Win7 machine).  This error is produced before the authentication dialogue is presented:
\\IPADDRESS\Share
A device attached to the system is not functioning.
However, I when I applied this fix to all directories, this error is gone.  I just found it strange that it was not revealed until I restarted the SMB service.
I'll have to test further to find out whether this issue is resolved permanently, or if it will come back at some point.