Q: Fool 2003 Drivers?

[ArtShapiro]

Probably a shot in the dark here, but why not?!

I have a Window Home Server box, a tiny Asus Mini TS machine. It's been a real pleasure over the years and the tiny Atom-based processor is extremely power-efficient.

The box only has a 10MB hard-wired LAN connection, which can be a bit of a nuisance the rare times I have to recover a machine image.

So I went out and purchased a Gigabit USB LAN adapter, a Startech product qualified for most Windows OSes including Server 2003. Windows Home Server is based on Server 2003, so I was hopeful that the device would work.

Unfortunately for me, it doesn't. The drivers aren't recognized by Windows Home Server and thus the request for manually installing appropriate drivers is displayed.

This machine really is Server 2003, and I'd guess some subtlety of machine identification is causing the failure to install those drivers.

By any miracle has anyone had need to fight a similar problem? The folks at Startech weren't able to help. I'd like to think I could diddle an INF file or the like to allow the adapter drivers to successfully load.

Art

 

[Fardringle]

What is the exact model number of the Startech adapter?

 

[imagoon]

Probably a shot in the dark here, but why not?!

I have a Window Home Server box, a tiny Asus Mini TS machine. It's been a real pleasure over the years and the tiny Atom-based processor is extremely power-efficient.

The box only has a 10MB hard-wired LAN connection, which can be a bit of a nuisance the rare times I have to recover a machine image.

So I went out and purchased a Gigabit USB LAN adapter, a Startech product qualified for most Windows OSes including Server 2003. Windows Home Server is based on Server 2003, so I was hopeful that the device would work.

Unfortunately for me, it doesn't. The drivers aren't recognized by Windows Home Server and thus the request for manually installing appropriate drivers is displayed.

This machine really is Server 2003, and I'd guess some subtlety of machine identification is causing the failure to install those drivers.

By any miracle has anyone had need to fight a similar problem? The folks at Startech weren't able to help. I'd like to think I could diddle an INF file or the like to allow the adapter drivers to successfully load.

Art

WHS v1 reports itself as 2003 server. You need to install the drivers, possibly using device manager rather than the installer.

 

[ArtShapiro]

What is the exact model number of the Startech adapter?

StarTech USB 2.0 to Gigabit Ethernet NIC Network Adapter (USB21000S2)

 

[ArtShapiro]

WHS v1 reports itself as 2003 server. You need to install the drivers, possibly using device manager rather than the installer.

My recollection (I'm at work right now) is that there was only an exe file, so I didn't have anything to which I could directly refer the device manager.

 

[imagoon]

My recollection (I'm at work right now) is that there was only an exe file, so I didn't have anything to which I could directly refer the device manager.

It is a zip file:

http://www.startech.com/Networking-...Ethernet-NIC-Network-Adapter~USB21000S2#dnlds

Driver is in the Windows folder.

 

[ArtShapiro]

It is a zip file:

Wow, thanks...I really think I had something different.

I'll try pointing the device manager at the 32bit folder and see what happens. (It's a 32 bit machine, so I cannot upgrade to WHS 2011.)

Art

 

[ArtShapiro]

Thanks to Imagoon, the gigabit drivers were successfully installed. It's backing up one of the laptops as we speak.

The only issue, right now, is that my main desktop computer is still picking up the old IP address, even after a FLUSHDNS operation. I suppose I can put an entry in the desktop's HOSTS file, or at least make a second wired connection to the old inbuilt NIC on the WHS box until I noodle out the issue.

UPDATE: after a half hour the main desktop started to recognize the new IP address, and similarly the WHS box suddenly realized that the desktop was online. We Are Happy!

Art