Slow on logoff.

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 connect
> to
> wireless hotspot and tries to log off or shut down the normal 1
> second
> ballon up into the minutes
>
> I've narrowed the process down to GPClient, but as to what exactl
> GPClien
> is trying to do that is causing the increased time I have not figure
> out
> Any suggestions on drilling down more on GPClient
>
> Logoff scripts have already been ruled out of the equation as a sourc
> o
> 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
>