Timed Block off by 1 hour

Question

I have just finished migrating my BM server (NetWare 6.5 SP7) from 3.8 to 3.9 SP1, and boy am I LOVING the switch from NWAdmin to iManager.
(Smell the sarcasm?)
Anyway, I am trying to reconfigure my timed block rules for the student user groups since the format/config whatever changed and 3.9 won't recognize the old rules.
Here's my problem: I set a rule to deny access for the HS_Students group to http://*.runescape.com*/ from 8:00AM to 3:00PM. It is currently 2:30PM, and the BM server's console TIME command reflects this. However, the student login is not blocked when accessing the URL. If I bump the timed block up to 8:00AM to 4:00PM, the site is blocked.
It appears that BorderManager thinks it is an hour later than it really is. Is this possible when the NetWare OS reports the correct time? Could it be some weird Daylight Saving issue? Do I just need to set the timed block entry to one hour later than it really is and forget about it?

Answer 1

In article <[email protected]>, CrazyFingers
wrote:
> I have just finished migrating my BM server (NetWare 6.5 SP7) from 3.8
> to 3.9 SP1, and boy am I LOVING the switch from NWAdmin to iManager.
> (Smell the sarcasm?)
Well, you can now edit BM configs from Linux, and also from the internet,
so there are some advantages...
>
> Anyway, I am trying to reconfigure my timed block rules for the student
> user groups since the format/config whatever changed and 3.9 won't
> recognize the old rules.
OK.
>
> Here's my problem: I set a rule to deny access for the HS_Students
> group to http://*.runescape.com*/ from 8:00AM to 3:00PM. It is
> currently 2:30PM, and the BM server's console TIME command reflects
> this. However, the student login is not blocked when accessing the
> URL. If I bump the timed block up to 8:00AM to 4:00PM, the site is
> blocked.
Coould it be daylight savings time? I know the BM rules never did
reflect DST time before, meaning you had to change time settings in rules
twice a year. Perhaps 3.9 is actually honoring the time changes now in
some way, and throwing the old rules off by an hour unexpectedly?
> It appears that BorderManager thinks it is an hour later than it really
> is. Is this possible when the NetWare OS reports the correct time?
> Could it be some weird Daylight Saving issue? Do I just need to set
> the timed block entry to one hour later than it really is and forget
> about it?
If you have not changed your rule since DST started this year, you are
probably just seeing what has been there all along.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***