Outlook Network Issue

[Bradcooper]

Hello,

We are having an issue with Office at the moment mainly causing issues with outlook. It's totally random but when staff open outlook they are getting a network issue error message "We are unable to connect right now. Please check your network and try again later." A restart fixes this temporarily.

 

What we have tried:

 

Updating from office 2019 to 2021.

Run this in powershell on the computer: "Disable-NetAdapterChecksumOffload -Name "*" -TcpIPv4" - This kicks it back into action temporarily.

re-image the computers having issues.

 

Please see attachments for screen shots, any ideas would be appreciated.

 

Thanks.

Edited February 6, 2023 by Bradcooper

[chaplic]

I am guessing that, say, you cab browse the web fine with chrome?

 

I think you have issues with NCSI - there's lots of it on here.

[Bradcooper]

Hi,

 

Yes they can browse the web and connect to network shares etc all fine.

 

thanks.

[aac]

I agree it sounds like NCSI. You want to set "Specify global DNS" and tick "Use global DNS" in

 

Computer Configuration/Administrative Templates/Network Connectivity/Status Indicator

[Oaktech]

Hello,

We are having an issue with Office at the moment mainly causing issues with outlook. It's totally random but when staff open outlook they are getting a network issue error message "We are unable to connect right now. Please check your network and try again later." A restart fixes this temporarily.

 

What we have tried:

 

Updating from office 2019 to 2021.

Run this in powershell on the computer: "Disable-NetAdapterChecksumOffload -Name "*" -TcpIPv4" - This kicks it back into action temporarily.

re-image the computers having issues.

 

Please see attachments for screen shots, any ideas would be appreciated.

 

Thanks.

 

I expect it is NCSI.

 

Has the school ever manipulated NCSI in any way - disabled it, redirected it to a local server etc? Are your devices allowed to turn off the network adapter in power saving?

 

One of the schools I support had it disabled for some reason - not just by policy but but by a load of reg hacks just scything keys out in startup scripts. It's taken me ages to work out exactly what that predecessor did to it and return it back to working order.