We have a win2k3 RRAS server serving up VPN connectivity. Addresses\nare handed out via DHCP relay agent and the network address range is\n10.0.96.0/255.255.252.0. When VPN clients connect, they receive an\naddress in the 10.0.96.0 range with subnet 255.255.255.255 and no\ngateway (when the "Use default gateway on remote network" checkbox is\nunchecked). Quite often, clients are unable to access server resources\nin the 10.0.98.0 range. When we do a route print, we see something\nlike this:\n\n10.0.96.0 255.255.255.0 10.0.96.4 10.0.96.4 1\n\nWhen it does work, we see:\n\n10.0.96.0 255.255.252.0 10.0.96.4 10.0.96.4 1\n\nI am unable to determine why sometimes it hands out the correct subnet\nand other times not. We can work around it buy checking the "Use\nDefault Gateweay" but we'd rather not have the clients' traffic routed\nthrough our slow internet connection (which invariably it ends up\ndoing). We can also blow away the 10.0.96.0 route and add the\ncorrected subnet mask manually. However, we would like this to "just\nwork" without resorting to rebuilding the route on the client end via\nbatch script.\n\nI read the thread at\n[URL]http://groups.google.com/group/microsoft.public.windows.server.networking/browse_thread/thread/8cfb7c2a1250dce0/f5531033487b698f?#f5531033487b698f[/URL]\n\nand it seems that this is by design. However, it doesn't do it\nconsistently - sometimes it is /24, others it is /22.\n\nHow can we get it so that it comes out /22 all the time?\n\n\n\n\nThanks so much!