[mdlug] Samba/Server2003 Active Directory integration problems after time update

[greenproc]

After updating a suse box running LDAP with the new timezone data, there appears to be a problem where clients on the network that try to access SMB shares on the linux box are denied access when the method is \\servername\sharename (as in access denied for unknown user)

When the access method is \\ip.x.y.z\sharename access is granted, no problems.

There is a two second clock skew between the Suse SMB/LDAP box and the Win2003 AD server -- is this enough of a clock skew to throw timestamps off enough to make auth go whacky?  

Or does it make sense that the problem lies elsewhere?