I just confirmed an anomaly that I observed a few days ago, regarding my
workstation's ability to synchronize its clock to that of my Netware
4.11+sp9 server. I accomplished this test by intentionally setting the
workstation's clock to be wrong, and then logging in to the server, to
effect a correction.

My workstation, called "RUMBA," is a W2K Pro computer running the Novell
4.91+sp3 client. It successfully logs in to Netware.

I am not complaining about any malfunction, here. I'd just like to
understand how time synchronization happens.

Here is the dilemma:

I would think that the Netware login process alone would effect time
synchronization to a Netware server. But, on the face of it, this doesn't
seem to happen. Why do I say this?

If I am sitting at RUMBA, with its clock in error, I can point my mouse to
the lower right corner, where a red "N" exists in the Windows task bar. By
right clicking on that "N," I can effect a "Novell login." Doing this does
NOT synchronize RUMBA's clock to the server.

So I sit once again at RUMBA, and this time, point to the "Start" button in
the lower left of my Windows desktop. Of course, this usually leads to the
Windows method of shutting down, but instead, I merely elect to "log off
John"; that is, to log off and back on again, at the Microsoft interface.
This process not only logs on to Windows, at the local workstation level,
but also logs in to Netware. (The Netware login occurs first.) NOW the
clock is synchronized to the Netware server.

Why is the Microsoft "logon" process required in order to effect time synch
to a Netware server, when the red "N" alone cannot accomplish this action?