Hello, i have 2 gigabit network adapters connected to a network bridge, but when i check the data sent and received, i only see it on 1 adapter and the other adapter won't show and sent and received data. thanks

1. Network adapters are on different subnets, I hope. 2. What is the output of ipconfig /all ? 3. Are network cards correctly "registered" in device manager? 4. What is output of route print ? 5. What are settings on card and bridge sides (auto, half..., full..) ? 6. What is the traceroute response, eg. tracert 8.8.8.8 ? 7. What would happen with network traffic, if you temporarily disable the "correct" network card? Regards Milos

To connect network bridge with two network adapters, they must be in different subnets. Why do you want to connect one network device with two network adapters on the same machine? One of the two network adapter will not get ip address until the other is disabled, if they are in the same subnet. Do you have two subnets? The 192.168.1.xx and 10.110.255.xx? I think you should set the two network adapters as different subnets manually. You may add route table to configurate your network manually. The IP routing table http://technet.microsoft.com/en-us/library/cc779122(v=ws.10).aspx Hope that helps. Ivan-Liu TechNet Community Support

Do you mean your NICs are connected to a actual network bridge device? Or, are they bridged together inside of Windows? I'm believing that you mean that they are bridged together to form 1 large network. When you bridge your 2 NICs you create one logical NIC using the 2 physical. With this, you are unable to configure both NICs and are only able to configure the newly created bridged adapter which translates & forwards all traffic to & from the 2 physical NICs. Hope this helps ______________________________ "Look deep & find your........Resolve." ______________________________

Do you mean your NICs are connected to a actual network bridge device? Or, are they bridged together inside of Windows? I'm believing that you mean that they are bridged together to form 1 large network. When you bridge your 2 NICs you create one logical NIC using the 2 physical. With this, you are unable to configure both NICs and are only able to configure the newly created bridged adapter which translates & forwards all traffic to & from the 2 physical NICs. Hope this helps ______________________________ "Look deep & find your........Resolve." ______________________________

the network cards are correctly registered in device manager. both of the settings of the cards is full. even if i disable the correct card, the bridge will disconnect and reconnect with the second card. ipconfig /all results Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Fit>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : STI Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No System Quarantine State . . . . . : Not Restricted Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) Physical Address. . . . . . . . . : 00-26-83-14-AD-5E DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Network Bridge: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : MAC Bridge Miniport Physical Address. . . . . . . . . : F6-6D-04-19-32-43 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::d197:13a0:17e8:693e%20(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.30(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DHCPv6 IAID . . . . . . . . . . . : 855769121 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-45-C5-D5-F4-6D-04-19-32-43 DNS Servers . . . . . . . . . . . : 192.168.1.1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : TAP-Win32 Adapter OAS Physical Address. . . . . . . . . : 00-FF-B7-04-79-63 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Tunnel adapter isatap.{7C23F938-56BC-4DA4-88CC-2D34F1B0B92F}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:c2e:36a1:27c5:adbb(Prefe rred) Link-local IPv6 Address . . . . . : fe80::c2e:36a1:27c5:adbb%12(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter isatap.{B7047963-46D1-45B1-9CAF-47C4C5B5DF10}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes route print Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32>route print =========================================================================== Interface List 26...00 26 83 14 ad 5e ......Bluetooth Device (Personal Area Network) 20...b2 48 7a 81 3f df ......MAC Bridge Miniport 17...00 ff b7 04 79 63 ......TAP-Win32 Adapter OAS 1...........................Software Loopback Interface 1 11...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3 =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.30 266 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.1.0 255.255.255.0 On-link 192.168.1.30 266 192.168.1.30 255.255.255.255 On-link 192.168.1.30 266 192.168.1.255 255.255.255.255 On-link 192.168.1.30 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.1.30 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.1.30 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 192.168.1.1 Default 0.0.0.0 0.0.0.0 192.168.1.1 Default 0.0.0.0 0.0.0.0 192.168.1.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 12 58 ::/0 On-link 1 306 ::1/128 On-link 12 58 2001::/32 On-link 12 306 2001:0:5ef5:79fd:c97:3944:3f57:fee1/128 On-link 20 266 fe80::/64 On-link 12 306 fe80::/64 On-link 12 306 fe80::c97:3944:3f57:fee1/128 On-link 20 266 fe80::f488:9f46:5d2f:eb1a/128 On-link 1 306 ff00::/8 On-link 12 306 ff00::/8 On-link 20 266 ff00::/8 On-link =========================================================================== Persistent Routes: None tracert 8.8.8.8 Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Fit>tracert 8.8.8.8 Tracing route to google-public-dns-a.google.com [8.8.8.8] over a maximum of 30 hops: 1 8 ms 16 ms 12 ms 10.110.255.1 2 17 ms 34 ms 17 ms 24.156.149.129 3 9 ms 21 ms 13 ms gw-mcnicol1-to-ipr02.distributel.net [206.80.244 .92] 4 23 ms 13 ms 13 ms ae2-1402.ipr02.distributel.net [206.80.244.89] 5 19 ms 10 ms 11 ms gw-google.torontointernetxchange.net [206.108.34 .6] 6 13 ms 24 ms 14 ms 216.239.47.114 7 40 ms 30 ms 36 ms 216.239.46.170 8 39 ms 59 ms 57 ms 72.14.239.93 9 39 ms 36 ms 38 ms 72.14.236.200 10 39 ms 35 ms 35 ms 216.239.49.145 11 35 ms 40 ms 35 ms google-public-dns-a.google.com [8.8.8.8] Trace complete.

To connect network bridge with two network adapters, they must be in different subnets. Why do you want to connect one network device with two network adapters on the same machine? One of the two network adapter will not get ip address until the other is disabled, if they are in the same subnet. Do you have two subnets? The 192.168.1.xx and 10.110.255.xx? I think you should set the two network adapters as different subnets manually. You may add route table to configurate your network manually. The IP routing table http://technet.microsoft.com/en-us/library/cc779122(v=ws.10).aspx Hope that helps. Ivan-Liu TechNet Community Support