Windows Live Messenger & Vista Beta 2 - Error 81000306

  • Thread starter Thread starter Guest
  • Start date Start date
I just re-flashed my DG934G firmware to 3.01.25 (from the newer version
3.01.29, which has oddly enough disappeared from the Netgear website) and now
Windows Live Messenger works fine. :-)

Seems to be the solution folks!
 
I just re-flashed my DG934G firmware to 3.01.25 (from the newer version
3.01.29, which has oddly enough disappeared from the Netgear website) and now
Windows Live Messenger works fine. :-)

Seems to be the solution folks!
 
That did it.
I am running a DG834G and had the V3.01.29 Firmware installed, then rolled
it back to V3.01.25 and worked first go!
Awesome!
 
I am getting the error 81000388 in Live MSN 8. The problem is that I'm
getting another error on Gaim, and on every other MSN client I tried!!
There's NO WAY for me to connect to MSN in Vista Beta 2.

It seems like a DNS error (in Live's Connection Test it has a Warning Sign,
but it won't tell me what the problem is) but... the rest of the www works
perfectly, including AIM or Jabber.
MSN works too on this very same computer on every other operating system,
but not on Vista.

This is the most strange failure I've ever seen. Clean setup.
 
What kind of network setup do you have? Or is your modem connected directly
to your computer either through usb or ehternet (or internally)? Have you
tried the TCP test to see what message comes up?
 
Same issues here, however I'm using a SonicWALL TZ170 appliance. From a
server station, msn works jsut fine, connecting from a Vista machine (64bit)
generates the same errors as you guys.

Sometimes it comes with a 81000306 error, sometimes it pops up with "your
Display Name could not be changed. Please try again".

All tests go just fine!

Could it be the sonicwall, doing some funny stuff with the TCP stream, or is
it Vista 64 bit that's doing funny....

Cheers!
 
Coakeyoakey said:
I've installed Windows Live Messenger v8.0.0.689.00_Branches on Windows Vista
Beta 2 v5384.

I have followed the steps to disable UAP (UAC).
Added MSNMngr, msvs, msncall to be allowed by the Windows Vista Firewall.

I cannot sign on to Windows Live Messenger. On Signing in to Vista i get
Error code 81000306.

I did a connection test and i can connect to the Windows Live Messenger
servers in Tools \ Options \ Connection \ Advanced \ TCP Test.

Here is error log :
[11:55:54.098] Zone_HotmailService CreateReducedPolicy: This is a PPM
policy
[11:55:54.098] Zone_HotmailService CreateReducedPolicy: reduced policy
- ?id=507&tw=40&fs=1&kpp=1&kv=7&ver=2.1.6000.1&rn=u12DVH5B
[11:55:54.098] Zone_HotmailService
CHotmailService::FireLocalStateChangeResult@0002BB48:(S_OK, 0x0001)
[11:55:54.113] Zone_SDrive SDriveLifetime::OnLogonResult
(0x81000306)
[11:55:54.113] Zone_SDrive SDriveLifetime::OnServiceLogoff
[11:55:54.113] Zone_SDrive Buddy's not online - Cannot get root
paths
[11:55:54.113] Zone_ConfigInfo CErrorResponder::Initialize -
UNHOOK_ALL_EVENTS for CConfigServerClientEvents
[11:55:54.113] Zone_ConfigInfo CErrorResponder::Initialize -
HOOK_EVENT for CConfigServerClientEvents
[11:55:54.113] Zone_ConfigInfo CSGetConfigInfo - with with
fRefresh=false
[11:55:54.113] Zone_ConfigInfo CSGetConfigInfo - not online.
[11:55:54.238] Zone_ConnectionTroubleshooter Appcompat canary not set.
[11:55:54.301] Zone_Net
CConnectionManager::OnConnectionStateChange@0259EFD0: Recieved state change
for id(3) from 0 to 1
[11:55:54.301] Zone_Net
CConnectionManager::OnConnectionStateChange@0259EFD0: Ignoring state change


Note : I am using same computer on XP and it signs in correctly.

Anyone any ideas ?
Click to expand...
 
Hi All

I just upgraded my Netgear DG834v2 to version 3.01.25 and it sorted the
problem out.

Hope it works for you too.

Cheers
 
I'm running a bunch of sonicwalls (TZ170, 2040, 4060) and all have the same
issue. As a Gold Medallion partner with Sonicwall, I've tried to get some
added focus on this, but since we're in beta there is not much support as of
yet... Let you know if I find anything out...
 
Found Sonicwall WorkAround... On the advanced tab of the firewall section on
an enhanced mode box (working for version 3.2 on all of the platforms noted
earlier), uncheck the "Enable Support for Windows Messenger" option. Not
sure why this causes the problem, but have posted an incident with Sonicwall
to alert them to the issue. This worked on all of our test boxes...
 
Hi,

I have this problem with Vista RC2 and i'm using a Linksys router WAG200G,
any suggestions ?

Thanks.
 
everything else works except for the SOCKS bit and on the troubleshooter it says there is something wrong with the Key Ports but my firewall is turned off

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
 
having trouble with windows live messenger need help , wont work , its loaded
on programs but still wont work. it says windows live mesenger has stopped
working,then it says something like it has a problem and windows is
closingand looking for a solution which never comes
 
Very Important: This is the Final Solution to this problem !!!

Regarding: (Messenger Vista 81000306)

The problem is caused by a Net-Gear Router.

Here is the real solution:

- 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
- There is no need to restart, Messenger will start working right away.

(c) Dr. Hisham® G. El-Banhawy
 
Very Important: This is the Final Solution to this problem !!!

Regarding: (Messenger Vista 81000306)

The problem is caused by a Net-Gear Router.

Here is the real solution:

- 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
- There is no need to restart, Messenger will start working right away.

(c) Dr. Hisham® G. El-Banhawy
 
Very Important: This is the Final Solution to this problem !!!

Regarding: (Messenger Vista 81000306)

The problem is caused by a Net-Gear Router.

Here is the real solution:

- 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
- There is no need to restart, Messenger will start working right away.

(c) Dr. Hisham® G. El-Banhawy
 
Back
Top