MSCS: Outbound traffic to different subnet uses wrong NIC

Discussion in 'Server Networking' started by tachnem, Jul 21, 2007.

  1. tachnem

    tachnem Guest

    We've built a two node SQL05 cluster and a two node MSMQ cluster. Both
    clusters are experiencing this issue. Any outbound traffic to the same
    subnet goes out the appropriate public NIC. Any outbound traffic directed to
    a different subnet attempts to go out the private NIC. Both clusters have
    the private NICs connected via crossover cable. Traffic to other subnets
    will only make it's way if I disable the private NIC. I've verified this by
    running a netstat will attempting to ping and telnet.

    Here is an ipconfig, there are 3 cluster resource IPs on the public adapter,
    which also has the gateway. The private NIC is just the crossover with no
    gateway.

    I've tried setting metrics on the adapters, changing the private/public
    position in the Advanced Properties in Network Connections, and also in
    ClusAdmin setting the Private interfaces for internal communication only and
    the Public interfaces for client access only.


    Windows IP Configuration

    Ethernet adapter Public:
    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 10.0.40.X
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : 10.0.40.X
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : 10.0.40.X
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : 10.0.40.X
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 10.0.40.X
    Ethernet adapter Private:
    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 10.0.0.101
    Subnet Mask . . . . . . . . . . . : 255.0.0.0
    Default Gateway . . . . . . . . . :


    Here is a netstat on a telnet to a different subnet:
    TCP 10.0.0.101:3126 10.0.X.X:80 SYN_SENT 2664


    Any insight/suggestions into what could be causing this issue would be much
    appreciated.

    Thanks
     
    tachnem, Jul 21, 2007
    #1
    1. Advertisements

  2. tachnem

    Ryan Hanisco Guest

    Tachnem,

    In the NIC properties | Advanced , you can set the priority on the default
    gateways to go to the proper gateway first.

    Also, not that while you have different subnets between the private and
    public NICs, they are technically on the same 10.0.0.0/8 network. This can
    cause problems. Most people put the heartbeat NIC on a different network
    alltogether 192.168.1.0/30 or allow it to grab an APIPA address.
    --
    Ryan Hanisco
    MCSE, MCTS: SQL 2005, Project+
    Chicago, IL

    Remember: Marking helpful answers helps everyone find the info they need
    quickly.
     
    Ryan Hanisco, Jul 25, 2007
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.