5g Wifi Adapter Pc

4 views
Skip to first unread message

Gwenda Gronert

unread,
Jul 25, 2024, 11:36:27 PM7/25/24
to simavr

When the user connects to their network at home, they are unable to connect to VPN, and it seems like the issues is caused by GlobalProtect setting the WiFi adapter's DNS-address to that of the VPN proxy DNS.

its a horrible design and have reported it multiple times. Once I figured it out that it was that setting, I disabled it and never used it again. I flush the DNS using a script on connect now, doing Palo Alto's job.

Never should a VPN client ever ever ever change settings on any adapter other than their own. No other VPN client does for a good reason. This was presumably their band aid fix for "DNS queries" to make sure both adapters use the same DNS. sorry, but that is not how it works and horrible software programming when others do not have to do that. Also, who would have thought that setting Flush DNS would change DNS settings on the wifi adapter? seriously? Palo Alto TAC told me to set the registry key and never told me it would do that for the network adapter, since I wanted the DNS to be flushed like any other VPN client does properly. Self inflicted painful months. By the way, it is not just the wifi adapter, it will do it for the ethernet adapter as well, but most people use wifi anyhow.

also be prepared to have to uninstall the GlobalProtect client and reinstall it, to clear out that bad setting. that was unfortunately my fix for the issue, because even though if it was disabled, it somehow was still cached and continued to do it until I uninstalled it and reinstalled.

I've tried literally everything for this $80 wifi adapter that I bought. It has very fast wifi speed but it just has one problem.. it disconnects every 5 minutes. Perhaps even less than 5 minutes most times. I just can't take it anymore and I cannot take it back to the store, as it is well past the return date. If you have one of these do you know what to do to fix it? I read a youtube comment about someone using a generic microsoft driver but after trying for several hours I could not find the one he was talking about. And every one that I tried failed to work after installation.

I had the same issue with the A7000 continually disconnecting every few minutes. I unclicked the power saver function in the adapter properties area and it appears to have fixed the issue. Thanks for the help!

I wanted to share a solution to a reoccuring problem with my A6210 Wifi Adapter that seemed to be causing a problem for a lot of other people as well. Many of the threads on this support community offered solutions that worked for some, but none of them worked for me. I was almost at the point where I was going to junk my A6210, and find a different WiFi adapter.

The problem I was having was that the adapter would intermittently disconnect. At first it only happened once or twice a week, then as time went on at least once a day. About a week ago, the problem became so severe that my adapter was disconnecting continuously. It would stay connected only for a few seconds before disconnecting, then reconnecting, failing, and so forth in an unbreaking cycle.

The problem for me was that this solution didn't work at all. I updated my Netgear router's firmware, And I also updated the latest drivers for the A6210 adapter. But nothing worked. The third recommendation on that link ("Try disabling the Minimum Power consumption feature on the adapter") didn't apply, because that option did NOT appear under the Adapter Properties list.

After exhausting the Netgear forums and other sites, I couldn't figure out what else to do. But it occurred to me that the problem might be related to the USB connection. My A6210 is connected to a USB 3.0 port, and the sound that the OS would make each time the adapter lost the WiFi connection was similar to a USB being removed.

SOLUTION: Based on the above clue, I followed the instructions for the third option mentioned earlier, with one critical difference: I changed the Max USB Speed value from "USB Auto" to "USB 3.0" This INSTANTLY fixed the problem. The adapter immediately found the Wifi signal, and the neverending "connect / disconnect" cycle went away. If you are using the A6210 Adapter on a USB 3.0 port, and experiencing this problem, I would give this a try.

I suspect what was happening was that the A6210 and the operating system were not agreeing on which USB speed to use. The adapter was set to auto-adjust to the proper USB connection, and Win10 was similarly trying to negotiate with the device. However, for some reason they got caught in a logical loop wherer neither the OS nor the adapter could actually agree -- hence the inability for the adapter to stay mounted for more than a second or two. .I'm speculating here, but this is the only solution I've found to this problem.

I hope this helps some poor soul that was as stuck as I was with this problem. I'll update this post if the problem reemerges, but hoping that this fixes the problem permanently. I would encourage Netgear to consider adding this solution to your support page for this problem: -A6210-WNDA3100v2-wireless-adapter-intermittently-disconnects

Wenesday, June 5th, 2024 -- Possible solution

I've been dealing with this issue for a couple of days and I think I've found a couple of ways to fix it. I haven't had any disconnections in the past few days since I tried these solutions.

1. Press the Windows key and type "Services".
2. Right-click on "Services" and select "Run as administrator".
3. In the Services window, scroll or press 'n' on your keyboard to find "NetgearSwitchUSB".
4. Right-click on "NetgearSwitchUSB" and select "Properties".
5. In the "General" tab, find "Startup type" in the dropdown menu and select "Disabled".
6. Click "Apply" and then "OK".

Whenever I use my computer for the day, I turn it on and connect it with the Netgear Genei software.
Once it's connected, I restart my computer and it doesn't disconnect for the whole day.
I hope these steps help fix the issue for everyone.

I dual booted Ubuntu 17.10 in my windows 10.While working in windows wifi works fine! But in Ubuntu it is always showing "No wifi adapter found, Make sure you have a wifi adapter plugged and turned on"Not getting any solutions online! Tried some of them but not working! Help please

I bought an A6150 WiFi adapter to connect my Windows 11 PC to a 5GHz WiFi network. I went through the recommended install procedure and everything was configured and working for a week or so. The street had a power failure while the PC was running, and after that, it could not see or connect to any 5GHz networks. Other devices in the house and the same adapter in a Windows 10 PC had no trouble, so it was related to the Windows 11 system.

I started a support request but they were no help and after two weeks of online exchanges, I phoned the local NETGEAR office. They were worse and told me that the problem was clearly down to Microsoft and I should call them. I didn't do that.

This will disconnect your 2.4MHz connection and reconnect on 5GHz. I already had a stored password from when it was working initially, so my connection was automagic and I didn't have to re-enter the network key.

The backports kernel is the next version of Debian's kernel. The backports kernel in OMV 4.x is the Debian Buster kernel which has stabilized on 4.19. So, OMV 4.x will probably never get a newer kernel than 4.19.

Probably true but I must insist on using a wireless NIC. I did a bit more research and only the 2 Edimax and Asus PCE-AC55BT card support Linux. For Asus PCE-AC55BT (and the B1 version) it's unclear which version of LInux it supports. I suspect Edimax has mediocre quality at best. Maybe I need to look into those Alhpa cards.
It would be very helpful if there would be a "supported wifi NICS" list for OMV.

Normally we try to talk people out of using wireless for a NAS. Since OMV is meant to be run headless, most users should be able to put the NAS near a place where it can be wired. But OMV is Debian which means it supports whatever Debian supports. Here is Debian's supported wifi adapter page -

Thanks for your comments so far. Unfortunately, the Debian wifi compatibility list isn't much help. It's mostly chipsets and the mentioned models are either really old or not availlable. I wish I could just use a ethernet cable but this is simply not an option. I noticed that there are some good adapters that have unofficial ways of making it work but only from a higher kernel version. So I'm still left in the dust here :/. All I need is one good wifi adapter. The hardware interface doesn't matter (m.2 (key E), PCI-E, USB).

1. A WiFi Range Extender with an Ethernet port.
2. Power line adapters.
3. A wireless router used as a "media bridge". (Do you have an extra wireless router laying around?)
Since all consumer routers don't support wireless bridging, this can a tricky option. While routers will layer, one behind the other, running two separate IP networks won't work. You'd need to "bridge" your server into the same IP network with your clients, to have access to network shares.
4. Wireless Routers using a "Mesh" topology. This can be expensive and you'd have to co-locate one router were you could run an Ethernet cable to a hard wired port. Certain models of Asus Router support what they call AI-Mesh (scroll to the bottom). These ASUS models, if bought used or refurb'ed, can be had for reasonable prices but two would be needed.

Reply all
Reply to author
Forward
0 new messages