I am try to install a Windows 2003 Server to provide DHCP
functionality to replace an existing install of ISC-DHCP running on a
Solaris box.

My application makes use of RFC 3011, option 118, which is the subnet
selection option.

I have a device that has a total of three IP address assigned to it,
one for local traffic, one for secure traffic, and one for remote
traffic. All traffic between this device and the DHCP server
originates from the secure address. The device will act as a relay and
request addresses for other devices in the local subnet and remote
subnets.

Everything works fine with ISC, however Microsoft's implementation
ignores the IP address passed in the option 118 segment and will only
return an address in the secure range. This means that I am unable to
use Microsoft's implementation of DHCP.

Does anyone know of a way to get Microsoft's DHCP server to use the
address that is passed in option 118?

Thanks

stephen.donovan@gmail.com (Stephen Donovan) wrote in
news:4f20885f.0503231526.19ede849@posting.google.c om:

Hi Stephen --

DHCP in WS03 does not implement this RFC, so there is not a way to get this
to work.

--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.

James McIllece [MS] wrote:

Hi James,

Thanks for the info, but I am confused. The following URL indicates at
the bottom of the page that this RFC is supported.

http://www.microsoft.com/technet/its...ices_SB_2.mspx

3011 The IPv4 Subnet Selection Option for DHCP Proposed Standard

Table 24. DHCP RFCs Supported by Windows Server 2003 DHCP

You can run, but you can't hide. Link moved:

http://www.microsoft.com/technet/its...es/ignsbp.mspx

Now in Table 23.

--
Message posted via http://www.winserverkb.com

stephen.donovan@gmail.com wrote in
news:1111670126.246751.236940@l41g2000cwc.googlegr oups.com:


Well I double-checked with the DHCP team and as far as we can tell that
document (which I could not locate) is incorrect, the RFC is not
supported.The DHCP Help specifies the RFCs with which our implementation is
compliant (2131, 2132, 951 for BOOTP,1542 for DHCP/BOOTP relay agent
capabilities, 2365 for multicast, etc.)

--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.

"James McIllece [MS]" <jamesmci@online.microsoft.com> wrote in message news:<Xns962E9373D3EABjamesmcionlinemicros@207.46. 248.16>...

The document has been moved.

http://www.microsoft.com/technet/its...es/ignsbp.mspx

Click on Enterprise Design for DHCP and look at Table 24.

stephen.donovan@gmail.com (Stephen Donovan) wrote in
news:4f20885f.0504090415.73c3cc9a@posting.google.c om:

Thanks for the link -- the first page loaded, but the link page won't load.
There must be some reorganization going on at TechNet, I don't know.

But anyhow I have reverified that the RFC you mentioned is not supported. I
don't know why the document you saw said that it was supported (and if I
can find the doc and owner I will request that it is changed.)

--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.