Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more ➡
Standard view
Full view
of .
Add note
Save to My Library
Sync to mobile
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
DHCP Vendor ID Implementation in 1 Series

DHCP Vendor ID Implementation in 1 Series



|Views: 5,381|Likes:
Published by surkal

More info:

Published by: surkal on Jul 23, 2009
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See More
See less





DHCP Vendor ID Implementationin 1 Series
A Technote bySystems Engineering
March 2006
Wyse Product Support 
This technote describes how DHCP Vendor ID is used and implemented in Blazer or 1Series Winterms. It assumes that the reader is familiar with basic DHCP and Blazerspecific server configuration parameters.
Level Support, Systems Engineering Group
Affected Products
WTOS 4.4 and 5.0 based 1000 series terminals.
DHCP (Dynamic Host Configuration Protocol) is an Internet protocol standard whichallows a booting host to configure itself dynamically without user supervision. It providesa means to obtain IP configurations from DHCP servers. The interoperability ofconfiguration services based on the DHCP in an environment of heterogeneous clientsdepends on clients accurately identifying themselves and their relevant characteristics toconfiguration servers. The class identifier provided through DHCP option 60 helps inthis regard. Different IP configurations can be sent from the server based on the DHCPvendor ID (DHCP option 60) provided by client.It should be noted that theoretically Vendor Class Identifier (DHCP option 60) shouldwork together with Vendor Specific Information (DHCP option 43) to provide a completesolution for customers who want to provide different set of network configurations toindividual Vendor Class product. Once configured, DHCP client sends a Vendor ClassIdentifier in option 60 of its discovery/request/inform packets to identify itself to theDHCP server. Using the Vendor Class Identifier information, DHCP server responds withspecific set of DHCP option values in option 43 of its offer and ack packets. DHCPoption values embedded in option 43 follows the same “Code-Length-Data” format thatis used in standard DHCP options field. But we will not implement option 43, the vendorspecific tag at this time in 1000 series terminals.DHCP Vendor ID is defined in RFC 2132 section 9.13 (
Based on DHCP Vendor ID sent by client, different configurations can be sent fromDHCP server to the client. This enables the customers to customize the environment theterminals operate. An example is setting different FTP server rootpath (thus differentwnos.ini) for different group of clients. Similar requirement will arise if two different setsof terminals should use two different Rapport servers.
DHCP Vendor ID implementation in 1 Series Page 2 of 5
Wyse Product Support 
Here are the steps to enable the DHCP Vendor ID for the 1 Series.First, follow Microsoft’s procedures on configuring the DHCP Vendor ID server side.
How to Create a New DHCP User or Vendor Class
Windows 2000 provides two option classes an administrator can use to manage configuration detailsfor DHCP clients within a particular DHCP scope. These option classes are vendor-defined and user-defined classes.Vendor-defined classes are used for managing DHCP options assigned to clients identified by vendortype.User-defined classes are used for managing DHCP options assigned to clients identified by acommon need for a similar DHCP options configuration.After defining an option class, individual scopes must be configured with any class-related options tobe provided to clients.
Create a New User or Vendor Option Class
1. Start DHCP Manager.2. In the console tree, click the applicable DHCP server branch.3. Right-click the server, and then click
Define User Classes
to create a new user class, or click
Define Vendor Classes
to create a new vendor class.4. Click
.5. In the
New Class
dialog box, type a descriptive identifying name for the new option in the
Display name
box. You may also add additional information to the
box.6. Type in the data to be used by the DHCP Server service for matching the class ID provided byDHCP clients under
. To enter the data as hexadecimal byte numeric values, click theleft side of the text box. To enter data as American Standard Code for Information Interchange(ASCII) text character values, click the right side of the text box.7. Click
, and then click
Configure a DHCP Scope with the New Class ID
1. In DHCP Manager, double-click the appropriate DHCP scope.2. Right-click
Scope Options
and then click
Configure Options
.3. Click
.4. Click to select the check box or boxes next to the features you want to use with the new vendoror user class.5. Click
Next, make sure to specify the FTP directory for option tag 162 you wish to use. Bydefault we use “ftproot\wyse\wnos\wnos.ini”. I changed the 162 value to WyseDHCP1and the new structure for the wnos.ini is now “ftproot\WyseDHCP1\wyse\wnos\wnos.ini”Lastly amend the wnos.ini file w/ the appropriate command and DHCP Vendor ID.
My command looks like this in my test:
DHCP Vendor ID implementation in 1 Series Page 3 of 5

Activity (4)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
古赫群 liked this
payo9999 liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->