NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
This is likely a "now you tell me!" post...
I randomly hovered over my WiFi icon in the Taskbar and noticed the Radio Type was stating 802.11n, not the AC I expected. Some searching around, a few netsh commands in DOS, all painted a differen...
Just thinking aloud here - could the problem be "does not report" rather than "does not support"?
To my way of thinking the OS would/should not determine the network function, although that might be a dictated by the source of the NIC drivers being used, as there may be native OS drivers, NIC manufacturer optimized drivers, and reference chipset drivers.
Windows doesn't care whether the network is ARCnet, token ring (remember those?), or whether your Ethernet connects at 10, 100, or 1000 mbps - why should it care if your WiFi is a, b, g, n or ac?
I will admit to having zero experience with 802.11ac, and also to still using 802.11g as my main wireless - I did the 802.11n thing when it first came out, the results were distinctly underwhelming, I do have an 802.11ac router, but no clients, and for me wireless is about convenience, as long as it connects, it's probably faster than my ADSL2 internet connection so why worry?
So to speak, in the interests of full disclosure, I was an early wireless adopter, having used it back in the days of 802.11 (that's right, no suffix), and my entire home is hard wired for Ethernet - I've just grown tired of the wildly exaggerated claims of increased throughput & coverage.
The simple facts are that the advertised throughput is purely theoretical and cannot be achieved in practice, and if the promised coverage was actually available, there would be no need for the wide array of extenders that currently flood the market.
To my way of thinking the OS would/should not determine the network function, although that might be a dictated by the source of the NIC drivers being used, as there may be native OS drivers, NIC manufacturer optimized drivers, and reference chipset drivers.
Windows doesn't care whether the network is ARCnet, token ring (remember those?), or whether your Ethernet connects at 10, 100, or 1000 mbps - why should it care if your WiFi is a, b, g, n or ac?
I will admit to having zero experience with 802.11ac, and also to still using 802.11g as my main wireless - I did the 802.11n thing when it first came out, the results were distinctly underwhelming, I do have an 802.11ac router, but no clients, and for me wireless is about convenience, as long as it connects, it's probably faster than my ADSL2 internet connection so why worry?
So to speak, in the interests of full disclosure, I was an early wireless adopter, having used it back in the days of 802.11 (that's right, no suffix), and my entire home is hard wired for Ethernet - I've just grown tired of the wildly exaggerated claims of increased throughput & coverage.
The simple facts are that the advertised throughput is purely theoretical and cannot be achieved in practice, and if the promised coverage was actually available, there would be no need for the wide array of extenders that currently flood the market.