RE: NT 3.51 behavior
Munil Shah <munils@microsoft.com> Wed, 29 May 1996 22:26 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03525;
29 May 96 18:26 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03521;
29 May 96 18:26 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa16838;
29 May 96 18:26 EDT
Received: from localhost by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA25722; Wed, 29 May 1996 18:14:53 -0400
Date: Wed, 29 May 1996 18:14:53 -0400
Message-Id: <c=US%a=_%p=msft%l=RED-75-MSG-960529211920Z-6179@tide21.microsoft.com>
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: Munil Shah <munils@microsoft.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: RE: NT 3.51 behavior
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.838.14
The NT 3.51 DHCP client does not use/handle 012 option. This option is also not included in the requested option list when it sends out DISCOVER/ REQUEST packets, so when it receives 012 option from the dhcp server, it logs this warning message. This is harmless in general. If you want DHCP client to store this option in registry somewhere, you can add that to the Options list under DHCP registry. -Munil >---------- >From: Hank Yung (The Last In Line)[SMTP:hyung@join.com] >Sent: Wednesday, May 29, 1996 1:50 PM >To: Multiple recipients of list >Subject: NT 3.51 behavior > >Hello, > >I am using Microsoft NT 3.51 as a DHCP client to talk to our >server. Everything seems to be working fine but in the Event Log, >I am getting this "warning" message: > >--- >DHCP received an unknown option 012 of length 009. The >raw option data is given below. >--- > >The raw data actually shows the hostname returned by >the server which happens to be 9 bytes long. Option 12 >is the hostname tag (assuming 012 is in decimal and not octal). >Has anyone seen something like this with NT 3.51? What is >the cause of this warning? > >Thanks in advance, > >Hank >-- >Hank Yung Email: hyung@join.com >Competitive Automation, Inc. WWW: http://www.join.com >1050 University Drive, Suite 210 FAX: (415)321-4405 >Menlo Park, CA 94025 Voice/Pager: (415)991-7966 >
- NT 3.51 behavior Hank Yung (The Last In Line)
- Re: NT 3.51 behavior Shawn Mamros
- RE: NT 3.51 behavior Munil Shah
- Re: NT 3.51 behavior Edie E. Gunter
- Re: NT 3.51 behavior Ken Key
- Re[2]: NT 3.51 behavior Luke ROBERTS