multiple NICs Remote Desktop Crash

I have a 2000SBS
I added a second NIC (Netgear GA311) and now when I connect to the server
using remote desktop (both from within the LAN and from outside the firewall)
the server crashes with an IRQ not less or Equal, 0x0000000a, at 8042C24F.
I can log on, and then after a variable length of time (minutes) the crash
occurs.
this occurs even if the card is unused and disabled.
everything else works fine -
This occurred when I first installed the card - I removed it, and Remote
Desktop functioned again.
I reinstalled it (different slot) and it crashes.
Any advice ?(Client is XP, both systems are on latest S/W updates)

Hi Brad,

IRQ not less or Equal is likely to be a resource sharing conflict, or a
dodgy bit of hardware / driver that runs the hardware.

You recently added a network card and now the server is miss-behaving -
Get rid of that card and get a difrrent model from another manucfacturer.


I have used 3com and found those to be OK with multihomed windows 2003
terminal servers.
The NetGear card might be just as good, or even better, it might have just
got damaged in transit but just so you completley eliminate the conflict I
would go for another companys card.

Network cards are so cheap now anyway.

Regards,

Michael



"bradcl" <(E-Mail Removed)> wrote in message
news:CC5046A8-B005-4AAA-90ED-(E-Mail Removed)...
>I have a 2000SBS
> I added a second NIC (Netgear GA311) and now when I connect to the server
> using remote desktop (both from within the LAN and from outside the
> firewall)
> the server crashes with an IRQ not less or Equal, 0x0000000a, at 8042C24F.
> I can log on, and then after a variable length of time (minutes) the crash
> occurs.
> this occurs even if the card is unused and disabled.
> everything else works fine -
> This occurred when I first installed the card - I removed it, and Remote
> Desktop functioned again.
> I reinstalled it (different slot) and it crashes.
> Any advice ?(Client is XP, both systems are on latest S/W updates)
>

That's what I figured, but wanted to see if there was something else that was
a known problem
Guess I'll go to the store again.
thanks


"msnews.microsoft.com" wrote:

> Hi Brad,
>
> IRQ not less or Equal is likely to be a resource sharing conflict, or a
> dodgy bit of hardware / driver that runs the hardware.
>
> You recently added a network card and now the server is miss-behaving -
> Get rid of that card and get a difrrent model from another manucfacturer.
>
>
> I have used 3com and found those to be OK with multihomed windows 2003
> terminal servers.
> The NetGear card might be just as good, or even better, it might have just
> got damaged in transit but just so you completley eliminate the conflict I
> would go for another companys card.
>
> Network cards are so cheap now anyway.
>
> Regards,
>
> Michael
>
>
>
> "bradcl" <(E-Mail Removed)> wrote in message
> news:CC5046A8-B005-4AAA-90ED-(E-Mail Removed)...
> >I have a 2000SBS
> > I added a second NIC (Netgear GA311) and now when I connect to the server
> > using remote desktop (both from within the LAN and from outside the
> > firewall)
> > the server crashes with an IRQ not less or Equal, 0x0000000a, at 8042C24F.
> > I can log on, and then after a variable length of time (minutes) the crash
> > occurs.
> > this occurs even if the card is unused and disabled.
> > everything else works fine -
> > This occurred when I first installed the card - I removed it, and Remote
> > Desktop functioned again.
> > I reinstalled it (different slot) and it crashes.
> > Any advice ?(Client is XP, both systems are on latest S/W updates)
> >
>
>
>

In news:59F81049-CEDD-4583-852C-(E-Mail Removed),
bradcl <(E-Mail Removed)> stated, which I commented on
below:
> That's what I figured, but wanted to see if there was something else
> that was a known problem
> Guess I'll go to the store again.
> thanks

In addition, you will want to choose a NIC that is tested and proven with
WIndows 2003. Some NICs, such as the Intel VL (a desktop NIC), works with
Windows Server, but not with Windows Server Enterprise.

The 3Coms and Intel non-desktop NICs are good choices. As an FYI, (for
anyone else reading this too)I wouldn't choose a USB NIC either. A Linksys
USB I've found caused blue screens with 2000 and 2003.

--
Ace
Innovative IT Concepts, Inc
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...