Posted by Neil Badger on December 18, 2006 at 13:33:26:
My biggest customer has a head office running c2k3 with ten branches each with a winxp server. One of the branch servers cooked last Friday. As it is closer to me than them I decided to put my test machine in there to get them up & running. I upgraded it to the latest everything, Microsoft & Comet, everything went reasonably smoothly. Every night we use CometAnywhere to transfer mobs of stuff bakwards and forwards, after the first transfer I could no longer connect with CA from my home. The window came up but was totally empty, so I couldn't log on. Dialling in with PCanywhere, the initiating screen for CA is there but also dead, no response to anything. Reboot of PC fixed it briefly. Eventually I became suspicious of the transfer from the Head office. I noticed that the HO was not at the same level of software so I took them up to 6.11 & 375. This appeared to fix the problem, until just now it has gone again. All branches have the ability to CA into all other branches. Does the system still do that updating of the versions when you connect thru CA and if so does it raise and lower versions. Could there be an incompatability between the latest version & an earlier version, probably about 6.08 & 372, that could cause this confusion, as each different branch logs on and churns the versions up & down ?
If the update thing still happens which way does it go and which end is in control ?
Hope this makes more sense than that which I am seeing.
Badge