Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DHCP vendor-specific in win-XP

Status
Not open for further replies.

RCNetAdmin

IS-IT--Management
Jun 23, 2003
24
IL
I have an area of PC's with windows XP professional that use DHCP.
I cannot change any thing in the registry or browser of these PC's because they are going to customers, however I must authenticate with the license with Microsoft.
I want to enforce these PC's to work with proxy, with out changing the browser option myself.
However they will be given the option by the DHCP.
I read in MS site that I can use the "vendor-specific" option (using the 252 code in the option).
This didn't work. In the site they wrote that it is for explorer 5 only.

I can I solve this?

Thanks

RC.
 
Vendor specific options
This section describes reserved DHCP option types for assigning vendor-specific information and vendor class use, as specified in RFC 2132. Vendor classes can be added and used by the DHCP Server service to classify supporting vendor-specific DHCP clients that identify themselves using a common vendor class ID when they use DHCP service on your network.

In addition, the DHCP console provides a single default vendor class, the DHCP Standard options class, that can be used to group and classify clients that do not identify a vendor class to the DHCP service.

Vendor specific information
Code: 43
Length: Variable, minimum length of 1 octet.
Value: An opaque object of n octets (where n is equal to the length specified with this option). The definition of values stored for this option type are vendor specific, and values provided here are presumed to be interpreted by a vendor-specific code on DHCP clients and the DHCP server.
Description: This option is used by clients and servers to exchange vendor-specific information. Servers that are not equipped to interpret the information ignore it. Clients that expect but do not receive the information attempt to operate without it.
In some cases, a vendor uses this option type to send more than one information item, in which case, this option can serve as a subfield for encapsulating vendor-specific options. When encapsulating options, DHCP servers maintain the same syntax (that is, the same code, length, and value fields sequence) for each encapsulated option type as it would normally appear in the full standard options field, with the following exceptions for the encapsulated vendor-specific subfield:

"Magic cookies" cannot be used.
All standard option codes--other than the padding option (0) or the end option (255) may be redefined.
If present, the end option (255) signifies the end of the encapsulated vendor options, but not the end of the encapsulated vendor-specific subfield. If no end option is present, the end for the encapsulated vendor-specific subfield is taken from its stated length.

Structure:
Code Len Vendor-specific information
+-----+-----+-----+-----+---
| 43 | n | i1 | i2 | ...
+-----+-----+-----+-----+---
When this option type uses an encapsulated vendor-specific subfield, the information bytes 1-n have the following format:

Code Len Data item Code Len Data item Code
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| T1 | n | d1 | d2 | ... | T2 | n | D1 | D2 | ... | ... |
+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+


Vendor class identifier
Code: 60
Length: Minimum of 1 octet. Length varies according to n (that is, the number of octets used as an identifier).
Value: A value of n octets interpreted by DHCP servers that can support vendor classification of clients.
Description: Can be used by DHCP clients to identify their vendor type and configuration. When using this option, vendors can define their own specific identifier values, such as to convey a particular hardware or operating system configuration or other identifying information.
For Windows 2000, all computers that function as either DHCP servers or clients can use and support this option type. Where vendor classes are used, the DHCP server responds to identifying clients using option code 43 (described above), the reserved option type for returning vendor-specific information to the client.

DHCP servers that do not interpret this option type are expected to ignore it when it is specified by clients. For earlier Windows-based clients and other clients that do not support this option type, the DHCP service classifies these clients as part of the default vendor class, the DHCP Standard options class that is predefined for Microsoft-based DHCP servers.

Structure:
Code Len Vendor class identifier
+-----+-----+-----+-----+---
| 60 | n | i1 | i2 | ...
+-----+-----+-----+-----+---
From Vendor Specific Options Hope this helps.

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin feel free to join the Tek-Tips in Chicago, Illinois Forum.

TTinChicago
Johnson Computers
 
So if I want the DHCP to force working with the proxy, what code do I write?
 
I would use code 43.
[highlight green]For Windows 2000, all computers that function as either DHCP servers or clients can use and support this option type. Where vendor classes are used, the DHCP server responds to identifying clients using option code 43 (described above), the reserved option type for returning vendor-specific information to the client.
[/highlight]


Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin feel free to join the Tek-Tips in Chicago, Illinois Forum.

TTinChicago
Johnson Computers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top