Static Routes from Active Directory do not appear

[Roger Savill]

For some time I have been researching a problem where the Static Routes
(nominated in the Dial-in area of Active Directory) do not take effect on
the remote client.

We have now seen this problem occur at a second site and the problem is now
becomin gquite urgent.

Calls to Microsoft have so far been unsuccessful and they have been unable
to provide further advice on the subject without forking out $300.

The primary question is - What is the mechanism (or protocol) used to push
Static Routes down to the desktop of remote (Dial up VPN) workstations
(running W2KP or WXPP).

The interesting point is that we have the configuration working just fine on
some networks (we manage lots of networks) however two networks do not work.

The Dial-in area of the AD is set to create three seperate static routes to
the Internal (private) networks of the WAN. When a remote station
establishes a Dial up VPN (PPTP) connection it connects fine and obtaines a
valid IP address but the Static Routes do not work. An examination of the
Routing table on the remote workstation confirms that the Routes are not
present.

So far we have been unable to determine the mechanism that the system uses
to create these routes on the remote workstation (we suspect RPC - but
really have no idea) and Microsoft won't tell us. We suspect that the ISA
Server or PIX firewall system may be interfering with the process but in the
absense of some documentation on the problem are unable t odiagnose the
problem further.

Does anybody have any idea how this works and also if there is a resolution
to the problem. Any feed-back would be greatly appreciated.

Thanks


Roger Savill

 

[Herb Martin]

I would consider make the RRAS server a "DHCP Relay Agent"
and then setting the routes on the "DHCP" server -- of course, the
RRAS must acquire address from that DHCP too.

Research the interaction between RRAS and being a "DHCP Relay
AGENT" -- it's a bit odd.