two network adapters on a dual processor - on interrupt routing



Hello,
I have two network cards on an Inte lXeon, Windows server 2003.
Both nics (network cards) are recieving packets continously.

I was told that windows would ensure that interrupts from each nic
would go to different processors. Do you think this would be the
case?.

The task manager shows very little activity in second processor and
lots in first.

In any case, I want to find out which processor the ISR is running on.
I don't think an NDIS driver can include/call ntddk apis (like
KeGetCurrentProcessorNumber). Is there any NDIS call which would tell
me the current processor?.

Thanks for your time.
csguy

.



Relevant Pages

  • Re: Event ID 1123 and 1122
    ... So basically even though I am treating all NIC as individual NICs when you ... BASP is a Broadcom intermediate software driver for Windows Server 2003, ... Chuck Timon, Jr. ... drivers on the cluster nodes, this happened from the start of this ...
    (microsoft.public.windows.server.clustering)
  • Re: Network connectivity problems
    ... MVP - Windows Server - Clustering ... I also verified that the switch settings match the ... HeartBeat NICs? ...
    (microsoft.public.windows.server.clustering)
  • Re: Can see all interfaces with NLB when adding a host
    ... The NICs are set to "Automatic metric". ... > 323437 How To Configure Network Load Balancing Parameters in Windows Server 2003 ... > Windows NT/2000/2003 Cluster Technologies ...
    (microsoft.public.windows.server.clustering)
  • Re: HELP ME VPN SERVER SETUP ON WIN2K SERVER
    ... company just upgraded their peer to peer network to domain network. ... They installed Windows Server 2003 with one NIC as Domain Controller, ... ipconfig /all they sent to us displays the two NICs are in the same IP range, ...
    (microsoft.public.win2000.ras_routing)
  • Re: Problem with Server2k3 dropping network configuration
    ... It sounds as if your NICs are going to sleep. ... the power management setting for the NIC. ... I have seen this happen now on two different ASUS motherboards. ... So I would think it's definitely an issue with windows server 2003 ...
    (microsoft.public.windows.server.networking)