NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
netgearA7000 nighthawk AC1900 WiFi USB Adapter - USB 3.0 - can't connect to this network
trouble shooting steps confirm that wifi network & access points lists the 5g & 2g SSIDs. List of visible access point(s) List of visible networks: neither 2G nor 5G connect and get the sam...
michaelkenward thanks for checking. yes it's windows & yes it showed on device manager. not sure if you got a chance to review the troubleshooting log that lists the wifi network & access points. in any case, rebooting the router and re-attmepitng to connect worked a-ok. thanks again for taking the time to review & respond.
yes, michaelkenward
done the trouble shooting no luck.
even after setting the preferred network it says 'can't connec to this network' on wifi interface on windows 10.
-----
Network Adapter Publisher details
Issues found
You have no preferred wireless networksYou have no preferred wireless networks
When you select a network and connect, Windows can automatically connect to it in the future. Not fixed Not Fixed
Connect to an available wireless network Completed
Diagnostics Information (Network Adapter)
Details about network adapter diagnosis:
Network adapter Wi-Fi 2 driver information:
Description . . . . . . . . . . : NETGEAR A7000 WiFi USB3.0 Adapter
Manufacturer . . . . . . . . . : NETGEAR Inc.
Provider . . . . . . . . . . . : NETGEAR Inc.
Version . . . . . . . . . . . : 1030.25.701.2017
Inf File Name . . . . . . . . . : C:\WINDOWS\INF\oem78.inf
Inf File Date . . . . . . . . . : Sunday, December 5, 2021 4:39:38 PM
Section Name . . . . . . . . . : RTL8814au.ndi
Hardware ID . . . . . . . . . . : usb\vid_0846&pid_9054
Instance Status Flags . . . . . : 0x180600a
Device Manager Status Code . . : 0
IfType . . . . . . . . . . . . : 71
Physical Media Type . . . . . . : 9
InformationalDiagnostics Information (Wireless Connectivity)
Details about wireless connectivity diagnosis:
Information for connection being diagnosed
Interface GUID: <string of alpha numerics>
Interface name: NETGEAR A7000 WiFi USB3.0 Adapter
Interface type: Native Wi-Fi
Connection incident diagnosed
Auto Configuration ID: 1
List of visible access point(s): 56 item(s) total, 56 item(s) displayed
BSSID BSS Type PHY Signal(dB) Chnl/freq SSID
-------------------------------------------------------------------------
<string of alpha numerics> Infra <unknown> -50 10 A24
<string of alpha numerics> Infra <unknown> -50 5805000 A5G
Connection History
Information for Auto Configuration ID 1
List of visible networks: 28 item(s) total, 28 item(s) displayed
BSS Type PHY Security Signal(RSSI) Compatible SSID
------------------------------------------------------------------------------
Infra <unknown> Yes 56 Yes ASH24
Infra <unknown> Yes 96 Yes ASH5G
List of preferred networks: 0 item(s)
InformationalNetwork Diagnostics Log
File Name: 2F686F89-4FF3-44FB-AA06-7084B71209E0.Diagnose.0.etl
InformationalOther Networking Configuration and Logs
File Name: NetworkConfiguration.cab
Collection information
Computer Name:
Windows Version: 10.0
Architecture: x64
Time: Tuesday, December 7, 2021 4:36:14 PM
Publisher details
Like I said, it isn't easy to follow your first message with its "telegram" writing style.
Take the first "sentence":
trouble shooting steps confirm that wifi network & access points lists the 5g & 2g SSIDs.
What does that mean?
What is this "wifi network" what are these "access points".
Do other wifi clients play nicely with the local wifi?
It sure sounds like a Windows thing.
Does the adapter work on a different device?
Have you looked at this thing in Device Manager?
michaelkenward thanks for checking. yes it's windows & yes it showed on device manager. not sure if you got a chance to review the troubleshooting log that lists the wifi network & access points. in any case, rebooting the router and re-attmepitng to connect worked a-ok. thanks again for taking the time to review & respond.
nguser9 wrote:
in any case, rebooting the router and re-attmepitng to connect worked a-ok.
That's good. An easy one for a change.
It is all too easy to get sucked into complicated troubleshooting. First try the simple things.
nguser9 wrote:
not sure if you got a chance to review the troubleshooting log that lists the wifi network & access points.
You probably need a degree in network engineering to understand that stuff.