Static Rolute Option for Win2K DHCP server

[Gregory James]

The DHCP service for Windows 2000 server offers a Static Route Option (33)
which assigns static routes to clients.

The option accepts address pairs: Destination/Gateway
It does not provide a means of assigning a network mask to the destination.
We're attempting to setup the static route option with the following address
pair: 192.168.20.0/192.168.10.15.

The route is indeed distributed to DHCP clients, but the netmask for the
destination is 255.255.255.255, rendering the route essentially useless.

There's a document referring to this problem with respect to the DHCP server
in WinNT. However, it does not povide any specific means of fixing it. Any
suggestions from anyone? Or is this option simply broken?

Thanks,
Greg

 

[Roland Hall]

:
: The DHCP service for Windows 2000 server offers a Static Route Option (33)
: which assigns static routes to clients.
:
: The option accepts address pairs: Destination/Gateway
: It does not provide a means of assigning a network mask to the
destination.
: We're attempting to setup the static route option with the following
address
: pair: 192.168.20.0/192.168.10.15.
:
: The route is indeed distributed to DHCP clients, but the netmask for the
: destination is 255.255.255.255, rendering the route essentially useless.
:
: There's a document referring to this problem with respect to the DHCP
server
: in WinNT. However, it does not povide any specific means of fixing it. Any
: suggestions from anyone? Or is this option simply broken?

Hi Gregory...

What is your goal here? You want to set static routes on only certain
clients? If not, is there a reason why you're not setting them on the
router? Microsoft uses Option 33 to assign pairs of addresses:
destination/router. You assign the destination and then the router. When
you look at your DHCP scope, you'll see it under server options. If you
want another static route, you assign it with two more addresses (pairs),
destination/router.

MSFT DHCP Static Route Option (33) is from RFC 2132: 5.8.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;121005
http://www.faqs.org/rfcs/rfc2132.html
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q312468

I've never used this option and it appears you have to have an application
that takes advantage of it. If you're wanting to use it as an alternative
to putting static routes on a router, I'm not sure if that is the purpose of
this option as a general use.

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201