This article has been archived. It is offered "as is" and will no longer be updated.
When a computer that is running Windows XP or Windows Server 2003 tries to set up a VPN connection to a remote network, the connection is set up successfully. However, the computer may be unable to access the resources on the remote network.
This problem occurs when the remote network's Dynamic Host Configuration Protocol (DHCP) server uses the 249 Classless Static Routes DHCP scope option.
This problem occurs when the routing table on the VPN client computer is not updated. This problem may also occur when the subnet masks are incorrect, even though the routing table is updated.
After the VPN connection is set up, the client computer sends DHCPInform packets to the DHCP server to obtain the DHCP server scope options. If the 249 Classless Static Routes DHCP scope option is configured on the DHCP server, the server sends both classful and classless routes to the client computer. However, this problem occurs when the routing table on the client computer cannot be updated with the classless routes. This problem may also occur when the routing table can be updated, but the subnet masks are wrong.
For example, when the routing table on the client computer is updated, you expect the subnet masks to appear as 255.240.0.0. However, the subnet masks may appear as 255.0.0.240. In this example, the second octet is moved to the fourth octet. When you run the route print command at a command prompt, the route table may resemble the following:
Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows XP Home Edition, Microsoft Windows XP Professional