[Fwd: Re: [Fwd: Re: Unable to negotiate a compatible protocol]]
Dan Hunt (dhunt@huntel.net)
Wed, 11 Dec 1996 09:25:17 -0600
Return-Path: <ronnie@itexas.net>
Received: from mailhost.itexas.net ([207.22.198.33])
by htlmail.htlmail.huntel.net (Netscape Mail Server v2.0)
with ESMTP id AAA168 for <dhunt@huntel.net>;
Tue, 10 Dec 1996 14:30:04 -0600
Received: from MidTower.itexas.net ([207.22.198.38]) by mailhost.itexas.net
(post.office MTA v2.0 0813 ID# 0-12497) with ESMTP id AAA139
for <dhunt@huntel.net>; Tue, 10 Dec 1996 14:27:14 -0600
From: ronnie@itexas.net (Ronnie D. Franklin)
To: <dhunt@huntel.net>
Subject: Re: [Fwd: Re: Unable to negotiate a compatible protocol]
Date: Tue, 10 Dec 1996 14:28:22 -0600
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1157
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <19961210202714707.AAA139@MidTower.itexas.net>
Thanks for the Info, but this is happening on customer's that were working
perfectly, and on both Windows 95 and Windows 3.1... It only started in the
last 2-3 weeks and we have solved it temporaly by having the customer
"bring up terminal window after dialing" and then wait for the "login"
prompt before clicking continue.. Works every time... Also, it only happens
when we start getting 50-60 users on line at one time... Works perfectly if
we only have 20-40 users.. so that leads me to believe that it does have
something to do with the PM's or at least a combination of the PM's and
other things.....
----------
> From: Dan Hunt <dhunt@huntel.net>
> To: ronnie@itexas.net
> Subject: [Fwd: Re: Unable to negotiate a compatible protocol]
> Date: Tuesday, December 10, 1996 2:06 PM
>
> Thought I'd share this with you.
>
> Thanks for your reply.
>
> Dan.
>