Re: Seeking "net time" Response without Active Directory



gcatlin@xxxxxxxxxxxxx wrote:
Martin, Danny, and Ryan, thank you for the suggestions. The
punchclock software we use is pcEntry by Paychex. Below are some
points that my original post overlooked.

1. We do have Windows servers; but our workstations, a combo of (a)
Win2000 with no firewall, (b) WinXP with the Windows Firewall and an
exception for 'File and Print Sharing,' and (c) a couple Vista boxes,
are not receiving a reply to "net time". It had been my understanding
that to receive a reply to "net time" required on a domain controller,
and we don't have any of them.


Installing ntpd solves these problems.

2. Our servers get the time from ntp sources, but it's my
understanding that being ntp-aware isn't enough to cause a Windows
workstation to receive a reply when they issue a "net time" query.

3. I did not know that if we enable samba on our Linux server we could
have our 'net time' requests replied to. I'll try to figure out how
to do that.

4. The reason we need to continually synchronize our devices during
the day to a reliable time source is because we have devices with
internal clocks that drift +/- quite a bit during a workday. The
people with the fast clocks wave 'goodbye' to those with the slow
clocks as they head out the door; the people with the slow clocks
grunt and blame the network administrator. A hundred or so
workstations are involved; so various registry tweeks to increase the
frequency of the "Internet Time' in Control Panel 'Date and Time'
would be too much of a headache.


This is normal. The computer manufacturers put no effort into getting
good clock hardware and buy the cheapest that they can find. NTP is
designed to deal with this and keep the clocks disciplined so that they
never drift. That's why it would be worth your while to install NTP so
you don't have this problem.

5. If we get "net time" to work, then all local stations (punchclocks)
should the same time, effectively locking down the time used for
punches. That would be good because someone was fired here a few years
ago for advancing their clock by an hour or so, punching out and
leaving. We do not want to offer that temptation.


On Windows, you can set the privileges so that noone has the privilege
to change the time, except for an adminstrator (and ntpd).

Danny
Glenn in NJ
.



Relevant Pages

  • Re: Seeking "net time" Response without Active Directory
    ... We do have Windows servers; but our workstations, ... are not receiving a reply to "net time". ... simplifies installation with a predefined configuration on a large number ... internal clocks that drift +/- quite a bit during a workday. ...
    (comp.protocols.time.ntp)
  • Re: Seeking "net time" Response without Active Directory
    ... punchclock software we use is pcEntry by Paychex. ... We do have Windows servers; but our workstations, ... are not receiving a reply to "net time". ... internal clocks that drift +/- quite a bit during a workday. ...
    (comp.protocols.time.ntp)
  • Re: SDRAM arrrgh :(
    ... >Front Side Bus Frequency 132.9 MHz ... >CAS# Latency 2.0 clocks ... >Windows version Microsoft Windows XP Professional Service Pack 1 ...
    (sci.electronics.repair)
  • Re: 500ppm - is it too small?
    ... Richard> clocks can meet this criterion I'm not going to worry about it. ... If that is really not the case for Windows, then somebody who has a much ... much that it cannot recover. ...
    (comp.protocols.time.ntp)
  • Re: SDRAM arrrgh :(
    ... > Name Intel Pentium III EB ... > CAS# Latency 2.0 clocks ... > Windows version Microsoft Windows XP Professional Service Pack 1 ... the intel 810 takes up to PC100 memory. ...
    (sci.electronics.repair)