Posted by Mike Saunders on February 18, 2009 at 06:05:10:
For those that have not realized this yet.
Comet Workstation v.394 and up use a "SERVICE" version of Comet File server.
(As opposed to an "application" version)
Currently my client PC's are mostly Vista, with users running as Standard Users. I have not problem in the past updating these clients to current workstation versions. As these are just "clients", I had NEVER installed the Comet Server Products on these systems.
When I attempted to update a Comet v.393 to v.395, I found it would not connect.
Turns out that workstation v.394 and v.395 did not include the "service" version of the server,
Once I installed Comet Server Products v.9 on this system it was then able to connect.
Comet Workstation v.396 does install the "service" version of the Comet Server and works without installing the Comet Server Product.
Some caveats to this are...
1) The Comet File Server Service Starts on system start.
2) The Comet File Server Service will ALWAYS be running on a client system, even when Comet is not running.
3) It will always have port 11754 open and be listening for a connection.
4) The Comet File Server Service does not shut down when Comet Workstation exits.
5) If I attempt to do a switch user, the user switched to will be greeted with a Create Pipes Error 231 on the File Server UI
I realize that there were technical reasons why this was done.
I just was looking raise the awareness of these changes.
I was a bit surprised that no one else posted.
so perhaps it is just me....
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.