locked
Question about Dual-NIC and routing for Edge server RRS feed

  • Question

  • Hi All,

     

    This dual NIC concept is confusing me slightly.

     

    Considering the following:

    • External NIC has a public IP pointing to my firewall as a default gateway
    • Internal NIC has an RFC1918 IP address (10.0.0.4/24 for the sake of this argument)
    • OCS 2007 server has an RFC1918 address that is on a different network than that of the Edge Server (10.0.1.4/24 for the sake of this argument)

    In order for the routing to be "predictable" I needed to set the "Default Gateway" on my Internal NIC to have a high metric (100). That is, I want all packets going to unknown networks to go out via my External IP. I then needed to "Enable Routing and Remote Access" and add a static route to my OCS 2007 server and Internal DNS servers via my Internal NIC.

     

    The "OCSEdgeServerDeploy.doc" file does not give any instructions on how to do this or that all of this is necessary. Does it simply assume that the Internal NIC and the OCS 2007 server are on the same subnet?

     

    If not, I'd consider adding a note in the deployment doc mentioning that Enabling and configuring static routes are necessary.

     

    Regards.

    X

    Tuesday, July 24, 2007 5:16 PM

Answers

  • X,

    You don't need to enable Routing and Remote Access on your server.

    You just need to put a default gateway the External NIC (do not change the metric) and static routes to all your private network through your internal NIC.

    To configure the static routes first you need to find the Internal NIC instance, it can be done with the command "route print", it will show you something like this:

    Interface List
    0x1 ........................... MS TCP Loopback interface
    0x20 ...00 13 02 d1 1b b4 ...... External NIC name
    0x452 ...00 16 d4 41 66 76 ...... Internal NIC name

    Then add the route with the command (assuming your internal router is 10.0.0.1):

    route ADD 10.0.0.0 MASK 255.0.0.0  10.0.0.1 METRIC 3 IF 0x452 -p

    The -p is to preserve the route after a reboot.

     

    Hope it is clear.

    Wednesday, July 25, 2007 8:59 PM