On a system operating at full capacity, this can result in a delay large enough to cause the packet to be dropped or sent once the calling client has given up waiting. Checksum offloading causes certain calls to be processed in the CPU instead of the NIC. A reboot may also be required.)Īll Network Interface Cards (NICs) support checksum offloading for both TCP and UDP protocols. (Note: Applying these settings may cause the network to disconnect and should hence only be performed when the system is not in use. Even though the recommendations below are mainly for VMs, they can also be applied to physical machines with good results. When the machine running the DocuWare Web Client is a virtual machine, these performance issues are generally more severe than if the server was a physical machine. There are many possible reasons for this kind of behavior. One of those may help.What can be done to resolve slow performance or timeouts in the Web Client? “There are some settings for TCP/IP, go to "netsh interface tcp" and then run "set global" and you'll see all the options for some of the advanced TCP/IP configuration. If you have Server Core the following might help:
Instead, you can disable the task offload properties on the Advanced tab of the Properties dialog box of the network adapter. If you do not want to disable TCP segmentation offloading on the whole system, and you want to only disable TCP segmentation offloading on the network adapters that Virtual Server 2005 guests use, you must not add the DisableTaskOffload registry entry that is described in Method 2. You want to use Method 3 in this article: There is a really ancient Microsoft KB article that talks about this.
And they are properties of the NIC driver – it is not a single server level setting. These are things such as TCP Checksum Offload, Large Send Offload, etc. In this particular scenario the features (yes, multiple with some NIC drivers) are referred to as TCP Task Offload. So here is my third attempt to try and straighten this out. In actuality they did not disable the correct feature. The end result is that the problem is not resolved, so they come to the forum. So they disable “TCP Checksum Offload” using netsh on the Hyper-V Server. This is an issue that lately I have been answering a lot in the Hyper-V TechNet forum.įolks find a link that refers to disabling Checksum Offloading or TCP Offload to help with strange networking behavior with an application server (Remote Desktop Services, XenApp, Exchange, SQL, SharePoint, etc.).