Domain – Stop unwanted network traffic on second nic

domainnetworking

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?

Best Answer

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.

Related Solutions

Linux – Configuring second NIC knocks server off the network

Couple of notes:

If you have a bond with two ports connected to the same unmanaged switch, it won't support the necessary protocols to bond the ports together. You must use mode=active-backup
No, your previous configuration won't affect your setup now.
The martians are a result of having two NICs on the same subnet. They're being sent to eth1 as they're broadcast packets. Other than cluttering your logs, you shouldn't have trouble with these in your setup.
the transmit timeouts look like some sort of a hardware problem

What you should do:

Try running: ip addr flush dev eth1; ip link set up dev eth1 to see if merely bringing up eth1 causes eth0 to fail. If it does, you likely have hardware problems.
Set up a single bonded interface (mode=active-backup) with both eth0 and eth1 as slaves and assign the server's IP address to that.

Force traffic out a specific nic on same network

Disclaimer: This is ugly and bad, and you should not do it.

Here's how to do it (from an elevated command prompt):

First, do a route print and get the name of the interface that you want to force traffic out of. This will be the number all the way to the left of the entry in the Interface list. Then, enter this command:

route add -p 1.1.3.0 MASK 255.255.255.0 10.35.1.254 METRIC 1 IF <foo>

If you do a route print, you should see the route in the route table. Make sure it has the lowest metric.

Best Answer

Related Solutions

Linux – Configuring second NIC knocks server off the network

Force traffic out a specific nic on same network

Related Topic