hi there,

It seems this problem is really spread.
this is a brand new HP Laptop running Vista (french).
WLM provide the same error @ logtime

when passing the netsh command line it fails with a weard message I cannot
figure what it means
===========================================
netsh interface tcp>set global autotuninglevel=disable

Échec de la commande Set global sur IPv4 L'opération demandée nécessite une
élévation.
==============================================

Sorry for the french , but it seems that the requested operation need to be
raised.
What ever this may means.

I cannot really understand that such a widly used utility as WLM do not work
right out the box !



"Judson Santiago" wrote:
[color=blue]
> I had the same problem with a Linksys WAG200 modem/router.
> Entering this command fixed the problem.
> Many thanks,
>
> Judson
>
>
> "Richard Holland" <RichardHolland@discussions.microsoft.com> escreveu na
> mensagem news:4F9AD8DA-50D5-492D-A44D-E902F522E492@microsoft.com...[color=green]
> > "DataBitz" wrote:
> >[color=darkred]
> >> Hi David,
> >> I found the procedure below in another group, and it solved my problem
> >> with
> >> Vista and Live Messenger. Apparently Vista's "auto-tuning" networking
> >> feature doesn't play nice with some routers. Not sure if it is a bug in
> >> Vista, a bug in Messenger or a bug in the router firmware but anyway this
> >> looks like a possible workaround that might help other people who have
> >> the
> >> same problem. BTW I have a NetGear DG834
> >>
> >> Try this:
> >> - Click start
> >> - Type: cmd
> >> - Right-click cmd.exe when it appears under Applications
> >> - Click Run As Administrator
> >> - Type the following: netsh int tcp set global autotuninglevel=disabled
> >> - Press enter
> >> - Restart your computer
> >>
> >> To check autotuning is disabled repeat the above but type: netsh int tcp
> >> show global[/color]
> >
> > I have the same problem, and a DG834 router. Entering this command fixed
> > the problem. However, my laptop also running vista never had a problem
> > connecting, even without this fix! Go figure![/color]
>[/color]