Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Termlite dying?

0 views
Skip to first unread message

Tony Lawrence

unread,
Nov 5, 2002, 1:38:59 PM11/5/02
to
I saw this earler this week:

Customer had a virus, cleaned it, and Termlite stopped working. I went
in, and verified that this was true, Termlite says "Cannot Connect".

However, Windows telnet works.

I completely removed termlite, including its config file, and
reinstalled. Same behavior.

To avoid wasting money, I had the customer download and buy Anzio Lite
which of course is a better product anyway. So I didn't look into this
problem any more deeply.

However, today, someone else called me with the same symptoms, except
they insist that they have had no virus. Termlite can't connect to
anything, Windows telnet can. As he was frantic, I gave him the same
advice, but I'm wondering if anyone else has observed this.


--

Please note new phone number: (781) 784-7547

Tony Lawrence
Unix/Linux Support Tips, How-To's, Tests and more: http://aplawrence.com
Free Unix/Linux Consultants list: http://aplawrence.com/consultants.html


Roberto Zini

unread,
Nov 6, 2002, 6:36:52 AM11/6/02
to
Tony Lawrence wrote:

> I saw this earler this week:
>
> Customer had a virus, cleaned it, and Termlite stopped working. I went
> in, and verified that this was true, Termlite says "Cannot Connect".
>
> However, Windows telnet works.
>
> I completely removed termlite, including its config file, and
> reinstalled. Same behavior.
>
> To avoid wasting money, I had the customer download and buy Anzio Lite
> which of course is a better product anyway. So I didn't look into this
> problem any more deeply.
>
> However, today, someone else called me with the same symptoms, except
> they insist that they have had no virus. Termlite can't connect to
> anything, Windows telnet can. As he was frantic, I gave him the same
> advice, but I'm wondering if anyone else has observed this.
>
>

Tony,

I had a similar problem in the past (TermLite could __NOT__ connect
whereas telnet did) and I was able to solve it by replacing the
WINSOCK.DLL file on the offending machine with a good one (and by "good
one" I mean I got it from a working Windows box - same version, of
course :-).

Please mind you that there are many WINSOCK.DLL scattered across the
filesystem: please check their size against the ones you have on a
"working" box.

Best,
Roberto

--
---------------------------------------------------------------------
Roberto Zini email : r.z...@strhold.it
Technical Support Manager -- Strhold Evolution Division R.E. (ITALY)
---------------------------------------------------------------------
"Has anybody around here seen an aircraft carrier?"
(Pete "Maverick" Mitchell - Top Gun)

0 new messages