RRAS VPN client doesn't get route update

Hi all,

If this has been answered before, just point me to the post.

I have a RRAS VPN server (W2003 standard) providing access
to my network. Most clients (almost all XP) connect
without problems and are able to route into my internal
network. However, some clients don't update their routing
tables to allow IP traffic to the office LAN.

Specifically, the RRAS server straddles the DMZ and an
admin network at my colo, so clients receive an IP address
on the admin net. From there, IP traffic is routed back to
the office over a private WAN. I turned off the "make
connection the default gateway" because the admin net does
not have access to the internet.

Most clients receive a route update that makes their
VPN-assigned IP address another gateway, and this works
fine for most users. However, the problem is that some
clients don't get this route update. They can talk to the
"local" admin net since they have an IP address on it, but
are unable to route to anything else on my network.

I can solve this temporarily by having them type a ROUTE
ADD command, but this only works for the current
connection. Since client IP's are assigned dynamically, I
can't add a route statement to the connection profile.

So, what's the deal here? I can't find a common thread
between client machines, connection type, etc. Is there a
way I can add a route statement that will grab the client's
IP address on the fly? That would seem the best way to be
sure the problem is solved.

Thanks in advance for your help,
Scott

Where does the client get this route change from? Does it come from a
router? Perhaps it is from RIP?

To receive RIP updates, the client must have RIP listener installed. You
add it from Add/remove Programs in the Networking section.

"Scott" <(E-Mail Removed)> wrote in message
news:286001c4a73e$256dcba0$(E-Mail Removed)...
> Hi all,
>
> If this has been answered before, just point me to the post.
>
> I have a RRAS VPN server (W2003 standard) providing access
> to my network. Most clients (almost all XP) connect
> without problems and are able to route into my internal
> network. However, some clients don't update their routing
> tables to allow IP traffic to the office LAN.
>
> Specifically, the RRAS server straddles the DMZ and an
> admin network at my colo, so clients receive an IP address
> on the admin net. From there, IP traffic is routed back to
> the office over a private WAN. I turned off the "make
> connection the default gateway" because the admin net does
> not have access to the internet.
>
> Most clients receive a route update that makes their
> VPN-assigned IP address another gateway, and this works
> fine for most users. However, the problem is that some
> clients don't get this route update. They can talk to the
> "local" admin net since they have an IP address on it, but
> are unable to route to anything else on my network.
>
> I can solve this temporarily by having them type a ROUTE
> ADD command, but this only works for the current
> connection. Since client IP's are assigned dynamically, I
> can't add a route statement to the connection profile.
>
> So, what's the deal here? I can't find a common thread
> between client machines, connection type, etc. Is there a
> way I can add a route statement that will grab the client's
> IP address on the fly? That would seem the best way to be
> sure the problem is solved.
>
> Thanks in advance for your help,
> Scott