[SOLVED] Linksys AE1000 plugged in and recognized but not available

[Valiant]

I have a Cisco AE1000 USB wireless adapter and up until I reinstalled Windows 7 it worked flawlessly. Now I plug it in and the computer recognizes it and finds the correct driver for it but it never shows up as a network adapter. Right now I am using the Intel a/b/g wifi adapter that is built in to my laptop. My drivers are correct. I've tried uninstalling it from device manager, restarting and letting it find it and it still doesn't work.

Here is the pertinent information:

ISP: Comcast
Router:ASUS RT-N56U
Modem: Motorola SB5101U
Anti Virus/Firewall: ESET Smart Security 5.0.94.0


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : S9312
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
Physical Address. . . . . . . . . : 00-16-36-F3-8B-07
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Con
nection
Physical Address. . . . . . . . . : 00-13-02-CA-8E-C5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ad73:3f4c:9905:2fd%21(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, December 12, 2011 8:48:08 AM
Lease Expires . . . . . . . . . . : Tuesday, December 13, 2011 8:48:07 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 352326402
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-6A-DE-41-00-16-36-F3-8B-07

DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{45EB59CF-156A-47FB-8246-937915A8AE6A}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{4C827C41-16FB-44A0-9CD7-104CE6983960}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:30d9:19da:9d0a:9da5(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::30d9:19da:9d0a:9da5%16(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

[2xg]

Hi Valiant,

Did you download and install the latest driver for your USB adapter from the manufacturer's site?

[Valiant]

Yes. When I noticed the problem, I uninstalled the first set of drivers and reinstalled a fresh download from Cisco/Linksys' site. It didn't help. The adapter shows up properly in device manager but it doesn't show up at all under my network adapters. I have 2 other types of usb wireless adapter and they don't work either.

[2xg]

Try uninstalling the device driver from Safe Mode by restarting your computer tap F8 then select this option. Disable Eset completely before uninstalling/reinstalling the updated driver.

[Valiant]

That solved the problem, but now ESET is reporting an ARP Cache Poisoning attack coming from 192.168.1.8 and a DDOS attack from 192.168.1.1
I know its a false alarm on both but it didn't do it when I was using my built in wireless g adapter.

[Valiant]

Oh thank you btw!

[2xg]

You should be okay. Enable Eset then try disabling the Firewall side only, leave your Windows Firewall enabled.

[Valiant]

I'll probably just go back to ESET 4.x instead of 5.x I don't like the interface changes anyway. Thank you for your help. Feel free to close this thread whenever.

[2xg]

You're quite Welcome.

This Thread is now mark Solved.