I received a new machine last week with W2K and the above card. On connecting it to our network (WinNT server with mix of 95/98/Nt/2000 machines) there was some very slow response in Network Neighbourhood but (some) other machines could be seen. The installed driver was a Realtek one. Suspecting a possible driver issue I tried several driver versions from the net to see if things would improve. I have ended up back with the original driver (although the description in device manager now includes "#2") but no machine sees mine and I can't see others. I can't ping anything else on the network but 127.0.0.1 seems okay. A second cable has been tried without success. The properties box shows packets being sent, but none received. I am suspicious of the #2 on the driver description. Also, when I uninstall this driver, it appears to uninstall but on re-boot there is no "new hardware found" and the device is still listed under network in device manager. Has anyone come across similar problems and is there a way of removing the device via the registry? Any other suggestions?

Came across this problem yesterday - literally. Sadly, the only solution was to reinstall. As a test, you could try this: Install NetBeui on this machine and one other. See if files get transferred normally. If they do, then you know that it's not the netwkr, and not the card or driver. It the IP stack. I'm sure there's a way to force the system to prompt you for the CD, instead of just pulling the IP dll's from the stored files, I'm just not sure what it is. The problem, most likely, is the files are corrupted, and when the system re-installs the stack, it's a bad load, so IP doesn't work. One thing you could also try, but don't hold out too much hope: Boot the system into whatever safe mode it offers, remove every occurrence of the NIC, then remove TCP/IP from the network settings. Reboot. It should file the NIC again, and reinstall the files. This MIGHT work, but again, don't hold out too much hope for it. HTH, Chase

The solution to my problems were two fold: 1. The problem of not seeing anything on the network turned out to be nothing to do with the hardware / software. Instead it depended on where the machine was physically connected onto the network. 2. Couldn't remove the "#2" driver. Re-installed Windows instead.