Does this still occur after upgrading to the latest beta version of WL
Messenger client?
http://download.live.com/messenger
- Jeroen
"c0rnflex" <> wrote in message
news:...
>
> Hi all,
> For the last couple of months I've been dealing with constant random
> logoff's of my WLM.
> Being an IT tech myself, I took a look at the connection log and just
> recently marked down the following lines as the cause to the issue
> (socket numbers vary):
>
> [16:48:44.07] Zone_HotmailProtocol
> CMNSConnection::OnPNGTimer@03A07070: PNG timer fired for 1th time
> [16:48:44.07] Zone_Net CTCPNetworkLayer::Send
> (03A07C58) >> sent 5 bytes on socket 2708
> [16:48:44.07] Zone_HotmailProtocol
> CMNSConnection::SendNetMsg@03A07070: Sent >PNG<
> [16:48:59.08] Zone_HotmailProtocol
> CMNSConnection::OnPNGTimer@03A07070: PNG timer fired for 1th time
> [16:48:59.08] Zone_Net CTCPNetworkLayer::Send
> (03A07C58) >> sent 5 bytes on socket 2708
> [16:48:59.08] Zone_HotmailProtocol
> CMNSConnection::SendNetMsg@03A07070: Sent >PNG<
> [16:49:14.08] Zone_HotmailProtocol
> CMNSConnection::OnPNGTimer@03A07070: PNG timer fired for 1th time
> [16:49:14.08] Zone_Net CTCPNetworkLayer::Send
> (03A07C58) >> sent 5 bytes on socket 2708
> [16:49:14.08] Zone_HotmailProtocol
> CMNSConnection::SendNetMsg@03A07070: Sent >PNG<
> [16:49:16.13] ZONE_NET CTCPNETWORKLAYER::ONMESSAGE
> (03A07C58) (2) >> GOT WM_WSASELECT_MESSAGE(1055) FROM WSAASYNCSELECT FOR
> SOCKET = 2708, ERROR = 10053, EVENT = FD_CLOSE
> [16:49:16.13] ZONE_NET CTCPNETWORKLAYER::ONERROR
> (03A07C58) (2) >> CALLED WITH 0X80072745
> [16:49:16.13] ZONE_NET CTCPNETWORKLAYER::ONSOCKETCLOSE
> (03A07C58) (2) CLOSING SOCKET 2708
> Basically as I understand it, PNG commands from the server are being
> sent, and replied to by the client with QNG commands. usually my client
> responds just fine, but as you can see sometimes it fails responding and
> the socket gets closed down, which immediately turns on the log off
> process and disconnects my WLM.
> I've been in contact with the MS WLM escalation team but until now with
> no success.
>
> I'm really hoping you guys could help me identify and resolve this
> issue.
>
>
> --
> c0rnflex