Interesting discovery...PCI wireless does not work without sound!

[wahnula]

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...

 

[vacunita]

Probably because that PCI device was your wireless card or a component of it. Sound cards would not be recognized as a PCI device. Rather a multimedia device or something different.

PCI almost always suggest some type of connectivity. Either modem, network card or in your case Wireless card.

At least that's been my experience.

----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

 

[wahnula]

Well, running the HD Audio install package from BioStar restored connectivity. I tried running the "Update Driver" on the "!" PCI Device against both the D-Link CD and the BioStar CD, it was only AFTER I installed the missing HD Audio through the M/B's CD installer that connectivity returned. Upon reflection, maybe some elements of the chipset drivers did not install correctly when I first ran the setup package. There was no "Audio Device" in Device Manager at the time. I agree it makes no sense, but the NIC's drivers were all well installed. Go figure.

Tony

Users helping Users...

 

[wahnula]

Answer: it was coincidental. Connectivity is gone again, no exclamation points, deeper problems are assumed.

Tony

Users helping Users...

 

[ATLMatt]

Depending on OS, you may have resource conflicts with the new device.

Additionally, try getting the drivers installed properly but not using the D-Link software package, just let the OS handle the wireless connection and see how that works. In XPPro and Vista machines, I continually have major issues with software that comes with wireless nics/routers, or comes pre-installed on name brand laptops, until I get rid of it and let the OS handle the connection.

 

[wahnula]

try getting the drivers installed properly but not using the D-Link software package, just let the OS handle the wireless connection

No can do, Win2K has no native wireless support. I agree it's best to let XP/Vista handle the wireless NIC, but that's just not possible here.

I turned the machine on this morning, everything worked fine, 10 minutes later no go.

Event Viewer had several "warning" errors, all related to DNS or DHCP. Event 1006 and 1003 from source DHCP, Event 11050 from DNSCache, Event 11180 from DNSApi, Event 35 from WinMgmt, this all indicates a DNS conflict.

Being a client of an SBS Network, DNS Server address in the NIC's TCP/IP Properties needs to point to the SBS box, 192.168.16.2. It passes through a WAP 192.168.16.10, when it's working I can ping the WAP and the SBS box.

I tried uninstalling/reinstalling TCP/IP, rebuilding the stack, no joy. I tried reloading all the chipset drivers and the NIC drivers, nothing. CPU temp is fine.

The D-Link utility shows a strong connection to the WAP, but I can't ping it!

I am resolved to believe either it's a dodgy M/B or a conflict with the modern chipset/CPU's handling of the older Win2K OS & D-Link card. Since I've had zero problems with the built-in wired NIC, I'm using that patch cable I ordered yesterday to string it up, I have no patience for an intermittent part!

Any other ideas are welcomed...

Tony

Users helping Users...

 

[ATLMatt]

My mistake, totally missed the Win2k part there. Blowing away the stack was the next thought, you did that.

Other than that, it might be worth checking to see if the soundcard/wired nic/wireless nic are trying to use any of the same resources, if they are though you should get a "!" and a "resource conflict" message under troubleshooting in the device manager, but it might be worth checking the resources tab just to be sure.

Is the BIOS up to date on the board?

 

[wahnula]

ATLMatt,

I am a little ahead of you, I tried disabling EVERYTHING in the BIOS that I could (serial, parallel, audio,LAN), in an attempt to free up resources. Device Mangler is squeaky clean, no apparent conflicts. My BIOS is current and dated 12/07, so it's pretty recent.

I'm looking out the window for UPS, they should be here with my patch cable soon. It's an easy string, just through one wall into the next office.

Still, it bugs me that I can't figure this out, but I can't be wasting too much time on a $150 PC. As a bonus, it will now make use of the gigabit NIC, it's the boss's PC and he will be happy with that.

Thanks for pitching in with your ideas.

Tony

Users helping Users...