Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I work for a company who make a networking product.

The device we create is attached to the testing PC via a second NIC and is on a seperate subnet to the primary nic on the corporate lan.

We are running Win 7 x64 is that makes a great deal of difference!

When we run wireshark, we're seeing the usual broadcast messages etc related to domain machines (i.e. the machine itself is a member of a domain, and keeps sending out broadcasts on all nic's relating network discovery etc)

Can anyone suggest ways of stopping this traffic and guaranteeing we only have the traffic we expect on that one nic?

share|improve this question

You need to go to the properties of the second NIC and disable the "Client for Microsoft Networks" and "File and Printer Sharing for Microsoft Networks" components; then, you should go to the advanced TCP/IP settings and disable NetBIOS over TCP/IP.

It should also be good to disable automatic DNS registration and ensure no default gateway is configured on this second NIC.

share|improve this answer

What is the traffic you expect on that NIC?

You can unbind whatever network components aren't needed on that NIC, such as:

  1. Client for Microsoft Networks

  2. QOS Packet Scheduler

  3. File and Printer Sharing for Microsoft Networks

  4. Link-Layer Topology Discovery Mapper I/O Driver

  5. Link-Layer Topology Discovery Responder

  6. TCP/IPv6 if it's not needed

  7. Disable NetBIOS over TCP/IP

To unbind these components, simply uncheck the appropriate boxes and/or select the appropriate options.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.