Jump to content

Recommended Posts

Posted

To complicate it further on our site, it appears some users on an affecting PC are fine and others are not fine!

 

On the whole it's OK, it's just those random times and it's obviously a massive inconvenience for staff or students if they can't sign in to Office 365!

Posted

Been having the exact same issues described in the original post. So far seems to be related to 2004 update.

 

For wireless devices the workaround here fixes the issue, but I don't think it works for ethernet connected devices.

https://support.microsoft.com/en-gb/help/4494446/an-internet-explorer-or-edge-window-opens-when-your-computer-connects#:~:text=NLA%20uses%20a%20component%20that,has%20intranet%20or%20internet%20connectivity.&text=These%20probes%20are%20triggered%20by%20changes%20in%20any%20of%20the%20network%20interfaces.

Posted
Been having the exact same issues described in the original post. So far seems to be related to 2004 update.

 

For wireless devices the workaround here fixes the issue, but I don't think it works for ethernet connected devices.

https://support.microsoft.com/en-gb/help/4494446/an-internet-explorer-or-edge-window-opens-when-your-computer-connects#:~:text=NLA%20uses%20a%20component%20that,has%20intranet%20or%20internet%20connectivity.&text=These%20probes%20are%20triggered%20by%20changes%20in%20any%20of%20the%20network%20interfaces.

 

:(

 

We're on 1903 and it's affecting us.

 

It's not prevalent but annoying when it does affect a user who think we can fix it!!!

Posted

I know it's not a fix-fix, but if it's really causing you many problems connecting to apps etc, have you considered just putting your own DNS record redirecting to your webserver hosting that file?

 

All that's on the end of the check is a txt file with a line of writing in it (At least as a work around for now)

 

Steve

Posted
In a cmd window, what does the output of 'netsh winhttp show proxy' give...? we've had issues where the system proxy (the netsh result) was different from what was set in our managemnet console (CC4.5)

 

We've come back after the summer with this too on a CC4 network. It's pulling down our old (2 years ago) proxy settings, though it's set to no proxy in the RMMC. Did you ever resolve this?

 

Thanks

Posted

Further to my previous post, we have found that setting 'Specify global DNS' to enabled fixes the issue. This was a new group policy setting in 1709.

 

https://docs.microsoft.com/en-us/windows/client-management/new-policies-for-windows-10#new-group-policy-settings-in-windows10-version-1709

 

The registry setting can also be manually set:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator\UseGlobalDNS

DWORD Value 1

 

Hope that helps.

  • Thanks 1
Posted
Further to my previous post, we have found that setting 'Specify global DNS' to enabled fixes the issue. This was a new group policy setting in 1709.

 

https://docs.microsoft.com/en-us/windows/client-management/new-policies-for-windows-10#new-group-policy-settings-in-windows10-version-1709

 

The registry setting can also be manually set:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator\UseGlobalDNS

DWORD Value 1

 

Hope that helps.

 

Would there be any negative side effects of setting this thus?

 

GlobeDNS.JPG

Posted (edited)

I know Microsoft are aware of this “bug” in Windows 10 2004 and have acknowledged that a fix is coming, but have there been any developments on the “fix” - I was hoping it would have been available in the last patch Tuesday updates but still have the issue on our 2004 machines... I’ve tried the registry hacks with mixed results and no consistent work around!

 

I’m finding that where workarounds are saying to “EnableActiveProbing to 1” in the registry - the setting is already set to 1 -

 

Thanks

 

Matt

Edited by mattpant
  • 2 weeks later...
  • 2 weeks later...
Posted

Not sure if you guys seen it yet but there was a new release to fix this recently for 2004, think it's still optional at this stage:

 

https://support.microsoft.com/en-gb/help/4577063/windows-10-update-kb4577063

 

Addresses an issue that might prevent applications from opening or cause other errors when applications use Windows APIs to check for internet connectivity and the network icon incorrectly displays “No internet access” in the notification area. This issue occurs if you use a group policy or local network configuration to disable active probing for the Network Connectivity Status Indicator (NCSI). This also occurs if active probing fails to use a proxy and passive probes fail to detect internet connectivity.

 

Steve

  • Thanks 1
Posted

Will look forward to this rolling into the OS so I can get rid of various hacks - also is problematic at OOBE stage.

 

I reimaged a bunch of machines at the weekend to 2002 and I thought I had reoccurrence of this issue. The machines are quick to boot and login, but would take about a minute to decide to connect to the wifi (it could see the wifi just wasn't even trying to connect!). After checking the wireless lan service and its dependencies were starting as it should, I disabled the remote access connection manager more or less as a punt. 100% fixed that issue (reproducible both ways on multiple machines). Gotta love it.

  • 2 months later...
Posted

Update.

 

We're still getting issues affecting random PC's around the school.

Our advice is always to try a reboot which invariably fixes the issue.

 

I'm no closer to understanding what causes the issue on these random PC's.

 

It's an annoyance and affects the users because they are not signed in to Office 365 automatically as the PC believes there is no internet connection!

 

We run this reg. tweak to all new builds:

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet]
"ActiveDnsProbeContent"="131.107.255.255"
"ActiveDnsProbeContentV6"="fd3e:4f5a:5b81::1"
"ActiveDnsProbeHost"="dns.msftncsi.com"
"ActiveDnsProbeHostV6"="dns.msftncsi.com"
"ActiveWebProbeContent"="Microsoft Connect Test"
"ActiveWebProbeContentV6"="Microsoft Connect Test"
"ActiveWebProbeHost"="www.msftconnecttest.com"
"ActiveWebProbeHostV6"="ipv6.msftconnecttest.com"
"ActiveWebProbePath"="connecttest.txt"
"ActiveWebProbePathV6"="connecttest.txt"
"EnableActiveProbing"=dword:00000001
"PassivePollPeriod"=dword:0000000f
"StaleThreshold"=dword:0000001e
"WebTimeout"=dword:00000023
"MinimumInternetHopCount"=dword:00000001

 

And we also set the following to Enabled via Group Policy:

 

Do not show the "local access only" network icon

 

Turn off Windows Network Connectivity Status Indicator active tests

 

 

If anyone has any further insights I'd be grateful.

 

We were rolling out Windows 10 1903 EDU and have just started rolling out Windows 10 1909 EDU - not sure if MS added any fixes in to 1909 to address the problem but I'll continue with the REG tweak and policy changes.

  • 1 month later...
  • 1 month later...
Posted
Update.

 

We're still getting issues affecting random PC's around the school.

Our advice is always to try a reboot which invariably fixes the issue.

 

I'm no closer to understanding what causes the issue on these random PC's.

 

It's an annoyance and affects the users because they are not signed in to Office 365 automatically as the PC believes there is no internet connection!

 

We run this reg. tweak to all new builds:

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet]
"ActiveDnsProbeContent"="131.107.255.255"
"ActiveDnsProbeContentV6"="fd3e:4f5a:5b81::1"
"ActiveDnsProbeHost"="dns.msftncsi.com"
"ActiveDnsProbeHostV6"="dns.msftncsi.com"
"ActiveWebProbeContent"="Microsoft Connect Test"
"ActiveWebProbeContentV6"="Microsoft Connect Test"
"ActiveWebProbeHost"="www.msftconnecttest.com"
"ActiveWebProbeHostV6"="ipv6.msftconnecttest.com"
"ActiveWebProbePath"="connecttest.txt"
"ActiveWebProbePathV6"="connecttest.txt"
"EnableActiveProbing"=dword:00000001
"PassivePollPeriod"=dword:0000000f
"StaleThreshold"=dword:0000001e
"WebTimeout"=dword:00000023
"MinimumInternetHopCount"=dword:00000001

 

And we also set the following to Enabled via Group Policy:

 

Do not show the "local access only" network icon

 

Turn off Windows Network Connectivity Status Indicator active tests

 

 

If anyone has any further insights I'd be grateful.

 

We were rolling out Windows 10 1903 EDU and have just started rolling out Windows 10 1909 EDU - not sure if MS added any fixes in to 1909 to address the problem but I'll continue with the REG tweak and policy changes.

 

Just to bump this thread as we're still seeing this issue randomly pop up.

 

Is the only fix to upgrade all PC's to 20H2?

Posted
I've seen it happen on 20H2. When building machines missing some drivers, I had to put them on a separate wifi SSID to connect to WUO, then sometimes switching them back would stick.
  • Thanks 1
Posted
Disabling IPV4 Checksum offload in NIC advanced settings always fixes this for us.

 

Next time we get an occurrence of the issue I'll get the techies to check the state of this advanced setting. Is this something that can be changed via group policy?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...