Monitoring system and picky NIC's

[americanmcneil]

I have a Microsoft Server 2003 box in my rack. It has to NIC's in it and they are both Intel Pro/1000's. My problem is this: I use the "Dude" monitoring software. When NIC A is enabled and NIC B is disabled it can see about one third of my network. When I enable NIC B, The other two thirds of my network show up but the first third goes down (graphically on the monitoring system, not actually crashing) Any clues? Any help would be greatly appreciated.

Scott "Thrown to the Wolves" McNeil

http://www.epproach.net

 

[dberg35]

Are both your NIC's configured with Static IP and DNS? Sounds like your network is pulling DNS from each nic.

 

[americanmcneil]

Well it sounded good so i tried it but alas to no avail. Any other possibilities? For the record I checked IRQ's and memory locations for both NIC's and there are no conflicts there either.

Scott "Thrown to the Wolves" McNeil

http://www.epproach.net

 

[GlenJohnson]

Just curious, since you're server is Windows 2003, why are you posting this in the Windows 2000 server forum. Go straight to the forum931 for 2003. Might have better luck. (Oh, and check for bad packets on each of the nic. Had a 2000 server, brand new, and shortly after I brought it online, some of the users could not authenticate. A week or so later, after all the specialists came in and tried to figure it out and couldn't, I realized that when I re-booted the server, people could log on. Shut the server down, people could authenticate. Started checking the nics, which were bound together, and found one was going bad and sending out bad packets. We had bought a very pricey brand new machine with a bad nic from the get-go. Good luck.)

Glen A. Johnson
If you like fun and sun, check out Tek-Tips Florida Forum
Don't forget to Buckle up. It works.
Want the best awnsers for your questions, read faq950-5848

 

[americanmcneil]

Update!!!

First to Glen, sorry about the post placement, all I initially saw was Microsoft server and dove right in. I'll be sure to double check posting areas from here on out.

Second, I got everything to work and here is how. On NIC A I assigned the servers primary IP with subnet, gateway and proper DNS addresses. On NIC B I assigned only IP and subnet information, NO gateway and DNS addresses. On NIC B I have bound adresses to 4 seperate networks and am able to monitor all of my equipment with no worries.

I discovered that when you have gateway and DNS information on both NICs they, for lack of a better phrase, fight for controll of network access.

Anyway, thanks all for the help!!!

Scott "Thrown to the Wolves" McNeil

http://www.epproach.net

 

[kmcferrin]

That is correct. That's why when you put a default gateway address on the second NIC Windows pops up a warning message that says that it only supports the use of a default gateway on the second NIC for redundancy purposes, i.e., you should only specify a default gateway on the second NIC if BOTH NICs are plugged into the same subnet AND you use the same address for the default gateway on both.

After all, you can't have two different "default" anythings. That's the definition of default.