- #Microsoft entourage 2008 send receive so slow Pc
- #Microsoft entourage 2008 send receive so slow professional
It automatically determines the optimal receive window size on a per-connection basis. Receive Window Auto-Tuning has a number of benefits. The new TCP/IP stack no longer uses the TCPWindowSize registry values which many third-party utilities used to "tweak". As the data flows over the connection, the TCP/IP stack monitors the connection, measures the current bandwidth-delay product for the connection and the application receive rate, and adjusts the receive window size to optimize throughput. In Vista, Receive Window Auto-Tuning enables TCP window scaling by default, allowing up to a 16 MB window size. Receive Window Auto-Tuning continually determines the optimal receive window size by measuring the bandwidth-delay product and the application retrieve rate, and adjusts the maximum receive window size based on changing network conditions.
What is auto-tuning for the TCP/IP receive window? Well, the new Microsoft TCP/IP stack supports Receive Window Auto-Tuning. I was aware that Vista comes with a new RDP (Remote Desktop Protocol) client called Remote Desktop 6.0, which has more security and networking features, so perhaps there was some sort of network security conflict.Īfter doing some more research I discovered that Remote Desktop 6.0 leverages a new feature called auto-tuning for the TCP/IP receive window that could be causing the trouble.
#Microsoft entourage 2008 send receive so slow Pc
It was very odd, because from my Vista PC I could connect to many other machines with no problems. It was only when I used Remote Desktop from my brand new Windows Vista Ultimate Edition PC that the performance was terrible.
#Microsoft entourage 2008 send receive so slow professional
Further, when I tried Remote Desktop from a Windows XP Professional PC, the server was also fast. Thus, only when I used Remote Desktop was it slow. I logged on locally to the server and the server's performance was normal. That wasn't likely either since I'm pretty diligent about protecting my servers. It had all the earmarks of a server's CPU being overwhelmed.īut surely, this brand-spankin' new server will all this horsepower couldn't possibly be overloaded unless it had spyware or a virus. It didn't seem related to network connectivity since the screen redraw was fairly fast, but it just took a long time for the server to respond to keystrokes, mouse-clicks, etc. Moving a Window would also be painfully slow.
I'd click on something and wait and wait for my click to register. In particular, I was trying to manage a Windows 2003 R2 64-bit Server running Exchange 2007 with 4GB of RAM and a fast 1.83Ghz dual-core processor. Remote Desktop 6.0, the latest version of Microsoft Remote Desktop client, which comes pre-installed with Vista was slower than molasses when I tried connecting to some Windows 2003 servers.
0 kommentar(er)
