I think I have an intersting workaround for you, but there are a few choices:
1. Install the NOVELL CLIENT32 on ALL of your workstations. Then you can specify in the client settings to "Set Workstation Time" to OFF. Then your MS Client for MS Networks will do its job.
OR
2. Modify your "Get Nearest Server" requests AT the Novell server to "NO". PROCEED WITH EXTREME CAUTION HERE as it will cause all of your clients to not get logged into that server.
OR
3. First, install the CLIENT32 on theNT server. Then install something freeware onto NT that get's atomic time sources and syncs the time from the Net to that NT server - then setup the NW 3.12 server as a SECONDARY TIME SOURCE. Next you have to then setup NW3 to sync itself to that Workstation (the NT server).
See Novell TID 2930686 to setup TIME SYNC. This doc applies to NW 3.x as well as all the newer stuff (4.x and 5.x)
Back when I worked around this issue (before we had a NW5 server) I had to use another piece of shareware (RK-NETplus from http://www.rk.net) to get the Novell server to sync via a workstation vs. the other way around, but it CAN be done.
Hope this info solves your dilema.
Regards