Windows 10: regulatory domain limiting channels/frequencies

inspirion 15-7559
intel wireless-ac 9260 and also happens with intel wireless-ac 8265
region: US
the linux info mentioned below is for a better explanation of whats happening on windows on the same machine, behavior is identical and only begain after the latest big windows update. getting equivalent outputs from a windows terminal has proven next to impossible as im unaware and unable to find any tool capable of displaying it.

the problem that seemingly nobody knows about and causes problems with wifi and available channels quite often seems unsolvable after a month of trying every possible thing i can think of. the problem began after a windows 10 update about 1-2 months ago.

before this windows update i had no problems connecting to channel [email protected] from both windows 10 and from arch linux, after this update not only could windows not see any 5ghz channel other than [email protected] (barely usable, max of 7mbps instead of 360mbps it usually is) but this also seems to effected the way linux is determining available frequencies and is limited to only channel [email protected] just like windows and happened after a windows update. fast boot is not enabled and there is no reason for this yet it happened.

on the linux side of things the fix was simple using the included module option `lar_disable=1` of the intel driver `iwlwifi`, that module option disables LAR ("Location Aware Regulatory") and all is good in the linux world with wifi again.

to simplify the question im trying to ask, a way of accomplishing any 1 of the following questions would be greatly appreciated.

1. is it possible to disable the LAR function of the windows 10 intel wireless driver? (there are no readily available region/regdom settings, none of the power management or forcing of 5ghz methods make any difference)

2. a way to force windows to stop limiting the wifi channels that for some reason are being blocked, or even an explanation of how windows manages this?, there is no documentation im able to find from both windows and from intel that explain how they manage it.

3. is there a registry entry that would even tell me what regulatory domain is actually being detected/used? (both intel and microsoft have not been able to answer this, or rather they just wont answer it)

addition info and links to intel/microsoft unresolved help requests on the same subject.
microsoft technet, including a list of everything i've tried
https://social.technet.microsoft.com...tpronetworking

intel support, again providing blanket statements and providing nothing of value
Forums

channels/frequencies i was able to use previously and should still be able to use on windows and linux. both commands are from linux and show whats happening in regards to location aware regulatory.

#this is with lar_disable=Y or lar_disable=1 (same thing)
#everything works perfectly

~ >>> iw reg get [234]
global
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 71000 @ 2160), (N/A, 40), (N/A)

the above is from a perfectly working wifi by passing `lar_disable=1` to the iwlwifi module to disable LAR. note the region is set correctly. below is from a boot not using the module option to disable LAR, note the extra portion "DFS UNSET" , the regulatory domain is detected properly but then DFS UNSET disables the channels it should not be disabling resulting in identical behavior as windows where only ch. [email protected] is able to be used.

#this is without lar_disable=Y and i cant use anything other than
#20 for channel width which results in no 5ghz ac ability and terrible speed
~ >>> iw reg get
global
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 71000 @ 2160), (N/A, 40), (N/A)

phy#0 (self-managed)
country ID: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5735 - 5815 @ 20), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ


thanks for reading, any help would be greatly appreciated.

:)

 

Windows 10 and 802.11d (change in Wi-Fi regulatory domains)

Hi community,

I am traveling from Europe to US for a business trip. I work as a wireless engineer and I need to test customer Wi-Fi but I am unable to use UNII-3 channels with my laptop (Lenovo with wNIC Intel 8265). Intel datasheet for the chipset 8265 specify it can
work on all the domains (UNII-3 channels from 149 to 161 included) but I am unable to connect.

In Linux, there is a command to change the regulatory domain of the wNIC (iw reg set US) but I cannot found any feature to do that on Windows, nor the vendor driver.

On wireless networks, there is a standard known as 802.11d to inform the connected devices about the regulatory domain configured in the WLAN, for them to change the supported channels (in the case of US, avoid the use of 120 to 128, and allow the use of
149 to 161).

The result is that I cannot test the connectivity of part of outdoor network of the customer because I am not able to see the SSID on those channels. Is Windows 10 802.11d capable? Is there any way to change it as laptops sold in US can do it?

Regards.

Jesus

 

Local Channel change of frequency

As of Today several of my local channels have announced the FTC is requiring them to change frequencies. When I turned on my TV it did not tune in those channels. I went into my TV setup and rescanned the channels and now on my TV they are working Fine.
In media center I went back into TV setup and set up my TV again but it did not correct any of the channels altered their broadcast frequency. I just get "No Signal" when I try to tune them in using Windows Media Center in Window 7

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW