Announcement

Collapse
No announcement yet.

TCP/IP on disabled NIC

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

  • TCP/IP on disabled NIC

    Hi folks.

    I have seen many MRXSMB, event id. 3019 discussions. In thinking about this, I'd like to ask the following question after spending considerable time trying to resolve this issue on multiple branch servers.

    One thing occurred to me and that was many of these servers are multihomed; not using the additional NIC but it is there anyway and in a disabled state. However, I have seen strange things with MS networking stacks before and a thought was that this 3019 error could be being caused by the disabled NIC. By default they always are set to DHCP client and also NetBIOS from the DHCP server in the WINS properties. Not saying I did that, just saying that is a default setting.

    Is there any harm in removing TCP/IP altogether from the disabled NIC? Any possible repercussions of removing NetBIOS from this unused NIC?

    Thanks in advance.

    --james

  • #2
    Re: TCP/IP on disabled NIC

    Nope, since it's disabled it wouldn't harm.
    Also I would check your bindings just to be sure.
    Marcel
    Technical Consultant
    Netherlands
    http://www.phetios.com
    http://blog.nessus.nl

    MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
    "No matter how secure, there is always the human factor."

    "Enjoy life today, tomorrow may never come."
    "If you're going through hell, keep going. ~Winston Churchill"

    Comment


    • #3
      Re: TCP/IP on disabled NIC

      Dumber beat me to it.
      I've frequently seen weirdness caused by having disabled NICs at the top of the binding order, more so in Server 2008 as it seems to change it's binding order at times.
      BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
      sigpic
      Cruachan's Blog

      Comment

      Working...
      X