HP3000-L Archives

February 2005, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Alex van Denzel <[log in to unmask]>
Reply To:
Alex van Denzel <[log in to unmask]>
Date:
Tue, 8 Feb 2005 14:04:28 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
 DJe wrote:

> "Broadcom NetXtreme Gigabit Ethernet" mean W2K3 found the driver, right?

Not quite. This only means that W2K3 found some sort of device-id and/or
device-class, probably with the PCI vendor/device/subsystem/function IDs.

It also found a INF file that seemed to know about this device-id, and
installed the driver with the information of the INF file.

It's possible that the driver in the Windows 2003 _seem_ to work, from
the viewpoint of the OS, and parts of the device do actually work, and
signal the appropriate messages to the driver, but not necessarily the
whole of the device does work.

I remember something with NT4 server and an Intel Pro100B network card.

Try installing the newest driver for the device. Download it from the
Broadcom site.

But before we are going off in the wrong direction: do the
link-status-leds on the network card and/or the hub/switch indicate a
working link? Maybe you are using crossover cables instead of straight
(computer to switch), or straight instead of crossover (computer to
computer).

--
Alex

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2