Posted by Grant Foraker on July 08, 2004 at 07:48:52:
One of my customers has a Win2000 network with a Linksys DSL router/firewall. The Linksys also provides DHCP. Not my preference. The LAN was set up by another vendor.
Several months back the customer added CAW. It's hosted on a Win98 PC that runs 24/7 and also serves as their FAX. Once, from a power outage, and once, from a forced reboot, CAW failed to reinitialize when /PN=Office1 restarted. Comet runs but the request for CAW sessions is denied. Checking the Security Console, I could see two entries for Office1 and "2 of 2" for the CAW sessions.
The Linksys has no settings in the DHCP for leasing so every reboot results in a new IP for the Win98 workstation. To recover, I have to adjust the IP forwarding to direct CAW to the new IP, have all the Comet users exit, force close Security and File (I think File is OK but I do it anyway), restart Security and File. CAW is reset to "0 of 2". Office1 starts properly and gets the two CAW sessions.
Apparent, Security doesn't recognize the returning Office1 and adds it as a new user instead of "refreshing". The new IP is probably the culprit.
So, I have changed the Win98 workstation to a fixed IP. If there's no forced reboot or power outage in the next few weeks, I may pull the plug on the CAW host and see how things recover :)