Why won't my NT Workstation 4.0 PC recognize its NIC?

Sukhoi

Elite Member
Dec 5, 1999
15,350
106
106
For the last few month's I've had a Linksys Ether16 ISA NIC in my 486 DX4-100 running Windows 95, and it's been working just fine. I use NetBEUI for file and printer sharing, and TCP/IP for internet access through my Win98SE ICS computer.

Yesterday I installed NT Workstation 4.0 as a dualboot. It shouldn't matter, but 95 and NT are both running off the FAT16 C: partition. I just can't get NT to recognize my NIC. I'm following the directions exactly as they are written in the little install book for the NIC. I install the adapter, leave the IRQ and memory address (I think that's what it is) on auto, give the NIC no network address, and install it. I also have TCP/IP and NetBEUI installed.

But when I reboot the computer to get all the changes to take effect, NT won't see the NIC. When I go into the event viewer, it says that it can't locate the NIC at the IRQ address. I loaded up my NIC's diagnostics utility, and it's running at IRQ 9. So I went into NT and set the NIC to be at IRQ 9, but it still won't get recognized. The NIC works just fine when I boot into 95. Any idea why it won't work in NT?

Also, I noticed that TCP/IP is actually installed as WINS (TCP/IP) or something similar to that. Why? :) Why isn't it just TCP/IP, and what does the WINS mean?

Thanks! :D
 

Sukhoi

Elite Member
Dec 5, 1999
15,350
106
106
Nevermind, did the usual changed nothing, came back 30 mins later, and everything now works fine. :)

But I'm still curious what WINS actually stands for, and is used for?
 

DnetMHZ

Diamond Member
Apr 10, 2001
9,826
1
81
WINS stands for Windows Internet Naming Service.. WINS is in some ways similar to DNS as it resolves
names to IP addresses (specificly NetBios names) it is also dynamic so DHCP clients are auto registered
as their IP's change.

hope that made sense, it's been a long day

DnetMHZ