Posted by Grant Foraker on October 30, 2009 at 12:49:12:
Customer upgraded their servers from Win2000 to Win2008 over the July 4th weekend. One server is standard file server etc. One server is dedicated to Comet.
The server vendor did the AD and data migration. I came in on Saturday and got Comet running on the new server and updated to latest Comet (399) and CometServer (9.05). The CometANywhere host and the IT guys Comet were running fine. Left it to the local IT guy to go around to the other Comet users and change their desktop icon to point to the new server.
On Monday, the Comet users immediately reported that Comet would take 25-30 to start. From icon click to splash screen. Previously it was 2-3 seconds. Once started Comet runs with no delays.
The server vendor, firewall vendor, and a few other outside experts have been in to work on other minor glitches. There were problems with reference to the old servers and IP's in DHCP and WINS. There was the hope that these fixes would also fix the Comet startup problem. Nope.
There seems to be three different scenarios.
1) 18 users always get the 25-30 second delay. The users power down their PC's every night.
2) the CometAnywhere host had never gotten the delay. But, it stays up almost full time. Comet might be restarted once a week.
3) the IT guy's Comet is about 50/50.
So, to help find this last glitch, I need to know more about what happens between the icon click and the splash screen. Some tidbit I can pass onto the IT guy.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.