Brand New AE1000 Periodically Stops Functioning [ Edited ]

[jminiman]

I'm running Windows 7 64-bit with the very latest AE1000 driver (3.0.10.0).  I have a Netgear WNDR3700 with dual band support.  I replaced a D-Link DWA-556 PCIe 2.4 GHz card with this USB unit because I was seeing interference with my keyboard and mouse (Logitech Bluetooth).  When the AE1000 works, I can consistently connect at 300 Mbps and the speed is great.

Unfortunately, every so often, the connection to the internet drops and Windows 7 must do a wireless adapter reset in order to regain access to my network.  During this time no other machines connected on the wireless network report any disruption and neither the 2.4 GHz or 5 GHz WiFi profiles are connectable with the AE1000.

I've tried switching from the built-in USB 2.0 ports on my motherboard to the USB 3.0 daughtercard to no avail.  I've tried uninstalling and reinstalling the driver.  However, I started seeing this issue literally the day I installed this thing.  The problem happens sometimes a few instances in an hour but then won't happen again for another few hours.

In Event Viewer, I'm pretty consistently seeing:

The TCP/IP NetBIOS Helper service was successfully sent a stop control.

 The reason specified was: 0x40030011 [Operating System: Network Connectivity (Planned)]

What's going on here?

[saber_tooth]

Did you try to uninstall and reinstall the drivers for AE1000 on the computer ?

If not, then try to reinstall the drivers for AE1000 on the computer and then check.

[jminiman]

Yes, I did try that earlier on.  Is something unique to the Cisco drivers where they get corrupted versus "normal" WHQL network drivers?  Other suggestions?

[saber_tooth]

I don't think that the driver is corrupted because you are able to see the network name but as you are getting disconnected to often it is recommended to update the drivers for the adapter. Also try changing different wireless channels and some of the advanced settings on the router and then check.

[jminiman]

I've tried all of the above.  And switching from the 5 GHz band to 2.4 GHz band doesn't fix the problem.  Something is going on with the card.  Does anyone from Cisco monitor this forum?

[saber_tooth]

Just try to use the AE1000 adapter on a different computer and then try to connect to the network through that computer.

[Kado]

I have recently added a review to CNET regarding this issue. Maybe it will help.

I have the Cisco Linksys E3000 router and this Cisco Linksys AE1000 wireless adapter; the two of them work great together. I do have to say I expected to get a little better signal from the two but it is enough to suffice. The unit comes with a stand so you can leave it plugged in and maneuverable for a better range, or you can simply unplug it (it is a simple thumb drive) and plug it straight in to your tower if you prefer. It is very chic and hardly noticeable and small enough you may be able to jack it into an internal USB card (not sure how the reception would be). Overall I have found the software (Cisco Connect) incredibly easy to manage at any technical skill level.

The unit’s drivers like many other devices, bugs out when used with windows 7 Home Premium 64 bit. Windows after about three days run time will just up and no longer recognize the device or driver. This is a pain because you then have to go into device manager uninstall the device and reinstall everything from scratch, if you haven't saved a copy of the drivers to an alternate location. However I have just got finished with Cisco chat support and they have provided the method to fix this situation or so I would hope. I have just completed the steps and will maintain a close eye to ensure that it does indeed work. I have added those steps below in the summary to help any others that may come across the same problem as I did.

from Benoy (70509) to All Participants: "Hi, my name is "Benoy (70509)". How may I help you?"

I then explained the situation that I explained above I will now list the steps in order as she described to fix the problem.

from Benoy

  http://homedownloads.cisco.com/downloads/driver/1224657257709/AE1000_Win7_3.0.10.0-WHQL.zip

Click on this link and save it

Then open the folder that you downloaded it to and unzip it.

Now go to device manager by right clicking My Computer select properties and then device manger.

Find the network Adapters and open it.

Right click the AE1000 device and select update drivers.

Browse to the folder containing the Unzipped folder there will be a 32bit and a 64bit folder choose the appropriate one and select ok.

If you have an E3000 router continue. Go to the computer that is hardwired to your router and click and save this link http://homedownloads.cisco.com/downloads/firmware/1224655340609/FW_E3000_1.0.04.006_US_20101206_code... Open the Cisco Connect software. Click on router settings, advanced settings, click ok, you should now be in the linksys interface. Once there click the administrator tab, go to the firmware upgrade subtab, then browse to the file you last downloaded and click start to upgrade. You may also consider changing the channel of the 2.4 mghz setting to help further prevent future problems if any are incurred.

Hope this may help some of those that have had the same issue as I have.

[worx]

Is your AE1000 recognized when you wake up your computer from sleep/standby mode? I am using the latest drivers from cisco and I am having this issue where my adapter isn't recognized when I wake up my computer from sleep mode.

[jminiman]

After a year with the AE1000 and the same March 2010 drivers, I still get periodic disconnects (the wireless networks disappear) after a standby resume.

I can't believe Cisco never figured out a fix for this.  Annoying as heck.  I've gotten accustomed to unplugging/plugging in the USB whenever I resume and I get disconnected.

Poor quality!

[clu801]

I have also had this problem going on 6 months.. spent all this money on a E2000 router and dropped more money on this AE1000 adapter that will never properly work after booting computer up from standby.

(Mod note: Edited for guideline compliance.)