Hello folks,
I was quite frustrated earlier today, a new build (Biostar el cheapo,Core Duo, SATA, Win2K) would NOT connect to my SBS2003 network no matter what. I use D-Link GL520 wireless network cards, and had it configured for security, the D-Link utility showed "connected" but I could ping nothing, not even the D-Link WAP. Onboard NIC works fine, but I like the freedom of wireless.
I swapped WiFi cards, unistalled/reinstalled D-Link utility, finally gave up and ordered a patch cable. There was a yellow exclamation point under "unknown PCI device", I figured it was the audio that would not install from the chipset CD before I ran WSUS, it needed Win2K SP4, I blew it off because this is an office PC and has no speakers.
I tried updating the device with the chipset CD in the tray, nothing. Finally re-ran the chipset install CD, lo and behold the network connection magically appeared! I have no idea why this happened, but I wanted to put it out there for anyone who might run into this same issue.
A reason WHY it happened might be nice too...
Tony
Users helping Users...
I was quite frustrated earlier today, a new build (Biostar el cheapo,Core Duo, SATA, Win2K) would NOT connect to my SBS2003 network no matter what. I use D-Link GL520 wireless network cards, and had it configured for security, the D-Link utility showed "connected" but I could ping nothing, not even the D-Link WAP. Onboard NIC works fine, but I like the freedom of wireless.
I swapped WiFi cards, unistalled/reinstalled D-Link utility, finally gave up and ordered a patch cable. There was a yellow exclamation point under "unknown PCI device", I figured it was the audio that would not install from the chipset CD before I ran WSUS, it needed Win2K SP4, I blew it off because this is an office PC and has no speakers.
I tried updating the device with the chipset CD in the tray, nothing. Finally re-ran the chipset install CD, lo and behold the network connection magically appeared! I have no idea why this happened, but I wanted to put it out there for anyone who might run into this same issue.
A reason WHY it happened might be nice too...
Tony
Users helping Users...