Posted by Jim Barbaruolo on December 27, 2006 at 12:39:56: Uploaded files: 2
We recently installed a new Windows 2003 server to replace an older Novell server for Comet at one of our customers. I installed CometServerProducts608 along with CometWorkstation373. Tuesday morning (12/26)and again this afternoon (12/27) the customer has encountered a system hang (Comet only) and when attempting to re-start Comet they receive the following Comet Startup error message: "The Comet Net Server "N01" at address: 10.1.1.253 could not be connected." Once the user clicks the "OK" box Comet lists all the dirs it could not open (all dirs) and will not run. If I reboot the server Comet runs fine. I have attached two COS startup logs for your review. One "Bad" and the other "Good". One thought we had was it might be a port conflict, since the Comet security server connects ok, but not the CFAM server, yet both use the same IP address. I was able to "telnet" to the IP and port 11752 from the workstation PC's, yet they cannot connect to the Comet CFAM File server prgm. Any ideas?