I have an issue between two Windows 7 machines. Here's the environment and the scenario: PC 1 resides in Network A PC 2 resides in Network B PC 1 is Windows 7 Pro 32-bit w/ 3GB RAM PC 2 is Windows 7 Pro 64-bit w/ 8GB RAM When the user logs into PC 1 locally and works, everything is grand. When the user logs out for the afternoon it takes approx. 30 seconds to complete the logoff request. The user then travels to another location to work. Each site is connected via a T1 circuit. The company is very small and only has one Windows Server. Each PC is a member of the domain. The functional level of the domain is 2008. The company's email is hosted by a provider and the user has configured MS Outlook to retrieve email from the company and stores the PST file locally on PC 1. The file is over 3GB in size. There are a few other resources local to the network segment PC 1 resides in that the user needs access to from Network B. In lieu of having the company purchase Remote Desktop Services and the licenses to accomodate this one and only user, I thought it would be wise to turn on Remote Desktop for PC 1. While the user is in Network B using PC 2, they could simply RDP into PC 1 and work. Life is grand.... When the user is done for the day and starts to logoff for the day, the logoff process from the RDP session takes on average 4 minutes. I'm not aware of anything that would be copied to/from the remote PC during this process. The logon process is quick. I've sifted through the event logs to look for any errors but I don't see anything. Any suggestions on where I could start to troubleshoot this thing? I have disabled auto creating the printers, no local drives are being mapped and the performance experience is set to low-speed broadband. There are no domain group policies for RDP and I'm not sure they would even apply to this anyway. Thanks in advance for any/all suggestions. Thanks! Chad

1. Have you done any detailed analysis with Network Monitor (MS or free Wireshark)? Any traces in Event logs? For processes analysis use Process Monitor from Sysinternals. 2. For faster respose try to change autotuning settings netsh interface tcp set global autotuninglevel=disabled netsh interface tcp set global autotuninglevel=highlyrestricted Regards Milos

Hi, Please test the issue by referencing the link below. http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/17c18c33-ec26-4225-bbbd-f2674e45838f If the issue persists, please disable Users Profiles Redirection in terminal server.Kim Zhou TechNet Community Support

Thanks for the suggestion Kim, but I'm not connecting to a terminal server. I'm connecting to another Windows 7 PC. Thanks! Chad

Milos, Thanks for the reply. I made several changes yesterday to the PC that the user is connecting to. I modified several items in the indexing options and I also discovered that IPV6 was disabled as well. Not sure why but the previous admin must have done that. I would have never purchased a 32-bit version of Windows either. I also increased the size of the virtual memory. The user mentioned yesterday and the message pops up that the system is low on VM. I looked in the event log and found several events stating that yesterday. Didn't see any prior to yesterday though. I discovered that the systems VM was configured for 2048 and the physical memory is 3GB. A 2GB VM file size is a bit small so I increased it to 3GB for now. I will try changing the autotuning settings if the above changes do not resolve the issue. Thanks! Chad

Hello Chad, any new update of troubleshooting? Have you tried to catch the network traffic? As to the user profiles, are they local or roaming? The latter would cause the delay in logout. What are real transfer rate in your T1? How does the real value differ from supposed? Have you played with active devices configuration? We have not speak on the Event logs - any traces? Is server Windows 2008 R2 or Windows 2008? Difference is in version of SMB, SMB 2.1 for newer verion of operating system. SMB 2.x which transfer files more effectively then previous version SMB 1.x (Windows XP -> SMB 1.x) Regards Milos

I worked on this again today. A few new things have surfaced that are a bit odd. The system is running out of virtual memory somewhere along the way. Not being on-site, it makes it difficult to see what's using it all by running Process Explorer. In regards to your questions above Milos.... The user profile is local. The transfer rate of the T1 is 1.5 Mbs up and down. The event logs are showing low system resources when it runs out of virutal memory. There is no server involved with this remote desktop connection. It is simply one Windows 7 Pro pc connecting to another Windows 7 Pro pc at another location. We are not using remote desktop services on a server at all. The customer uses proprietary software and I suspect there may be some issues running that through remote desktop. I'm going to have the user run the software locally and use everything else in the remote desktop. I'll try to pick one piece of software at a time and chip away at what's causing the memory leak. I believe if I find what's causing the memory leak my log off issues will go away as well. Thanks! Chad