I'm having some problem with static routes after update from Windows 2003 Server to Windows 2008 Server R2.
Server has two NIC cards. One for Internal and other for Internet.
RRAS is enabled for accept PPTP connections and clients are connecting as expected.
At AD, on Dial-In, "Apply Static Routes" is enabled. Assign "Static IP Addresses" too, with 10.1.1.2 value.
After the VPN established the route appear on ROUTE PRINT, but don't work. If i manually remove "route delete 192.168.2.0" and recreate it with "route add 192.168.2.0 mask 255.255.255.0 10.1.1.2" it works.
Exactly same setup on Windows 2003 and is working fine.
How can I fix it?
- Edited by Tobias Tromm Monday, September 24, 2012 4:24 PM
- Edited by Aiden_CaoModerator Tuesday, September 25, 2012 6:17 AM
Thanks for the detailed information.
Could you please let us know why you want to add the route 192.168.2.0 mask 255.255.255.0 10.1.1.2 after the VPN connection establish?
The issue is because by the two routes will forward 192.168.2.0 packet with different interface. For more detailed information, you may check the routing table of RRAS management console.
The following is an example:
The static route we configured in Dial-in properties will use the internal interface.
The manually created route will use the Internet connected interface.
TechNet Community Support
This is my network:
(10.0.0.X) Internal LAN -> 2008 R2 SERVER COMPUTER -> PPTP LAN (10.1.1.1) -> External LAN (192.168.25.1) < - > INTERNET (X.X.X.X IP) < - > PPTP ROUTER (10.1.1.2) - Internal LAN (192.168.2.X, 192.168.3.X, 192.168.1.X).
192.168.2.0 is remote subnet.
Please, let me know if you understand.