Jump to content

Recommended Posts

Posted

Good Afternoon All,

 

Wondering if some of you wonderful people could offer some further suggestions/insight into a problem that we are having and getting extremly frustrated on.

 

On our Windows 1903 builds the computers are majority of the time saying they have no internet access when they clearly do as we can access everything. We ahve tried a number of things including:

 

 

  • Adding the Microsoft NCSI urls to our filtering allow list
  • Adding the named computer to filtering allow all group
  • Bypassing the Filtering system all together
  • Hosting our own NCSI internally
  • Disabling Internet Probing via Group Policy
  • Disabling IPv6 via Group Policy using registry changes
  • Uninstalled AV/Firewall
  • Installed Latest Updates
  • Took it off domain

 

We have had it working at times but cannot reliably get it working what works on one machine doesn't work on another. These include:

 

 

  • Disabling IPv6
  • De-attaching from the domain and re-attaching

 

This seems to be happening across the board of all new deployments since using 1903 and because of it when we are setting up Outlook for the first time using ADAL it fails to connect even with probing disabled. This is on different manufacture and models of computers and wasn't a problem in previous builds. It happens both on domain and off domain but only via LAN connection works perfectly on WIFI (part of the same LAN and its a flat network). We do also have a second network that is completly disjointed and goes straight out to the internet and it works on this network as well.

 

We deploy via WDS/MDT and just testing another image.

 

Kind Regards,

Max

  • 1 year later...
Posted

Hi, did you manage to resolve this problem? We have currently moved to 20H2 and it still seems to be a big problem, most machines here are showing no internet access.

 

Thanks

Posted

Good Afternoon,

 

Yes we did sort of. We haven't managed to fix it centrally however on individual computers if you go into Device manager and open properties to the network adapter then go to Advanced. Turn off TCP Offloading and reboot. That fixes the problem in all of our cases so far.

 

Kind regards,

Max

  • Thanks 1

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