Netgear GA311 Gigabit ethernet drivers for WinServer2003 ???

Does anybody know where I can find drivers for Netgear GA311 that work on
Server2003? I can't find any anywhere and I'm sure they must exist for this
card. I seen statements by people on the internet saying that the card
works fine on Server2003 - that's why I bought it.

Cheers

ss.

Synapse Syndrome wrote:
> Does anybody know where I can find drivers for Netgear GA311 that
> work on Server2003? I can't find any anywhere and I'm sure they must
> exist for this card. I seen statements by people on the internet
> saying that the card works fine on Server2003 - that's why I bought
> it.
Try XP Pro drivers

--
Alex

Sig on old laptop - new one coming soon.
www.drzoidberg.co.uk www.ebayfaq.co.uk

"Dr Zoidberg" <AlexNOOOO!!!!!!!@drzoidberg.co.uk> wrote in message
news:(E-Mail Removed)...
> Synapse Syndrome wrote:
>> Does anybody know where I can find drivers for Netgear GA311 that
>> work on Server2003? I can't find any anywhere and I'm sure they must
>> exist for this card. I seen statements by people on the internet
>> saying that the card works fine on Server2003 - that's why I bought
>> it.
> Try XP Pro drivers
>

The Netgear installer stops saying that it only works on 98/2000/XP.
Running it in XP compatibility mode doesn't work either.

ss.

depending on the driver, you may be able to get around this.
most installers (i.e. ones that aren't needlessly complicated) will
unpack a load of .inf etc files that the device needs to work, and then
automate the process of allowing windows to pick them up for use.
what you can often do (and good installers often have a specific
command line switch for doing this for exactly this purpose) is
install, examine the .inf files etc it generates, and then copy those
files onto the win2003 box. in device manager, use "install driver
from specified location" and point it at them. we have to do a lot of
buggering around with things like this when we're working on client
autobuilds - where you don't want the automatic build to be wasting
time prompting you do hit "next" etc.

whether all this mither is worth it, compared to getting another NIC is
another matter though!
ric

Also, look at the .inf files for the vid and pid values (they may appear
multiple times) and make sure they match the hardware. You can search the
registry for "ga31" and see what values windows is looking for vid/pid
(Vendor ID, Product ID). If they are different, edit the inf file and make
them match.

....kurt


"ric" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> depending on the driver, you may be able to get around this.
> most installers (i.e. ones that aren't needlessly complicated) will
> unpack a load of .inf etc files that the device needs to work, and then
> automate the process of allowing windows to pick them up for use.
> what you can often do (and good installers often have a specific
> command line switch for doing this for exactly this purpose) is
> install, examine the .inf files etc it generates, and then copy those
> files onto the win2003 box. in device manager, use "install driver
> from specified location" and point it at them. we have to do a lot of
> buggering around with things like this when we're working on client
> autobuilds - where you don't want the automatic build to be wasting
> time prompting you do hit "next" etc.
>
> whether all this mither is worth it, compared to getting another NIC is
> another matter though!
> ric
>

"Kurt" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Also, look at the .inf files for the vid and pid values (they may appear
> multiple times) and make sure they match the hardware. You can search the
> registry for "ga31" and see what values windows is looking for vid/pid
> (Vendor ID, Product ID). If they are different, edit the inf file and make
> them match.
>
> ...kurt
>
>
> "ric" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) oups.com...
>> depending on the driver, you may be able to get around this.
>> most installers (i.e. ones that aren't needlessly complicated) will
>> unpack a load of .inf etc files that the device needs to work, and then
>> automate the process of allowing windows to pick them up for use.
>> what you can often do (and good installers often have a specific
>> command line switch for doing this for exactly this purpose) is
>> install, examine the .inf files etc it generates, and then copy those
>> files onto the win2003 box. in device manager, use "install driver
>> from specified location" and point it at them. we have to do a lot of
>> buggering around with things like this when we're working on client
>> autobuilds - where you don't want the automatic build to be wasting
>> time prompting you do hit "next" etc.
>>
>> whether all this mither is worth it, compared to getting another NIC is
>> another matter though!
>> ric
>>

Thanks guys, I found out that the generic Realtek drivers for the chipset
seem to work fine, by pointing to them in Device Manager. I'm pretty
disappointed in Netgear for being so crap.

ss.

On Fri, 17 Feb 2006 13:40:17 -0000, "Synapse Syndrome"
<(E-Mail Removed)> wrote:

>Thanks guys, I found out that the generic Realtek drivers for the chipset
>seem to work fine, by pointing to them in Device Manager. I'm pretty
>disappointed in Netgear for being so crap.

Such is often the case with "installers", which check OS
version. I'd always rather a plain old
bunch-of-files-in-folder that is browsed to. It also makes
the "driver" a much smaller size so it's easy to just keep
all drivers for everything on a thumbdrive, avoiding the
need to fool with floppies or CDs.