NTP is the tool of choice for synchronizing time. But this should be a network project, not just a couple of machines. Ultimately, all your computers should be running NTP to remain synchronized. Start with a very high accuracy time source--there are dozens on the Internet, and always specify more than 3 or 4. NTP can maintain time witnin 128ms accuracy.
Now if your firewall prevents the NTP port from going to the Internet, then you'll need a local time source (could be a GPS unit, your HP-UX box or with special software, a PC) and then sync all the boxes to that server with possible alternates.
Now if the two boxes (HP-UX and Win2k) are off because of timezones, you definitely do NOT want to change the HP-UX box to match a different timezone. HP-UX, like most flavors of Unix, can handle any timezone dynamically, and you can create any custom timezone. The key os in the environment variable TZ. For IST, set this in your HP-UX .profile:
export TZ=GMT+2
and then type the date command. All time references in this environment will be IST. The key is that you can create a custom environment for time anywhere on earth using the TZ variable. This means that your Kerberos server can be in any timezone. And NTP always maintains time internally as GMT.
Bill Hassell, sysadmin
