Hi Sean: Glad to know that we're not the only one, in any case. :) One thing that one of our IT Team Members suggested is to disable the TCP Chimney Offload feature in Windows on the server. I'm checking with Scribe Support, to see if Scribe requires this feature. If Scribe does not require it, we may try disabling it. I don't know if it will work to fix this Scribe issue but, again, we may try it. Below is the information that IT found on this feature and on disabling it. You're welcome to try it. Again, though, I make no guarantees that this is the fix nor do I know whether disabling this actually causes any problems. If you do try it and have success, please let me know. support.microsoft.com/.../942861 blogs.dirteam.com/.../backward-compatible-networking-with-server-core.aspx The Following Commands Fixed this issue for me: netsh interface tcp set global rss=disabled netsh interface tcp set global chimney=disabled netsh interface tcp set global autotuning=disabled You can confirm that they were disabled with the following command netsh int tcp show global
↧