![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Performance and Maintainance of Windows Vista A forum for performance and maintenance tasks in Windows Vista. (microsoft.public.windows.vista.performance_maintainance) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
When a user is connected to the wired lan, then disconnects and connects to a
wireless hotspot and tries to log off or shut down the normal 14 seconds ballon up into the minutes. I've narrowed the process down to GPClient, but as to what exactly GPClient is trying to do that is causing the increased time I have not figured out. Any suggestions on drilling down more on GPClient? Logoff scripts have already been ruled out of the equation as a source of problems. |
|
|||
|
Erik;1116819 Wrote: When a user is connected to the wired lan, then disconnects and connects to a wireless hotspot and tries to log off or shut down the normal 14 seconds ballon up into the minutes. I've narrowed the process down to GPClient, but as to what exactly GPClient is trying to do that is causing the increased time I have not figured out. Any suggestions on drilling down more on GPClient? Logoff scripts have already been ruled out of the equation as a source of problems. It seems that "netsh interface tcp set global autotuninglevel=disable" would fix the problem. -- whs |
|
|||
|
Made no difference.
"whs" wrote: Erik;1116819 Wrote: When a user is connected to the wired lan, then disconnects and connects to a wireless hotspot and tries to log off or shut down the normal 14 seconds ballon up into the minutes. I've narrowed the process down to GPClient, but as to what exactly GPClient is trying to do that is causing the increased time I have not figured out. Any suggestions on drilling down more on GPClient? Logoff scripts have already been ruled out of the equation as a source of problems. It seems that "netsh interface tcp set global autotuninglevel=disable" would fix the problem. -- whs |