Announcement

Collapse
No announcement yet.

Vpn and windows routes.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Vpn and windows routes.

    Hello everybody,

    I have a problem with a vpn connection from a RDP session.

    I'm building a server, It should be for RDP session and from the RDP session established a
    VPN connection to a lot of Customers.
    The server is built from virtual system which has a lot of xp operating systems,
    Each xp be assigned to Each employee to connect with RDP and From there it will connect on
    VPN.

    The issue is that in many cases when the VPN established in the RDP session- the RDP
    session is Falls.
    I tried to set a "route add" in the route table of the xp to my network and it solved the
    problem in some cases.
    but in other cases as in a fortigate sslvpn- Looks at route print that the line i added was
    duplicate by the vpn connetion.

    Example:
    Active Routes:
    Network Destination Netmask Gateway Interface Metric
    0.0.0.0 0.0.0.0 192.99.0.138 192.99.0.1 11
    0.0.0.0 0.0.0.0 192.168.99.12 192.168.99.12 1
    100.100.100.0 255.255.255.0 192.99.0.137 192.99.0.1 2 ****
    100.100.100.0 255.255.255.0 192.168.99.12 192.168.99.12 1 ****
    127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
    192.99.0.0 255.255.255.0 192.99.0.1 192.99.0.1 10
    192.99.0.1 255.255.255.255 127.0.0.1 127.0.0.1 10
    192.99.0.255 255.255.255.255 192.99.0.1 192.99.0.1 10
    192.168.99.12 255.255.255.255 127.0.0.1 127.0.0.1 50
    192.168.99.255 255.255.255.255 192.168.99.12 192.168.99.12 50
    194.90.149.165 255.255.255.255 192.99.0.138 192.99.0.1 1
    224.0.0.0 240.0.0.0 192.99.0.1 192.99.0.1 10
    224.0.0.0 240.0.0.0 192.168.99.12 192.168.99.12 1
    255.255.255.255 255.255.255.255 192.99.0.1 192.99.0.1 1
    255.255.255.255 255.255.255.255 192.99.0.1 3 1
    255.255.255.255 255.255.255.255 192.168.99.12 192.168.99.12 1
    Default Gateway: 192.168.99.12
    ================================================== =========================
    Persistent Routes:
    Network Address Netmask Gateway Address Metric
    100.100.100.0 255.255.255.0 192.99.0.137 1

    192.168.99.12 - this is the gateway of a vpn
    192.99.0.138 - the is the gateway of my network
    The third row is the line I added and after the vpn established Metric gone to 2 from 1,
    and the Fourth row is come true.

    After a lot of searches and googled about this problem i found a "use default gateway on
    the remote network" Option in the vpn properties> networking> TCP\IP> advanced.
    But even here some vpn as SSLVPN returns the check automatically.

    I'll be happy if someone can help.
    Thank you very much!

  • #2
    Re: Vpn and windows routes.

    Something wrong with that routing table, you have 2 default routes. Do you have more than one physical NIC in the server?

    Only your default gateway should normally have the 0.0.0.0 route, as that is the route that should be taken for all traffic that does not have a specific route defined. Unfortunately I don't have a Windows XP machine to test with at the moment, but I would expect a VPN to only add a route to the subnet of the remote network.
    BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
    sigpic
    Cruachan's Blog

    Comment


    • #3
      Re: Vpn and windows routes.

      Hello cruachan,
      I dont have more than one physical NIC in my server.
      When you connect to VPN, virtual NIC is created, his default route is come true and his Metric is becomes lower (1 Value).
      So that my real default gateway bypassed and his Metric is Becomes lower higher (11 Value).

      Comment

      Working...
      X