none
Window server 2008 R2 Routing between 2 subnet using RRAS

    Question

  • I just installed server 2008 r2 and can not get it to route between 2 subnets using RRAS.  Server 2003 works fine with the same setup.

    load all the updates, turned off the filewall, tried using rip. tried adding staic routes will not route.  Will route fine using Nat and or vpn. 

     

    using 2 nic card

    Setup is like this : subnet one   ----   server  ---- subnet two

     

     

     

     

    Tuesday, August 10, 2010 10:50 PM

Answers

  •    RRAS in 2008 R2 works just like RRAS in 2003. How have you configured the default gateways? It will only work "out of the box" if the  router is the default gateway for both subnets.

     192.168.1.x   dg 192.168.1.1
           |
      192.168.1.1    dg  blank
         RRAS
      192.168.2.1    dg  blank
           |
      192.168.2.x    dg 192.168.2.1

    If one subnet is using another router, you need to use NAT, or add extra routing to the existing gateway router to get traffic to the internal router.

       Internet
      192.168.1.1
           |
      192.168.1.x   dg 192.168.1.1
           |
      192.168.1.254 dg  192.168.1.1
          RRAS
      192.168.2.1   dg  blank
           |
      192.168.2.x   dg  192.168.2.1    

       Without NAT you need a static route on the gateway router to get traffic for 192.168.2.0 to the internal router.

    192.168.2.0 255.255.255.0 192.168.1.254


    Bill
    • Proposed as answer by Ace Fekay [MCT]MVP Wednesday, August 11, 2010 4:18 AM
    • Marked as answer by Tiger Li Friday, August 13, 2010 1:48 AM
    Tuesday, August 10, 2010 11:46 PM
  • Thanks for your fast respone , as far as a can see am configed as in Bill Grant post  unless did something wrong


    internet
    168.177.222.10 (interface)
     |
    168.177.222.0  255.255.255.0 dg 168.177.222.10 (subnet)
     |
    168.177.222.6 dg 168.177.22.10 (interface)
     RRAS
    168.177.221.130 dg blank (interface)
     |
    168.177.221.128 255.255.255.128 dg 168.177.222.6 (subnet)


    Hi ,

    I think incorrect default gateway setting of clients in 168.177.221 ip segment caused this issue, please check if it worked with change this entry to 168.177.221.130.

    Thanks.

    Tiger Li


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Ace Fekay [MCT]MVP Thursday, August 12, 2010 6:09 PM
    • Marked as answer by Tiger Li Friday, August 13, 2010 1:48 AM
    Thursday, August 12, 2010 2:04 AM
  • Thanks for your fast respone , as far as a can see am configed as in Bill Grant post  unless did something wrong


    internet
    168.177.222.10 (interface)
     |
    168.177.222.0  255.255.255.0 dg 168.177.222.10 (subnet)
     |
    168.177.222.6 dg 168.177.22.10 (interface)
     RRAS
    168.177.221.130 dg blank (interface)
     |
    168.177.221.128 255.255.255.128 dg 168.177.222.6 (subnet)


    Hi ,

    I think incorrect default gateway setting of clients in 168.177.221 ip segment caused this issue, please check if it worked with change this entry to 168.177.221.130.

    Thanks.

    Tiger Li


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    I agree. I'm not sure why 168.177.221.128 255.255.255.128 dg 168.177.222.6 (subnet)" was configured, because any host on that subnet has no idea how to get to dg 168.177.222.6, but they can set it to 168.177.221.130, which does know how to get to 168.177.222.10, which is the "doorway" (gateway) to the "world," so to speak.
    Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003, Microsoft Certified Trainer, Microsoft MVP - Directory Services. This posting is provided AS-IS with no warranties or guarantees and confers no rights.
    • Marked as answer by Gjohnson_99 Thursday, August 12, 2010 4:28 PM
    Thursday, August 12, 2010 5:06 AM

All replies

  •    RRAS in 2008 R2 works just like RRAS in 2003. How have you configured the default gateways? It will only work "out of the box" if the  router is the default gateway for both subnets.

     192.168.1.x   dg 192.168.1.1
           |
      192.168.1.1    dg  blank
         RRAS
      192.168.2.1    dg  blank
           |
      192.168.2.x    dg 192.168.2.1

    If one subnet is using another router, you need to use NAT, or add extra routing to the existing gateway router to get traffic to the internal router.

       Internet
      192.168.1.1
           |
      192.168.1.x   dg 192.168.1.1
           |
      192.168.1.254 dg  192.168.1.1
          RRAS
      192.168.2.1   dg  blank
           |
      192.168.2.x   dg  192.168.2.1    

       Without NAT you need a static route on the gateway router to get traffic for 192.168.2.0 to the internal router.

    192.168.2.0 255.255.255.0 192.168.1.254


    Bill
    • Proposed as answer by Ace Fekay [MCT]MVP Wednesday, August 11, 2010 4:18 AM
    • Marked as answer by Tiger Li Friday, August 13, 2010 1:48 AM
    Tuesday, August 10, 2010 11:46 PM
  • I agree with Bill. As for the static routes, here's an example to go by:

    Static Route Example
    http://i966.photobucket.com/albums/ae147/acefekay/Visios%20for%20Public%20Posting/StaticRoutingExample.jpg 


    Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003, Microsoft Certified Trainer, Microsoft MVP - Directory Services. This posting is provided AS-IS with no warranties or guarantees and confers no rights.
    Wednesday, August 11, 2010 4:18 AM
  • Hi,

    Please post the "ipconfig /all" and "route print" result of your RRAS server here for further investigation.

    How to Use Static Routes with Routing and Remote Access Service

    http://support.microsoft.com/kb/178993

    Thanks.

    Tiger Li


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, August 11, 2010 4:20 AM
  • Thanks for your fast respone , as far as a can see am configed as in Bill Grant post  unless did something wrong


    internet
    168.177.222.10 (interface)
     |
    168.177.222.0  255.255.255.0 dg 168.177.222.10 (subnet)
     |
    168.177.222.6 dg 168.177.22.10 (interface)
     RRAS
    168.177.221.130 dg blank (interface)
     |
    168.177.221.128 255.255.255.128 dg 168.177.222.6 (subnet)


    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\admin>route print
    ==========================================================================
    Interface List
     24...........................RAS (Dial In) Interface
     11...00 15 17 78 7a 4f ......Intel(R) PRO/1000 PT Dual Port Server Adapte
     10...00 15 17 78 7a 4e ......Intel(R) PRO/1000 PT Dual Port Server Adapte
      1...........................Software Loopback Interface 1
     12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
     13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
     14...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
     16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
    ==========================================================================

    IPv4 Route Table
    ==========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metri
              0.0.0.0          0.0.0.0   168.177.222.10    168.177.222.6    26
            127.0.0.0        255.0.0.0         On-link         127.0.0.1    30
            127.0.0.1  255.255.255.255         On-link         127.0.0.1    30
      127.255.255.255  255.255.255.255         On-link         127.0.0.1    30
        168.177.206.0  255.255.255.224   168.177.222.10    168.177.222.6     1
      168.177.206.192  255.255.255.192   168.177.222.10    168.177.222.6     1
      168.177.206.192  255.255.255.224   168.177.222.10    168.177.222.6     1
        168.177.212.0    255.255.255.0   168.177.222.10    168.177.222.6     1
      168.177.221.128  255.255.255.128         On-link   168.177.221.130    26
      168.177.221.128  255.255.255.128    168.177.222.6  168.177.221.130     2
      168.177.221.130  255.255.255.255         On-link   168.177.221.130    26
      168.177.221.255  255.255.255.255         On-link   168.177.221.130    26
        168.177.222.0    255.255.255.0         On-link     168.177.222.6    26
        168.177.222.6  255.255.255.255         On-link     168.177.222.6    26
       168.177.222.79  255.255.255.255         On-link    168.177.222.79    30
      168.177.222.255  255.255.255.255         On-link     168.177.222.6    26
            224.0.0.0        240.0.0.0         On-link         127.0.0.1    30
            224.0.0.0        240.0.0.0         On-link     168.177.222.6    26
            224.0.0.0        240.0.0.0         On-link   168.177.221.130    26
            224.0.0.0        240.0.0.0         On-link    168.177.222.79    30
      255.255.255.255  255.255.255.255         On-link         127.0.0.1    30
      255.255.255.255  255.255.255.255         On-link     168.177.222.6    26
      255.255.255.255  255.255.255.255         On-link   168.177.221.130    26
      255.255.255.255  255.255.255.255         On-link    168.177.222.79    30
    ==========================================================================
    Persistent Routes:
      Network Address          Netmask  Gateway Address  Metric
              0.0.0.0          0.0.0.0   168.177.222.10  Default
    ==========================================================================

    IPv6 Route Table
    ==========================================================================
    Active Routes:
     If Metric Network Destination      Gateway
     14   1110 ::/0                     2002:c058:6301::c058:6301
      1    306 ::1/128                  On-link
     14   1010 2002::/16                On-link
     14    266 2002:a8b1:dd82::a8b1:dd82/128
                                        On-link
     14    266 2002:a8b1:de06::a8b1:de06/128
                                        On-link
     14    266 2002:a8b1:de4f::a8b1:de4f/128
                                        On-link
     10    266 fe80::/64                On-link
     11    266 fe80::/64                On-link
     11    266 fe80::514b:eca0:b832:3f/128
                                        On-link
     10    266 fe80::99fd:f289:614b:c755/128
                                        On-link
      1    306 ff00::/8                 On-link
     10    266 ff00::/8                 On-link
     11    266 ff00::/8                 On-link
    ==========================================================================
    Persistent Routes:
      None   
     
     
    C:\Users\admin>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : server14
       Primary Dns Suffix  . . . . . . . : senate.utleg.org
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : Yes
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : senate.utleg.org

    PPP adapter RAS (Dial In) Interface:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : RAS (Dial In) Interface
       Physical Address. . . . . . . . . :
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 168.177.222.79(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.255
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection 2:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 PT Dual Port Server Ad
    pter #2
       Physical Address. . . . . . . . . : 00-15-17-78-7A-4F
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::514b:eca0:b832:3f%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 168.177.221.130(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.128
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 285218071
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-EE-25-8E-00-15-17-78-7A-4

       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 PT Dual Port Server Ad
    pter
       Physical Address. . . . . . . . . : 00-15-17-78-7A-4E
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::99fd:f289:614b:c755%10(Preferred)
       IPv4 Address. . . . . . . . . . . : 168.177.222.6(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 168.177.222.10
       DHCPv6 IAID . . . . . . . . . . . : 234886423
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-EE-25-8E-00-15-17-78-7A-4

       DNS Servers . . . . . . . . . . . : 168.177.206.10
                                           168.177.206.194
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{41EFC523-CD80-4887-B31B-AD2F4F18E64B}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{F22BA1AA-A29F-4369-A1E5-78CAD672D9E7}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter 6TO4 Adapter:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft 6to4 Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2002:a8b1:dd82::a8b1:dd82(Preferred)
       IPv6 Address. . . . . . . . . . . : 2002:a8b1:de06::a8b1:de06(Preferred)
       IPv6 Address. . . . . . . . . . . : 2002:a8b1:de4f::a8b1:de4f(Preferred)
       Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
       DNS Servers . . . . . . . . . . . : 168.177.206.10
                                           168.177.206.194
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter isatap.{6E06F030-7526-11D2-BAF4-00600815A4BD}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Wednesday, August 11, 2010 6:46 PM
  • Thanks for your fast respone , as far as a can see am configed as in Bill Grant post  unless did something wrong


    internet
    168.177.222.10 (interface)
     |
    168.177.222.0  255.255.255.0 dg 168.177.222.10 (subnet)
     |
    168.177.222.6 dg 168.177.22.10 (interface)
     RRAS
    168.177.221.130 dg blank (interface)
     |
    168.177.221.128 255.255.255.128 dg 168.177.222.6 (subnet)


    Hi ,

    I think incorrect default gateway setting of clients in 168.177.221 ip segment caused this issue, please check if it worked with change this entry to 168.177.221.130.

    Thanks.

    Tiger Li


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Ace Fekay [MCT]MVP Thursday, August 12, 2010 6:09 PM
    • Marked as answer by Tiger Li Friday, August 13, 2010 1:48 AM
    Thursday, August 12, 2010 2:04 AM
  • Thanks for your fast respone , as far as a can see am configed as in Bill Grant post  unless did something wrong


    internet
    168.177.222.10 (interface)
     |
    168.177.222.0  255.255.255.0 dg 168.177.222.10 (subnet)
     |
    168.177.222.6 dg 168.177.22.10 (interface)
     RRAS
    168.177.221.130 dg blank (interface)
     |
    168.177.221.128 255.255.255.128 dg 168.177.222.6 (subnet)


    Hi ,

    I think incorrect default gateway setting of clients in 168.177.221 ip segment caused this issue, please check if it worked with change this entry to 168.177.221.130.

    Thanks.

    Tiger Li


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    I agree. I'm not sure why 168.177.221.128 255.255.255.128 dg 168.177.222.6 (subnet)" was configured, because any host on that subnet has no idea how to get to dg 168.177.222.6, but they can set it to 168.177.221.130, which does know how to get to 168.177.222.10, which is the "doorway" (gateway) to the "world," so to speak.
    Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003, Microsoft Certified Trainer, Microsoft MVP - Directory Services. This posting is provided AS-IS with no warranties or guarantees and confers no rights.
    • Marked as answer by Gjohnson_99 Thursday, August 12, 2010 4:28 PM
    Thursday, August 12, 2010 5:06 AM