"bad addr len ... 52:41 ..." FIX
John Kemp <kemp@network-services.uoregon.edu> Thu, 20 June 1996 22:39 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06054;
20 Jun 96 18:39 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06050;
20 Jun 96 18:39 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa18822;
20 Jun 96 18:39 EDT
Received: from localhost by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA04607; Thu, 20 Jun 1996 18:37:33 -0400
Date: Thu, 20 Jun 1996 18:37:33 -0400
Message-Id: <199606202234.PAA29452@timber.uoregon.edu>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John Kemp <kemp@network-services.uoregon.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: "bad addr len ... 52:41 ..." FIX
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
This bad addr len from from Ethernet address 52:41:53:20:00:AD or similarly bogus address appears to come from NT3.5.1 and or NT's RAS. The fix is: NT 351 Control Panels Network Installed Network Software Remota Access Service [ select ] Remove ( or disable ) Got a good lead from Microsoft, then tested it here. Fixed two out of two! John Kemp (kemp@ns.uoregon.edu)
- "bad addr len ... 52:41 ..." FIX John Kemp