Can you run netstat at the command prompt and tell us what you see? Do you have any firewall software installed? What OS do you have? Do you have a NIC installed? What does your cconsole.log say? Any luck with a regular telnet client instead of the terminal? I had something similar to this recently but it was an issue with Norton. Norton would periodically block Cache. It would be fine on boot up, but after a restart Norton blocked it. Disabling the firewall resolved the issue.
"powerfox" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I've encountered the prob described in this article: > > -------------------------------------------------------------------------- -- > September 26, 2003 - Cach� and McAfee product conflict > > InterSystems WRC has received several reports that Cach� will not run > correctly when McAfee Personal Firewall v.4 or McAfee Virus Scan v.7 are > installed on the same system. The following symptoms have been observed: > > TELNET daemon fails to start at Cach� startup with message: > " CTELNETD startup error, bind (sock) failed, Reason: WSAENOTSOCK" > > GUI connections fail with: > " Unable to connect to cn_iptcp 127.0.0.1[1972];%SYS" or a similar message. > > These problems occur because of the filtering implemented in McAfee's > CSLSP.DLL. Note that because the conflict is in a DLL, it is not > necessary for the McAfee products to be running on a system, having them > installed is enough to trigger the conflict. > > The problems can occur with any version of Cach� but only on Windows > platforms. > > McAfee has addressed this conflict in McAfee Personal Firewall Plus v.5 > and McAfee Virus Scan v.8. InterSystems WRC has tested these versions > with Cach� and found that the problems no longer exist. > > If the system is not using the HAWK function of McAfee Virus Scan and is > not using the McAfee Personal Firewall it is possible to avoid this > problem by removing CSLSP.DLL as follows in the Windows Start menu: > Start > run > regsvr32 "C:\winnt\system32\CsLsp.dll" /u > -------------------------------------------------------------------------- - > > but...i don't have installed any MacAfee product...and the CsLsp.dll is > not present in my system... > > then..i've changed parameters in Administrative Tools -> Services to run > Cache` as Local System Account and i've allowed it to Interact with > Desktop,as described in this article: > > ----------------------------------------------------------------------- > May 14, 2003 - Telnet Connections on Cach� Windows > > InterSystems WRC has recently encountered a situation where the number > of telnet connections to Cach� is artificially limited. The symptom of > this problem is that telnet connections will fail once a threshold has > been reached. The threshold has been observed to be 150-190 connections > depending on memory configuration. An inconsistent error message will be > returned to the failing processes. The message may be a generic Windows > application error with a memory address, it may be "Connection Refused" > or "Connection Timeout". If a telnet connection is failing with a > message concerning licensing then it is not due to the issue covered by > this alert. > > All versions of Cach� on Windows NT or 2000 are susceptible to this issue. > > If these symptoms are being observed it is probably because the Cach� > Controller service has been set to run as something other than local > system. This can be seen in the Windows Control Panel -> Administrative > Tools -> Services -> Cache Controller for [Cache instance] -> Properties > -> Log On tab -> Log on as: and should be set to "Local System account" > and the check box for "Allow services to interact with desktop" should > be checked. > > If Cach� must run as a specific user, the Cache Controller service > should still be set to run as "Local System account" but use the Cach� > Network Server user name and password found in the Cach� Configuration > Manager Advanced tab -> Input/Output to enter the Windows user as whom > Cach� should run in the DOMAIN\user format. > ---------------------------------------------------------------------- > > > NOTHING.... :( i continue to receive this message: Unable to connect to > cn_iptcp 127.0.0.1[1972] .... > > how can i solve this problem?? > > TY!!
