Time sync

Ok, are both servers in the same tree? If your answer is yes and one was installed after the other, then the first one will automatically be the primary and every other server installed into the tree after that will point to the first. When you moved the both servers into the same network, I hope that you used inetcfg and changed the default gateway and the subnet mask to reflect that. If you didn't, that will certainly cause communications problems. As for the ip or ipx issue, if your clients use queue-based printing, they NEED IPX. You can leave both protocols attached to both servers so that they can communicate until you move to NDPS. Each server must share one common protocol to communicate correctly, though. In the inetcfg menu, there is a command to reinitialize so that you DONT have to reboot the server, and still change ip and ipx addresses on the fly. Make sure that both network numbers match on the ipx addresses so that the servers communicate correctly. Use tcp/ipfor the time source number.

Check to see if time is the problem.

load DSREPAIR at the console, and run the time sync check. If it's out, see what the servers are set to.

Make sure that the SET parameters for default timesync type are the same as timesync type.

I wouldn't use configured sources if there are only two servers, and I also wouldn't bother with NTP either. Clock drift can be a concern, but not much of a concern really, it's easy to do an adjustment, and generally, new servers don't drift more than a minuite a month or so.

Turn service advertising on, and the servers will find each other using SAP.

Kev.

IP or IPX doesn't matter, just make sure both have something in common, and that they can communicate correctly using that protocol. IPX: same network for same frametype? IP: same range, subent mask and default gateway?
If they are on the same network, and there's only 2, they don't need "configured sources" at all, they'll find everything themselves.
There's no need to reboot, "set timesync restart flag=on" should do the trick for sure. "set timesync reset=on" will read most of the changesyou make, but will not change the server type, for example.

If you want to be sure if time sync really is your problem, there's two things you can do:
-type "time" (+enter) on the console. It should read that "time is synchronised to the network" on all servers.
-type "set timesync debug=7" (+enter). This will show a debug screen on which you can monitor time traffic. If you haven't changed the default interval (600 sec, or 10 minutes), you should see which server contacts which other, and if it was successful or not, every 10 minutes.

What "application problems" are you exactly talking about? Are you sure they're time-sync related?

Jim

This question was closed by the author