[Fwd: Re: Unable to negotiate a compatible protocol]

Dan Hunt (dhunt@huntel.net)
Thu, 12 Dec 1996 17:08:07 -0600

Return-Path: <jrowley@bitstorm.net>
Received: from ra.mscnet.net ([207.100.82.2]) by htlmail.htlmail.huntel.net
(Netscape Mail Server v2.0) with ESMTP id AAA241
for <dhunt@huntel.net>; Thu, 12 Dec 1996 14:33:14 -0600
Received: from localhost (jrowley@localhost) by ra.mscnet.net (8.7.5/8.7.3) with SMTP id PAA17544 for <dhunt@huntel.net>; Thu, 12 Dec 1996 15:26:33 -0500 (EST)
Date: Thu, 12 Dec 1996 15:26:32 -0500 (EST)
From: J Rowley <jrowley@bitstorm.net>
X-Sender: jrowley@ra.mscnet.net
To: Dan Hunt <dhunt@huntel.net>
Subject: Re: Unable to negotiate a compatible protocol
In-Reply-To: <Pine.LNX.3.91.961212141934.20627E-100000@server.icenter.net>
Message-ID: <Pine.BSF.3.95.961212152321.17477B-100000@ra.mscnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I just had a customer call with the same problem. After going in circles
for ever it seems, he mentioned that he recently installed the MS Win95
Service Pack 1. We removed that and he's been connecting fine throughout
the day.

For users without the service pack, I recommend that they open a dialup
window after dialing so they manually enter their login/passwd until we
can work out a solution for them. The Service pack is a big cause of the
problems though.

J

> On Tue, 10 Dec 1996, Dan Hunt wrote:
>
> > "Unable to negotiate a compatible protocol" is an error some of my users
> > are experiencing. They result is that they are disconnected before they
> > are able to log in. The customer I'm working with now is using Win95
> > DUN. I know it has happened before but I'm not sure if it's happened in
> > other environments. I'm using a Portmaster 2eR.
> >
> > What causes it? Please respond to me directly as I have unsubscribed
> > from the list due to the high volume of messages. (I don't have the
> > time to sort through everything).