Trying to connect message when Saving in Excel 365

I plan to sit down and version test my way back up the release chain, but I can say that 16227.20212 seems to be working without issue. 16327.20248 had it, and even rolling back to 16327.20214 still had it. Those are all builds of 2304, so maybe something changed between 2303 and 2304.

We are on 2304 and the problem is back but difficult to tell how bad as we are also having UK issues with 365 services.

We too have the issue when saving on DFS or directly on the file server itself and it seems to inpact some users o ly and especially those with large linked macro sheets it say obviously "trying to connect" and cuts out with some weird vba errors and for our users at another site the saving takes 3x as long as it should do. we've ruled out Netapp and Checkpoint and the ticket is with Microsoft. I guess this is a trick to get everyone to move to sharepoint online as we are anyway. Still nonethless the issue has been outstanding for 4 to 5 months here and webclient.exe disabling doesnt always work now. Interesting fault. 22H2 and on semi-annual I believe were stiill on 2208 I will beed to double checkon Monday! atleast bow I know the issue so will run Network monitor or wireshark and maybe tcpipview

Good to know I am not alone. MS is claiming solved and for a while it appeared to be. Came back about a week ago or maybe slightly more. Been running around at work with the quarantine issue so haven't been monitoring this closely. The network save bug coming back may explain the intermittent freeze in Outlook desktop as we use redirected folders here. Let me know what you find with wireshark please it could be really helpful.

Ffom a mate on Reddit who i asked too can you try the below and look into it, but with us I will need to check the below on the specific users with slow saving files and Trying to connect to error obviously- SevaraB

Netadmin If you were able to pin down the DFS location, you could have taken it to the finish line. Connecting with one version and connected with the previous tells me either:

1. The connection protocol was changed between versions
2. The authentication method changed between versions.

Authentication changes are way, way, way more likely here, IMO. Is that UNC share authenticating via Kerberos? LDAP? OAuth or SAML?

Also, how old a share are we talking? Is it possible that the share is looking for older encryption ciphers/protocols -like, say, RC4- that were deprecated and finally patched out of M365 apps?