Posted by Robert G Laurin on June 04, 2004 at 17:53:14:
In Reply to: node abort/comet time out posted by Dave Hahner on June 04, 2004 at 11:34:30:
We are still running CometSrv.NLM on our Novell 4.11 server with Comet 2002.
We do get those "Comet time out errors" once in a while.
I've seen it on a couple stations including our CometAnywhere and our eComet XAP machines which are both running Win2k Server - soon to be upgraded to Windows server 2003.
There does not seems to be any apparent link with the actual Windows version as I have seen it on Windows XP and 98se as well.
However, I did notice that it seems to happen either when the station has been sitting idle for a very long time and/or when the station is idle for a certain period of time with an excessively busy network (you can actually feel the network sluginess).
I've also noticed that some network ressources have a tendency to "disconnect" itself when a station is idle for a while. Accessing a windows shared resource (like a shared printer) seems to take forever... (I hate Windows!)
We are upgrading our Novell 4.11 to Novell 6.5 next week-end. At that time I will also power up a Windows server running CometServe32. That means that I will now have 2 CometServe - a Novell and a Windows. At the same time we shall upgrade to Comet 2004.
I can't wait to see how all of these new systems behave !!!