Novell logon, NIC device drivers

[PaulS]

Reinstalled WIN95 on customers workstation, reinstalled Client32. Re-boot of WS did not pick up installed NIC, installed thru Add New Hardware, device had &quot;!&quot; next to it in Control Panel - System - Devices. Ran driver update, no change. Re-booting WS, Client32 logo shows for about 1 second, then Windows login window appears. Cabling is OK, LED on NIC is on, LED on network hub is on. Appears WIN95 is not accepting NIC driver. It's a 3Com FastLink 3905TX-B (?) card.<br>
Any ideas?

 

[mgtjr]

From our experience the NIC card has to be remove from network and system in control panel and then reboot. The machine should find the card. Then you should set it up for your clients and protocols.

 

[grubb]

mgtjr's tip has worked for me, but I've also found that sometimes the only way to get Win95 (especially &quot;b&quot to accept that particular card is to boot into &quot;safe mode&quot;, remove the NIC there from Device Manager (sometimes you'll see the NIC is listed 2x in safe mode), then reboot and install the drivers. There's something about that particular card and Win95 that just doesn't jell - and no good solution from 3Com or MS. Once you get it working, it will keep working, though.

 

[J]

Check irq settings in device manager for NIC...

 

[unit512]

Finally...check in device manager and see if there<br>
is an Other. If other has a PCI Ethernet Card<br>
remove it.

 

[KennyG]

Had this problem a lot. Be sure the NIC isn't in one<br>
of the slots closest to the power supply. On later <br>
pc's with bus mastering, the OS won't see the nic or<br>
sees it weirdly. Move it to another slot away from<br>
the power supply. Sometimes there are two slots with<br>
bus mastering, also check CMOS for bus mastering turned<br>
off.