Recently I made a number of changes, one of which was to make a certain UNC path "always available offline". And then I made that path also the only path defined in my Documents library. After the changes, I'd have a couple of strange things happen. Perhaps every 2nd or 3rd save of a file would result in hang time... perhaps 5 - 10 seconds, even with small files and no actual changes. Also, some directories with a greater quantity of items would not update quickly at all. For example, if I right click and New Folder, nothing would appear. I press F5, and it shows up highlighted waiting for me to type the name of the folder. I type the name and press enter, and nothing. I hit F5, and there it is with the new name. I drag files in, but they don't show up... press F5, and there they are. Or rather than pressing F5, it turns out that waiting 30 seconds to 1 minute also works. But weird. Someone suggested that I should instead make the UNC location a mapped drive. I did. First I made it so the location was no longer available offline. Then formatted the Offline Files db. Mapped the UNC path to a letter, and made that letter available offline, and added THAT to my documents library as the only source. Sure enough... both problems have disappeared. I'd love to know why.

Can be related to delayed TCP/IP acknowledgment, also known as a TCP ACK, occurs in an "SMB: C NT transact - Notify Change" packet. Typically, change Notify requests in Windows Explorer occur more frequently when you use a mapped drive than when you use a UNC path to connect to the network share. However the case when you used UNC path should not occur. That kind of issue can be caused by firewall. In some cases it can also be caused by your network devices that do not support Auto-Tuning.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.