Re[2]: NT 3.51 behavior

Luke ROBERTS <LROBERTS@csfp.csfb.com> Thu, 30 May 1996 12:38 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14762; 30 May 96 8:38 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14758; 30 May 96 8:38 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa06501; 30 May 96 8:38 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA13413; Thu, 30 May 1996 08:32:22 -0400
Date: Thu, 30 May 1996 08:32:22 -0400
Message-Id: <CSFP.LROBERTS.583104080096151FCSFP@CSFB.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: Luke ROBERTS <LROBERTS@csfp.csfb.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re[2]: NT 3.51 behavior
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4


> installed.  Microsoft's NT DHCP server, in turn, can use this hostname,
> coupled with the IP address it provides, to update the WINS server database
> (which, in turn, can feed into an MS NT DNS server, thus providing their
> own form of dynamically updateable DNS).

My understanding is that WINS name registration happens as a separate process,
at the client rather than the server.

The DHCP server will however provide the address of the WINS server(s) to the
client.

--
Luke Roberts                         Internet: lroberts@csfp.csfb.com
PC Engineering                         Telephone: +44 (0)171 516 2260
Credit Suisse Financial Products       1 Cabot Square, London E14 4QJ