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

Dan Hunt (dhunt@huntel.net)
Wed, 11 Dec 1996 09:24:54 -0600

Return-Path: <steve@headwaters.com>
Received: from ns1.bellglobal.com ([198.235.216.1])
by htlmail.htlmail.huntel.net (Netscape Mail Server v2.0)
with SMTP id AAA229 for <dhunt@huntel.net>;
Tue, 10 Dec 1996 11:15:41 -0600
Received: from headwaters.com (credit.headwaters.com [204.101.212.2]) by ns1.bellglobal.com (SMI-8.6/8.6.12) with SMTP id MAA20473 for <dhunt@huntel.net>; Tue, 10 Dec 1996 12:12:51 -0500
Received: by headwaters.com; (5.65/1.1.8.2/12Aug95-1259PM)
id AA30424; Tue, 10 Dec 1996 12:27:17 -0500
Date: Tue, 10 Dec 1996 12:27:17 -0500 (EST)
From: "Stephen B. Henry" <steve@headwaters.com>
Subject: Re: Unable to negotiate a compatible protocol
To: Dan Hunt <dhunt@huntel.net>
In-Reply-To: <32AD91D6.40D6@huntel.net>
Message-Id: <Pine.3.89.9612101212.A26618-0100000@headwaters.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Dan,

I think you'll find this is specifically a Win95 problem and it is at the
client end. It has nothing to do with the PM. It seems to happen most
often when more than one protocol (IPX and/or NetBEUI as well as TCP/IP)
is installed in "NETWORKS". For some reason Win95 can't seem to keep the
bindings straight and will periodically use another protocol (or NO
protocol) when trying to make the connection.

Seems to be fixed in the latest bug fix... er... there are no bugs in
Win95... it's the latest "enhancement" release!

Regards,

Steve

Stephen B. Henry steve@headwaters.com
Director of Operations http://www.headwaters.com/
headwaters network http://www.headwaters.com/steve/
a division of WebNET Corporation member: HTML Writer's Guild

"As the most participatory form of mass speech yet developed, the
Internet deserves the highest protection from government intrusion..."
-- Philadelphia Federal Court in ruling sections of
the Communications Decency Act unconstitutional.