MSN 7.0 Hung after log on (possible solution)

Hi,

To all those who face the above mentioned problem like me, I think I may
have found out what is actually causing this issue.

In my case I am behind my home WLAN router (DLINK DI 824VUP+). Followed
Jonathan suggestion on deleting msn folder and amending the registry but
still did not work out (worked once but after which it never happen again).

So i went to take a connection log in MSN messenger 7.0 and found the
following line which may prove to be some kind of network firewall problem.

[17:23:51.966] Voice CEchoClient::ProcessNATDetection > Phase 5
[17:23:51.976] Voice CEchoClient::ReceiveSecondaryEchoTest > Timed out
waiting 1112327013ms for response from secondary echo server. Already
tested no firewall, so must be misconfigured echo test server.

Thinking on this path I went to amend my firewall settings on my XP but
still it doesn't work. The next logical step was to amend my router
configuration. To my surprise I found a solution to my problem. By setting
SPI mode to disable, MSN messenger 7.0 works. For those who don't know what
SPI (Stateful Packet Inspection), the explanation is as below:

SPI Mode
When this feature is enabled, the router will record the packet information
pass through the router like IP address, port address, ACK, SEQ number and
so on. And the router will check every incoming packet to detect if this
packet is valid.

This leads to my conclusion. Apparently with SPI Enabled, my router
inspected the packet MSN messenger 7.0 transmitted and somewhere along the
line this packet was found to be "Not trusted" and was droped. Thus leads
to the failure to completed whatever programming sequence was was coded into
MSN messenger 7.0. This cause MSN messenger 7.0 to be in a deadlock,
forever waiting for the packet before it can continue.

This solution works for me. I am just guessing why the hanging occurs on my
side and this reason might not be the case for all other who also faced the
same problem.

Hope this piece of information help the other who face the same problem.
Lets pray Microsoft will fix this problem.

Regards,
Winston

Jonathan
Fri Apr 08 13:11:06 CDT 2005

Greetings Winston,

Excellent, this explains -a lot-.
____________________________________________
Jonathan Kay
Microsoft MVP - MSN Messenger/Windows Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.

"Winston" <WINSTONLI@miw.com.sg> wrote in message
news:OvGHZLGPFHA.1564@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> To all those who face the above mentioned problem like me, I think I may have found out
> what is actually causing this issue.
>
> In my case I am behind my home WLAN router (DLINK DI 824VUP+). Followed Jonathan
> suggestion on deleting msn folder and amending the registry but still did not work out
> (worked once but after which it never happen again).
>
> So i went to take a connection log in MSN messenger 7.0 and found the following line which
> may prove to be some kind of network firewall problem.
>
> [17:23:51.966] Voice CEchoClient::ProcessNATDetection > Phase 5
> [17:23:51.976] Voice CEchoClient::ReceiveSecondaryEchoTest > Timed out waiting 1112327013ms
> for response from secondary echo server. Already tested no firewall, so must be
> misconfigured echo test server.
>
> Thinking on this path I went to amend my firewall settings on my XP but still it doesn't
> work. The next logical step was to amend my router configuration. To my surprise I found
> a solution to my problem. By setting SPI mode to disable, MSN messenger 7.0 works. For
> those who don't know what SPI (Stateful Packet Inspection), the explanation is as below:
>
> SPI Mode
> When this feature is enabled, the router will record the packet information pass through
> the router like IP address, port address, ACK, SEQ number and so on. And the router will
> check every incoming packet to detect if this packet is valid.
>
> This leads to my conclusion. Apparently with SPI Enabled, my router inspected the packet
> MSN messenger 7.0 transmitted and somewhere along the line this packet was found to be "Not
> trusted" and was droped. Thus leads to the failure to completed whatever programming
> sequence was was coded into MSN messenger 7.0. This cause MSN messenger 7.0 to be in a
> deadlock, forever waiting for the packet before it can continue.
>
> This solution works for me. I am just guessing why the hanging occurs on my side and this
> reason might not be the case for all other who also faced the same problem.
>
> Hope this piece of information help the other who face the same problem. Lets pray
> Microsoft will fix this problem.
>
> Regards,
> Winston
>
>
>

Jonathan
Fri Apr 08 13:17:48 CDT 2005

Hi Winston,

By the way, the log files that people sent to me also show exactly the same thing.
____________________________________________
Jonathan Kay
Microsoft MVP - MSN Messenger/Windows Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.

"Jonathan Kay [MVP]" <msnewsreplies@jonathankay.com> wrote in message
news:OF2yWZGPFHA.164@TK2MSFTNGP12.phx.gbl...
> Greetings Winston,
>
> Excellent, this explains -a lot-.
> ____________________________________________
> Jonathan Kay
> Microsoft MVP - MSN Messenger/Windows Messenger
> Associate Expert
> http://www.microsoft.com/windowsxp/expertzone/
> Messenger Resources - http://messenger.jonathankay.com
> All posts unless otherwise specified are (c) 2005 Jonathan Kay.
> You *must* contact me for redistribution rights.
>
> "Winston" <WINSTONLI@miw.com.sg> wrote in message
> news:OvGHZLGPFHA.1564@TK2MSFTNGP14.phx.gbl...
>> Hi,
>>
>> To all those who face the above mentioned problem like me, I think I may have found out
>> what is actually causing this issue.
>>
>> In my case I am behind my home WLAN router (DLINK DI 824VUP+). Followed Jonathan
>> suggestion on deleting msn folder and amending the registry but still did not work out
>> (worked once but after which it never happen again).
>>
>> So i went to take a connection log in MSN messenger 7.0 and found the following line which
>> may prove to be some kind of network firewall problem.
>>
>> [17:23:51.966] Voice CEchoClient::ProcessNATDetection > Phase 5
>> [17:23:51.976] Voice CEchoClient::ReceiveSecondaryEchoTest > Timed out waiting
>> 1112327013ms for response from secondary echo server. Already tested no firewall, so must
>> be misconfigured echo test server.
>>
>> Thinking on this path I went to amend my firewall settings on my XP but still it doesn't
>> work. The next logical step was to amend my router configuration. To my surprise I found
>> a solution to my problem. By setting SPI mode to disable, MSN messenger 7.0 works. For
>> those who don't know what SPI (Stateful Packet Inspection), the explanation is as below:
>>
>> SPI Mode
>> When this feature is enabled, the router will record the packet information pass through
>> the router like IP address, port address, ACK, SEQ number and so on. And the router will
>> check every incoming packet to detect if this packet is valid.
>>
>> This leads to my conclusion. Apparently with SPI Enabled, my router inspected the packet
>> MSN messenger 7.0 transmitted and somewhere along the line this packet was found to be
>> "Not trusted" and was droped. Thus leads to the failure to completed whatever programming
>> sequence was was coded into MSN messenger 7.0. This cause MSN messenger 7.0 to be in a
>> deadlock, forever waiting for the packet before it can continue.
>>
>> This solution works for me. I am just guessing why the hanging occurs on my side and this
>> reason might not be the case for all other who also faced the same problem.
>>
>> Hope this piece of information help the other who face the same problem. Lets pray
>> Microsoft will fix this problem.
>>
>> Regards,
>> Winston
>>
>>
>>
>
>

anonymous
Fri Apr 08 14:18:50 CDT 2005

For the computer illiterate, as well as for those of us
who do not have a router... what can we do?


>-----Original Message-----
>Greetings Winston,
>
>Excellent, this explains -a lot-.
>____________________________________________
>Jonathan Kay
>Microsoft MVP - MSN Messenger/Windows Messenger
>Associate Expert
>http://www.microsoft.com/windowsxp/expertzone/
>Messenger Resources - http://messenger.jonathankay.com
>All posts unless otherwise specified are (c) 2005
Jonathan Kay.
>You *must* contact me for redistribution rights.
>
>"Winston" <WINSTONLI@miw.com.sg> wrote in message
>news:OvGHZLGPFHA.1564@TK2MSFTNGP14.phx.gbl...
>> Hi,
>>
>> To all those who face the above mentioned problem like
me, I think I may have found out
>> what is actually causing this issue.
>>
>> In my case I am behind my home WLAN router (DLINK DI
824VUP+). Followed Jonathan
>> suggestion on deleting msn folder and amending the
registry but still did not work out
>> (worked once but after which it never happen again).
>>
>> So i went to take a connection log in MSN messenger
7.0 and found the following line which
>> may prove to be some kind of network firewall problem.
>>
>> [17:23:51.966] Voice CEchoClient::ProcessNATDetection
> Phase 5
>> [17:23:51.976] Voice
CEchoClient::ReceiveSecondaryEchoTest > Timed out waiting
1112327013ms
>> for response from secondary echo server. Already
tested no firewall, so must be
>> misconfigured echo test server.
>>
>> Thinking on this path I went to amend my firewall
settings on my XP but still it doesn't
>> work. The next logical step was to amend my router
configuration. To my surprise I found
>> a solution to my problem. By setting SPI mode to
disable, MSN messenger 7.0 works. For
>> those who don't know what SPI (Stateful Packet
Inspection), the explanation is as below:
>>
>> SPI Mode
>> When this feature is enabled, the router will record
the packet information pass through
>> the router like IP address, port address, ACK, SEQ
number and so on. And the router will
>> check every incoming packet to detect if this packet
is valid.
>>
>> This leads to my conclusion. Apparently with SPI
Enabled, my router inspected the packet
>> MSN messenger 7.0 transmitted and somewhere along the
line this packet was found to be "Not
>> trusted" and was droped. Thus leads to the failure to
completed whatever programming
>> sequence was was coded into MSN messenger 7.0. This
cause MSN messenger 7.0 to be in a
>> deadlock, forever waiting for the packet before it can
continue.
>>
>> This solution works for me. I am just guessing why
the hanging occurs on my side and this
>> reason might not be the case for all other who also
faced the same problem.
>>
>> Hope this piece of information help the other who face
the same problem. Lets pray
>> Microsoft will fix this problem.
>>
>> Regards,
>> Winston
>>
>>
>>
>
>
>.
>

malecatsub
Fri Apr 08 14:20:39 CDT 2005


this SPI thing might work for you, but for the rest of us
who use a Linksys router, there is _nothing_ in the
router set-up utility w/ those letters, so it is of no
help for the rest of us.

Jonathan
Fri Apr 08 14:44:28 CDT 2005

Hi,

Hopefully they'll get a fix out for this soon.
____________________________________________
Jonathan Kay
Microsoft MVP - MSN Messenger/Windows Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2005 Jonathan Kay.
You *must* contact me for redistribution rights.

<malecatsub@hotmail.com> wrote in message news:09c501c53c70$0cdd7190$a501280a@phx.gbl...
>
> this SPI thing might work for you, but for the rest of us
> who use a Linksys router, there is _nothing_ in the
> router set-up utility w/ those letters, so it is of no
> help for the rest of us.

Frederico
Fri Apr 08 14:55:02 CDT 2005

i hope the same thing too! for Microsoft sakes! i mean for users sakes! :|

"Jonathan Kay [MVP]" wrote:

> Hi,
>
> Hopefully they'll get a fix out for this soon.
> ____________________________________________
> Jonathan Kay
> Microsoft MVP - MSN Messenger/Windows Messenger
> Associate Expert
> http://www.microsoft.com/windowsxp/expertzone/
> Messenger Resources - http://messenger.jonathankay.com
> All posts unless otherwise specified are (c) 2005 Jonathan Kay.
> You *must* contact me for redistribution rights.
>
> <malecatsub@hotmail.com> wrote in message news:09c501c53c70$0cdd7190$a501280a@phx.gbl...
> >
> > this SPI thing might work for you, but for the rest of us
> > who use a Linksys router, there is _nothing_ in the
> > router set-up utility w/ those letters, so it is of no
> > help for the rest of us.
>
>
>

Winston
Sat Apr 09 03:18:14 CDT 2005

Hi,

In some cases the SPI is enable on the router it self and cannot not be
turned off. However, some special cases like the first generation router
with SPI capabilities, the packet pass thru fine.

Perhaps asking the manufacturer of the routers if there is other way (like
telnet) to configure the router or wait for the new patchs from microsoft
when they solved the problem.

Regards,
Winston
<malecatsub@hotmail.com> wrote in message
news:09c501c53c70$0cdd7190$a501280a@phx.gbl...
>
> this SPI thing might work for you, but for the rest of us
> who use a Linksys router, there is _nothing_ in the
> router set-up utility w/ those letters, so it is of no
> help for the rest of us.

dt23
Sat Apr 09 10:21:31 CDT 2005

unfortunenately, the SPi firewall is really effective. no
way i gonan it off jus for msn7.0. time to rollback to 6.2
methinks

>-----Original Message-----
>Hi,
>
>To all those who face the above mentioned problem like me,
I think I may
>have found out what is actually causing this issue.
>
>In my case I am behind my home WLAN router (DLINK DI
824VUP+). Followed
>Jonathan suggestion on deleting msn folder and amending
the registry but
>still did not work out (worked once but after which it
never happen again).
>
>So i went to take a connection log in MSN messenger 7.0
and found the
>following line which may prove to be some kind of network
firewall problem.
>
>[17:23:51.966] Voice CEchoClient::ProcessNATDetection >
Phase 5
>[17:23:51.976] Voice CEchoClient::ReceiveSecondaryEchoTest
> Timed out
>waiting 1112327013ms for response from secondary echo
server. Already
>tested no firewall, so must be misconfigured echo test server.
>
>Thinking on this path I went to amend my firewall settings
on my XP but
>still it doesn't work. The next logical step was to amend
my router
>configuration. To my surprise I found a solution to my
problem. By setting
>SPI mode to disable, MSN messenger 7.0 works. For those
who don't know what
>SPI (Stateful Packet Inspection), the explanation is as below:
>
>SPI Mode
>When this feature is enabled, the router will record the
packet information
>pass through the router like IP address, port address,
ACK, SEQ number and
>so on. And the router will check every incoming packet to
detect if this
>packet is valid.
>
>This leads to my conclusion. Apparently with SPI Enabled,
my router
>inspected the packet MSN messenger 7.0 transmitted and
somewhere along the
>line this packet was found to be "Not trusted" and was
droped. Thus leads
>to the failure to completed whatever programming sequence
was was coded into
>MSN messenger 7.0. This cause MSN messenger 7.0 to be in
a deadlock,
>forever waiting for the packet before it can continue.
>
>This solution works for me. I am just guessing why the
hanging occurs on my
>side and this reason might not be the case for all other
who also faced the
>same problem.
>
>Hope this piece of information help the other who face the
same problem.
>Lets pray Microsoft will fix this problem.
>
>Regards,
>Winston
>
>
>
>.
>