04-15-2024, 06:26 PM
(This post was last modified: 04-15-2024, 06:30 PM by Grant_H.
Edit Reason: Formatting
)
Hi,
I had a similar issue, and discovered that for me, it seems to be caused the networked drives mapped on my laptop (Windows 10) I have a lot of in-office related maps that are not available off the LAN, and the save dialog is waiting for each one to timeout before trying the next one - adding up to a long wait.
The following post seems to have helped quite a lot. Not instant, but now useable when out of office:
(Whole post copied for reference)
https://answers.microsoft.com/en-us/wind...c3b5e2faee
That's the initial timeout for new Tcp/Ip connections in miliseconds. The default value is 3000 and it is doubled with each subsequent retry. So with 2 retries it takes 3+6+12 = 21 s before a connection attempt fails.
The change requires administrator privileges and is effective immediately, without restarting anything.
300 ms is the minimum allowed value. With other settings at their default values, it reduces the total timeout for offline network drives from 45-60 s to 5-15 s. But it may cause connection failures on very slow networks.
See http://support.microsoft.com/kb/170359 for more information.
I had a similar issue, and discovered that for me, it seems to be caused the networked drives mapped on my laptop (Windows 10) I have a lot of in-office related maps that are not available off the LAN, and the save dialog is waiting for each one to timeout before trying the next one - adding up to a long wait.
The following post seems to have helped quite a lot. Not instant, but now useable when out of office:
(Whole post copied for reference)
https://answers.microsoft.com/en-us/wind...c3b5e2faee
Code:
netsh interface tcp set global initialRto=300That's the initial timeout for new Tcp/Ip connections in miliseconds. The default value is 3000 and it is doubled with each subsequent retry. So with 2 retries it takes 3+6+12 = 21 s before a connection attempt fails.
The change requires administrator privileges and is effective immediately, without restarting anything.
300 ms is the minimum allowed value. With other settings at their default values, it reduces the total timeout for offline network drives from 45-60 s to 5-15 s. But it may cause connection failures on very slow networks.
See http://support.microsoft.com/kb/170359 for more information.