Networks

Ask something
Question Locked

dual nics

0 helpful
12 replies

by mmv0013

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have 2 network cards in a MS 2003 web edition server. NIC A has a static IP and is connected to my LAN and is working just fine. NIC B has a static IP and is connected to my DMZ. The problem is NIC B stops sending and receiving packets but it doesn?t disable its self so I?ve just repair the connection and it works fine for 6 hours or so.

The system detected that network adapter Intel(R) PRO/1000 PT Dual Port Server Adapter #2 was connected to the network, and has initiated normal operation over the network adapter.

12 replies

by scott_heath

You may have a issue with conflicting routes. Try using "route add" to add persistent routes to the network in the DMZ.

by mmv0013

both subnets on the nics are 255.255.255.0 but all the ips anf gateways are different or is it a windows routing thing if so how do you set that up?

by scott_heath

255.255.255.0 is the subnet mask. That means that the subnet is class C and it would be the first 3 octets of the IP. For instance if my ip address was 63.14.78.56 with a 255.255.255.0 subnet mas then my network address (or subnet) is 63.14.78.56.0. You could run "route print" when the problem is occuring and when it isn't and compare the routing table. You could also post those ehre along with the IP you are trying to get to and I'm sure we could figure it out.

by scott_heath

A repair just runs several standard command line tools you can run yourself. I believe one of the things it does is flush the route table, as well as the dns and netbios cache. Google Windows Network Repair and I bet it will tell you exactly somewhere...

by mmv0013

I wish i could paste an image but i will type out the routing tables

by scott_heath

route print > c:\routes.txt

Then open the file and past the contents

by mmv0013

when its working

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 19 b9 c9 78 dd ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)
0x30004 ...00 15 17 2e 66 9a ...... Intel(R) PRO/1000 PT Dual Port Server Adapter #2
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.30 20
0.0.0.0 0.0.0.0 192.168.1.29 192.168.1.19 20
10.0.0.0 255.255.255.0 10.0.0.30 10.0.0.30 20
10.0.0.30 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.0.0.30 10.0.0.30 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.19 192.168.1.19 20
192.168.1.19 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.19 192.168.1.19 20
224.0.0.0 240.0.0.0 10.0.0.30 10.0.0.30 20
224.0.0.0 240.0.0.0 192.168.1.19 192.168.1.19 20
255.255.255.255 255.255.255.255 10.0.0.30 10.0.0.30 1
255.255.255.255 255.255.255.255 192.168.1.19 192.168.1.19 1
Default Gateway: 10.0.0.1
===========================================================================
Persistent Routes:
None

by mmv0013

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 19 b9 c9 78 dd ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)
0x30004 ...00 15 17 2e 66 9a ...... Intel(R) PRO/1000 PT Dual Port Server Adapter #2
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.30 20
0.0.0.0 0.0.0.0 192.168.1.29 192.168.1.19 20
10.0.0.0 255.255.255.0 10.0.0.30 10.0.0.30 20
10.0.0.30 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.0.0.30 10.0.0.30 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.19 192.168.1.19 20
192.168.1.19 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.19 192.168.1.19 20
224.0.0.0 240.0.0.0 10.0.0.30 10.0.0.30 20
224.0.0.0 240.0.0.0 192.168.1.19 192.168.1.19 20
255.255.255.255 255.255.255.255 10.0.0.30 10.0.0.30 1
255.255.255.255 255.255.255.255 192.168.1.19 192.168.1.19 1
Default Gateway: 192.168.1.29
===========================================================================
Persistent Routes:
None

by sgt_shultz

have you tried a new nic, cable or port? or updated the driver? have you tried locking media type (does that apply to 1000gb?)
sounds like maybe a negotiation glitch.
i think you are looking for zebras and it's just a herd of mules.
anything in the event logs?

by scott_heath

You have 2 default routes. These are specified by the 0.0.0.0 network address with the 0.0.0.0 subnet mask. When everything is working the PC is using the 10.0.0.1 default gateway then it break when using the 192.162.1.29 gateway. My suggestion is that you use a custom persistent route with a lower metric so that it is always used. The metric is the last number on the line and is 20 for both default routes. If you run the command:

route -p add 0.0.0.0 mask 0.0.0.0 10.0.0.1 metric 1

It should make the default route to 10.0.0.1 always have a lower "cost" than the other default route. Let me know if you have any questions and how it goes.

by mmv0013

i ran that command so we will see if it helps...
just wanted to say thanks for the help

This discussion is closed to new replies.