Jump to content

Recommended Posts

Posted

Just trying to get head round the issue.

 

Background is our core Switch gives out our ip address and this computer plugs into the edge switch. The computer gets an ip but it says no internet access. I can ping the default gateway/core switch and upstream plus it resolves and pings google.co.uk. After around 1 minute it will start working fine. I am pointing to network driver on the device but wondered if anyone has seen this before?

Posted
Just trying to get head round the issue.

 

Background is our core Switch gives out our ip address and this computer plugs into the edge switch. The computer gets an ip but it says no internet access. I can ping the default gateway/core switch and upstream plus it resolves and pings google.co.uk. After around 1 minute it will start working fine. I am pointing to network driver on the device but wondered if anyone has seen this before?

 

It’s often due to poor/hesitant connection to the MS servers it contacts to determine if it can get out of the LAN/WAN. Smoothwall can play a part in this. If it thinks that it has no access, it won’t even attempt to download drivers (despite having internet access).

  • Thanks 1
Posted
It’s often due to poor/hesitant connection to the MS servers it contacts to determine if it can get out of the LAN/WAN. Smoothwall can play a part in this. If it thinks that it has no access, it won’t even attempt to download drivers (despite having internet access).

 

Are you saying issue likely on client side or on switches? There is a smoothwall upstream but can ping it and speed tests at site are showing 95/95mb on machines which are having the issue.

Posted

Client Side. You're thinking too low level (and tbf too logical for microsoft :rolleyes: )

 

Windows has something called NCSI which uses a variety of methods to detect if it has an internet connection. its poorly documented, contradictory, intermittent. But once NCSI decides no internet, whatever relies on it (not everything does) will not connect. Chrome ignores NCSI

 

Also, what Ive seen done is a scheduled task that sets a proxy, or not, depending on network connectivity and that would follow with your basic network connectivity working but not application layer stuff, but I think you'd know if you had that configured.

 

I use this script which touch wood has been reliable but got there through trial-and-error and if you start googling NCSI then you'll see everyone has a different take, I think because it's intermittent what works and what doesn't isnt always obviousl.

 

 

 

if((Test-Path -LiteralPath "HKLM:\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet") -ne $true) { New-Item "HKLM:\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet" -force -ea SilentlyContinue };Set-ItemProperty -LiteralPath 'HKLM:\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet' -Name 'EnableActiveProbing' -Value 1 -Force Set-ItemProperty -LiteralPath 'HKLM:\Software\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator' -Name 'NoActiveProbe' -Value 0 -Force Set-ItemProperty -LiteralPath 'HKLM:\Software\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator' -Name 'DisablePassivePolling' -Value 0 -Force Set-ItemProperty -LiteralPath 'HKLM:\Software\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator' -Name 'UseGlobalDNS' -Value 1 -Force

  • Thanks 2

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...