Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[DsurioN]

I'm thinking there might be an incompatibility with the motherboard - three of us so far in this thread (that includes me) have a P55-based motherboard, and since these are relatively recent, D-Link may not have tested the drivers with these mobos.  I just spent a while with Level 3 technical support at D-Link and they didn't have any idea what the problem could be.  They said the drivers should technically support 64-bit Windows 7, but that it's possible my motherboard is incompatible.  I think I'm just going to return this card and get one that isn't based on the Atheros AR5008 chipset. 

[tgillis]

I've got a P55 as well, mine boots just fine, no issues there, but I loose connectivity all together after a period of time using a secured network.

[cklaubur]

I just bought a DWA-552, and have a freezing issue under Windows 7 Professional 64-bit. Same as others have mentioned (freezes at login, even freezes during Windows installation as long as the card is in the computer), but the only difference from the last few posters is that my motherboard uses a P45 chipset (Gigabyte EP45-UD3LR).

Casey

[thecreator]

I just bought a DWA-552, and have a freezing issue under Windows 7 Professional 64-bit. Same as others have mentioned (freezes at login, even freezes during Windows installation as long as the card is in the computer), but the only difference from the last few posters is that my motherboard uses a P45 chipset (Gigabyte EP45-UD3LR).

Casey

Hi Casey,

Try this: Go into Computer Bios, and disable the Onboard Gigabyte Ethernet port. Before you do, uninstall the software for the Ethernet Port.

Also, make sure that you are only installing the Drivers and not the D-Link Utility for the DWA-552 card.

[cklaubur]

Disabling the onboard LAN did do some good, but still unacceptable performance. With the onboard LAN disabled, the computer would boot into Windows and install the correct driver for the card, but when I attempted to connect to my wireless network, the card would detect the network, but once my security code was entered, the card would fail to connect. It did connect once, but locked the computer up as soon as I tried to visit a web site (www.speedtest.net). Any other time, Windows would say "Windows could not connect to this network".

Casey

[thecreator]

Disabling the onboard LAN did do some good, but still unacceptable performance. With the onboard LAN disabled, the computer would boot into Windows and install the correct driver for the card, but when I attempted to connect to my wireless network, the card would detect the network, but once my security code was entered, the card would fail to connect. It did connect once, but locked the computer up as soon as I tried to visit a web site (www.speedtest.net). Any other time, Windows would say "Windows could not connect to this network".

Casey

Hi Casey,

You need to reboot the computer, once entering the Security Code for the Windows Wireless Network Manager. It does not work, if you don't reboot.

[cklaubur]

I did reboot, but it still didn't work.

Casey

[thecreator]

I did reboot, but it still didn't work.

Casey

Hi Casey,

Now responding from Windows 7 Ultimate 32-Bit Release Candidate Version.

Open Network and Sharing Center

Click on Wireless Network Connection
Click Wireless Properties.
Make sure that the first and last of 3 choices are checked.
Click the Security Tab.
Check the Network Security Key. Check Show Characters to make sure the Security Key is correct that you entered and once confirmed, remove the checkmark from Show Characters.

[cklaubur]

The card locks the entire computer up when it does finally find and connects to the wireless network! It's not a problem with the network configuration!

It's not my problem anymore, though. That card's gone.

Casey

[sssg]

My board is P6T.
I downloaded the driver release 1.6 from another computer to a usb.
My system freezes after accessing Internet.
Before opening IE i installed the release 1.60 from usb.
The problem disappeard.

[tgillis]

I did the same thing (though using a wired connection) and I get more time, but it still dies after a while (usually measured in days now).  Root cause to me is still drivers.

[sssg]

Actually i run the setup program in the directory setup of driver 1.60.
Then the problem is disappeared.
My OS is XP sp3.