2nd NIC on server with same same network caused sql problems

Discussion in 'Windows Networking' started by CNewsReader, Oct 16, 2008.

  1. CNewsReader

    CNewsReader Guest

    we enabled a 2nd nic on a development sql server with a static IP, we did
    not register the name in dns. we wanted to use the 2nd nic for a planned
    dedicated mirror using only the IP address of the second NIC. I checked
    dns and wins and it desnt show up for that server. we did add a dns name
    to be used by that nic for the mirror. We havent used this nic yet for the
    mirror. we had many issues that came up with batches runnning of that
    server. these were all transport layer errors. Once we disabled the 2nd
    NIC the problems went away. Is there a recommended method to get the 2nd
    nic in the same server on the same net without causing other issues??


    Jason T
    CNewsReader, Oct 16, 2008
    1. Advertisements

  2. Do you mean an IP address on the same subnet as the main NIC? You should
    just add a second IP address to the main NIC for that.
    Anthony [MVP], Oct 16, 2008
    1. Advertisements

  3. CNewsReader

    CNewsReader Guest

    at server has 2 IP addresses(static) on the same subnet( and
    any reason this wouldnt work??

    CNewsReader, Oct 16, 2008
  4. on one nic

    Anthony [MVP], Oct 16, 2008
  5. CNewsReader

    CNewsReader Guest

    Sorry for being so confusing. 2 nics in 1 2003 server. each has an IP
    address as stated below. 1 ip per nic 2 per server.
    CNewsReader, Oct 16, 2008
  6. Hi Carl,
    You need one nic.
    You can have more than one IP on the same subnet on one nic.
    Anthony [MVP], Oct 17, 2008
  7. One nic per subnet! It doesn't matter how many IP#s there are,..one subnet
    is one subnet.

    If you want a second "data network":

    1. It is arguable that the amount of data flow warrents the second network
    for efficiency,...most of the time it does not justify it. In my opinion
    (everyone has one), doing this stuff is usually based on superstition rather
    than the reality of being needed.

    2. The second Nic must be in a different subnet which is determined by the
    IP# and Mask used. It also must be physically separated at the physical
    level (the cabling).

    3. Measures must be taken to insure that the server is properly
    identified/resolved to the correct IP#/Nic when a connection is made to it
    for the correct purpose. This can be done by accessing by the second IP# or
    by a different "Name" that is resolved to the correct IP# by a Hosts File, a
    static WINS Record, or by adding an "A" Record in DNS for this purpose.

    Phillip Windell

    The views expressed, are my own and not those of my employer, or Microsoft,
    or anyone else associated with me, including my cats.
    Phillip Windell, Oct 20, 2008
    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.