Hi guys/girls, How are you keeping ? A while ago I mentioned a problem that I'm picking up with Samba with OpenLDAP and the "logon hours" restrictions which are implemented via the NT 4.0 User Manager. Basically my problem was that users were unable to login 2 hours before the actual restriction should kick in. At the time I thought that perhaps the problem was caused by Slackware Linux and it's timezone implementation of SAST (GMT+2). Since then I've experienced the same problem on SLES9 and Suse Linux 9.3.>From what I can see, the "sambaLogonHours" value is always set with GMT inmind. Because in South Africa we are at GMT+2 Samba enforces restrictions 2 hours before it should. For example if users should only denied login access at 16:00, Samba is denying them access at 14:00. I've looked all over and cannot find a solution to the problem other than adding two hours to the logon hours restrictions for each user when using the NT User Manager tool. Does anyone know of a workaround for this ? Is there a way to get Samba to check the time zone on the server first and make calculations before writing values for the "sambaLogonHours" attribute ? Links/references: Explanation of feature: archive-two.com/new-2794385-2895.html lists.samba.org/archive/samba-technical/2004-December/038271.html archives.free.net.ph/message/20051006.181854.4d7c50dc.en.html archives.free.net.ph/message/20050701.071531.eeffd7e5.en.html lists.samba.org/archive/samba/2005-February/099778.html Thanks in advance. Kind regards David Wilson CNS, CLS, Linux+ 033 3427003 082 4147413 0860-1-LINUX
Hi guys, Any takers ? Kind regards David Wilson CNS, CLS, Linux+ 033 3427003 082 4147413 0860-1-LINUX support@dcdata.co.za ----- Original Message ----- From: "David Wilson" <dave@dcdata.co.za> To: <samba@lists.samba.org> Sent: Saturday, October 15, 2005 2:16 PM Subject: sambaLogonHours and timezones> Hi guys/girls, > > How are you keeping ? > > A while ago I mentioned a problem that I'm picking up with Samba with > OpenLDAP and the "logon hours" restrictions which are implemented via the > NT 4.0 User Manager. > > Basically my problem was that users were unable to login 2 hours before > the actual restriction should kick in. > At the time I thought that perhaps the problem was caused by Slackware > Linux and it's timezone implementation of SAST (GMT+2). > Since then I've experienced the same problem on SLES9 and Suse Linux 9.3. > > From what I can see, the "sambaLogonHours" value is always set with GMT in > mind. > Because in South Africa we are at GMT+2 Samba enforces restrictions 2 > hours before it should. > For example if users should only denied login access at 16:00, Samba is > denying them access at 14:00. > > I've looked all over and cannot find a solution to the problem other than > adding two hours to the logon hours restrictions for each user when using > the NT User Manager tool. > > Does anyone know of a workaround for this ? Is there a way to get Samba to > check the time zone on the server first and make calculations before > writing values for the "sambaLogonHours" attribute ? > > Links/references: > Explanation of feature: archive-two.com/new-2794385-2895.html > lists.samba.org/archive/samba-technical/2004-December/038271.html > archives.free.net.ph/message/20051006.181854.4d7c50dc.en.html > archives.free.net.ph/message/20050701.071531.eeffd7e5.en.html > lists.samba.org/archive/samba/2005-February/099778.html > > Thanks in advance. > > Kind regards > > David Wilson > CNS, CLS, Linux+ > 033 3427003 > 082 4147413 > 0860-1-LINUX >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Wilson wrote: | Hi guys/girls, | | How are you keeping ? | | A while ago I mentioned a problem that I'm picking up with Samba with | OpenLDAP and the "logon hours" restrictions which are implemented via | the NT 4.0 User Manager. | | Basically my problem was that users were unable to login 2 hours before | the actual restriction should kick in. | At the time I thought that perhaps the problem was caused by Slackware | Linux and it's timezone implementation of SAST (GMT+2). | Since then I've experienced the same problem on SLES9 and Suse Linux 9.3. | |> From what I can see, the "sambaLogonHours" value is always set with |> GMT in sambaLogonHours is localtime. Not GMT IIRC. cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - enigmail.mozdev.org iD8DBQFDVi+CIR7qMdg1EfYRAtOjAKDrZ7nl63r9N3t0lCU6mT5UNNW3PgCfcJGx PGEvZLagxfsG1UrX0XabuaY=NWZc -----END PGP SIGNATURE-----
Hi guys, Any ideas on this one ? I've really tried everything now from what I can see. Could it be a problem with the SAST tmezone implementation under Linux ? Is there anyone else I can contact about this problem ? Kind regards David Wilson CNS, CLS, Linux+ 033 3427003 082 4147413 0860-1-LINUX support@dcdata.co.za ----- Original Message ----- From: "David Wilson" <dave@dcdata.co.za> To: "Gerald (Jerry) Carter" <jerry@samba.org> Cc: <samba@lists.samba.org> Sent: Wednesday, October 19, 2005 2:38 PM Subject: Re: [Samba] sambaLogonHours and timezones> Hi Jerry, > > Thanks for your reply. > > The time on the server is set to localtime, the timezone set to SAST > (GMT+2) as are all the XP workstations. > The time on the server and workstations is correct. > > Any ideas why my values are out by 2 hours each time ? > > Thanks for your help so far. > > Kind regards > > David Wilson > CNS, CLS, Linux+ > 033 3427003 > 082 4147413 > 0860-1-LINUX > support@dcdata.co.za > > > ----- Original Message ----- > From: "Gerald (Jerry) Carter" <jerry@samba.org> > To: "David Wilson" <dave@dcdata.co.za> > Cc: <samba@lists.samba.org> > Sent: Wednesday, October 19, 2005 1:35 PM > Subject: Re: [Samba] sambaLogonHours and timezones > > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> David Wilson wrote: >> | Hi guys/girls, >> | >> | How are you keeping ? >> | >> | A while ago I mentioned a problem that I'm picking up with Samba with >> | OpenLDAP and the "logon hours" restrictions which are implemented via >> | the NT 4.0 User Manager. >> | >> | Basically my problem was that users were unable to login 2 hours before >> | the actual restriction should kick in. >> | At the time I thought that perhaps the problem was caused by Slackware >> | Linux and it's timezone implementation of SAST (GMT+2). >> | Since then I've experienced the same problem on SLES9 and Suse Linux >> 9.3. >> | >> |> From what I can see, the "sambaLogonHours" value is always set with >> |> GMT in >> >> sambaLogonHours is localtime. Not GMT IIRC. >> >> >> >> >> >> >> cheers, jerry >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.0 (GNU/Linux) >> Comment: Using GnuPG with Thunderbird - enigmail.mozdev.org >> >> iD8DBQFDVi+CIR7qMdg1EfYRAtOjAKDrZ7nl63r9N3t0lCU6mT5UNNW3PgCfcJGx >> PGEvZLagxfsG1UrX0XabuaY>> =NWZc >> -----END PGP SIGNATURE----- >