Audio conversation using Messenger in XP 2

[leftywedge]

HI,
I am trying to create an audio conversation with messenger in WinXP. One PC works ok the other not. Both go through the same firewall and router. Both have the same Messenger version. Hardware is OK too (mic and speakers).

What can cause this?

LW

 

[KimLeece]

I have had similar problems with Messenger. Video connections seem to work fine, but as soon as you try to add the audio anything can happen - half connections, patchy sound (hear some bits not others), one sided connections etc. All the hardware checks out, and sometimes it works better than others. My final conclusion was that it was probably to do with the amount of available bandwidth on one side or the other - or maybe how busy or not the Microsoft servers are. There really didn't seem to be much to do about it. Probably if you use other video conferencing software that has quieter servers it might work better - but you have to pay for that! I'll be interested to see if anyone comes up with a good answer to this one!!!

Kim.

'Everybody is ignorant - only on different subjects.'
Will Rogers.

 

[Mikke]

Here is the complete Log that we captured regarding MSN Messenger from the side that is having the trouble.

If you copy and paste the data into a note or Word Document it will be easier to read.

The following was conducted during this logging session.

1. Connection is made to the MSN when starting the application
2. Connection is made to other user
3. Other user sends a "hello" note
4. Bad side sends a "hello" note
5. Good side invites the bad for a voice conversation
6. The Bad side accepts the invite
7. A voice convesation IS established
8. The bad side can hear the good side
9. The good side can not hear the bad
10. Session terminated

Once again, what you see hear is the log from the bad side.
No sign of Port 6901 yet voice was going one way.

Thanks for the help

Time ACTION PRO Local Addrort Remote Addrort Status Byte Process
11:47:57am RECEIVE TCP 192.168.0.100:4417 207.46.107.49:1863 Success 91 msnmsgr.exe:1140 United States
11:47:57am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:47:57am CONNECT TCP 0.0.0.0:4428 207.46.108.63:1863 Success msnmsgr.exe:1140 United States
11:47:57am SEND TCP 192.168.0.100:4428 207.46.108.63:1863 Success 52 msnmsgr.exe:1140 United States
11:47:57am RECEIVE TCP 192.168.0.100:4428 207.46.108.63:1863 Success 51 msnmsgr.exe:1140 United States
11:47:57am RECEIVE TCP 192.168.0.100:4428 207.46.108.63:1863 Success 10 msnmsgr.exe:1140 United States
11:47:59am RECEIVE TCP 192.168.0.100:4428 207.46.108.63:1863 Success 140 msnmsgr.exe:1140 United States
11:47:59am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:47:59am CONNECT TCP 0.0.0.0:4429 207.68.171.232:80 Success msnmsgr.exe:1140 United States
11:47:59am SEND UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:47:59am RECEIVE UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:47:59am RECEIVE TCP 192.168.0.100:4427 206.24.190.189:80 Success 0 msnmsgr.exe:1140 United States
11:47:59am SEND TCP 192.168.0.100:4429 207.68.171.232:80 Success 262 msnmsgr.exe:1140 United States
11:47:59am CLOSE TCP 192.168.0.100:4427 206.24.190.189:80 Success msnmsgr.exe:1140 United States
11:47:59am RECEIVE TCP 192.168.0.100:4426 207.68.178.239:80 Success 1 msnmsgr.exe:1140 United States
11:47:59am SEND UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:47:59am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 1024 msnmsgr.exe:1140 United States
11:47:59am RECEIVE UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:47:59am SEND UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:47:59am RECEIVE UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:00am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 1024 msnmsgr.exe:1140 United States
11:48:00am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 356 msnmsgr.exe:1140 United States
11:48:00am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 1024 msnmsgr.exe:1140 United States
11:48:00am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 99 msnmsgr.exe:1140 United States
11:48:00am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 1 msnmsgr.exe:1140 United States
11:48:00am SEND UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:00am RECEIVE UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:00am SEND UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:00am RECEIVE UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:01am RECEIVE TCP 192.168.0.100:4428 207.46.108.63:1863 Success 177 msnmsgr.exe:1140 United States
11:48:06am SEND TCP 192.168.0.100:4428 207.46.108.63:1863 Success 106 msnmsgr.exe:1140 United States
11:48:08am SEND TCP 192.168.0.100:4428 207.46.108.63:1863 Success 142 msnmsgr.exe:1140 United States
11:48:09am RECEIVE TCP 192.168.0.100:4428 207.46.108.63:1863 Success 522 msnmsgr.exe:1140 United States
11:48:09am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:09am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:09am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:09am SEND UDP 192.168.0.100:64643 192.168.0.1:1900 Success 132 msnmsgr.exe:1140
11:48:09am SEND UDP 192.168.0.100:64643 192.168.0.1:1900 Success 133 msnmsgr.exe:1140
11:48:09am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:09am SEND UDP 192.168.0.100:64643 192.168.0.100:1900 Success 132 msnmsgr.exe:1140
11:48:09am SEND UDP 192.168.0.100:64643 192.168.0.100:1900 Success 133 msnmsgr.exe:1140
11:48:09am CLOSE UDP 0.0.0.0:0 0.0.0.0:0 Success msnmsgr.exe:1140
11:48:09am RECEIVE UDP 192.168.0.100:64643 192.168.0.1:1900 Success 310 msnmsgr.exe:1140
11:48:09am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:09am CONNECT TCP 192.168.0.100:58649 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:09am SEND TCP 192.168.0.100:58649 192.168.0.1:5678 Success 70 msnmsgr.exe:1140
11:48:10am RECEIVE TCP 192.168.0.100:58649 192.168.0.1:5678 Success 119 msnmsgr.exe:1140
11:48:10am RECEIVE TCP 192.168.0.100:58649 192.168.0.1:5678 Success 3220 msnmsgr.exe:1140
11:48:10am CLOSE TCP 192.168.0.100:58649 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:10am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:10am CONNECT TCP 192.168.0.100:27023 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:10am SEND TCP 192.168.0.100:27023 192.168.0.1:5678 Success 478 msnmsgr.exe:1140
11:48:11am RECEIVE TCP 192.168.0.100:27023 192.168.0.1:5678 Success 797 msnmsgr.exe:1140
11:48:11am CLOSE TCP 192.168.0.100:27023 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:11am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:11am CONNECT TCP 192.168.0.100:8723 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:11am SEND TCP 192.168.0.100:8723 192.168.0.1:5678 Success 499 msnmsgr.exe:1140
11:48:12am RECEIVE TCP 192.168.0.100:8723 192.168.0.1:5678 Success 608 msnmsgr.exe:1140
11:48:12am CLOSE TCP 192.168.0.100:8723 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:12am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:12am CONNECT TCP 192.168.0.100:29446 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:12am SEND TCP 192.168.0.100:29446 192.168.0.1:5678 Success 499 msnmsgr.exe:1140
11:48:12am RECEIVE TCP 192.168.0.100:29446 192.168.0.1:5678 Success 608 msnmsgr.exe:1140
11:48:12am CLOSE TCP 192.168.0.100:29446 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:12am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:12am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:12am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:12am CONNECT TCP 192.168.0.100:31703 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:12am SEND TCP 192.168.0.100:31703 192.168.0.1:5678 Success 896 msnmsgr.exe:1140
11:48:13am RECEIVE TCP 192.168.0.100:31703 192.168.0.1:5678 Success 477 msnmsgr.exe:1140
11:48:13am CLOSE TCP 192.168.0.100:31703 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:13am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:13am LISTEN TCP 192.168.0.100:7194 0.0.0.0:0 Success msnmsgr.exe:1140
11:48:13am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:13am CONNECT TCP 192.168.0.100:29332 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:13am SEND TCP 192.168.0.100:29332 192.168.0.1:5678 Success 894 msnmsgr.exe:1140
11:48:14am RECEIVE TCP 192.168.0.100:29332 192.168.0.1:5678 Success 477 msnmsgr.exe:1140
11:48:14am CLOSE TCP 192.168.0.100:29332 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:17am SEND TCP 192.168.0.100:4428 207.46.108.63:1863 Success 490 msnmsgr.exe:1140 United States
11:48:17am RECEIVE TCP 192.168.0.100:4428 207.46.108.63:1863 Success 7 msnmsgr.exe:1140 United States
11:48:17am RECEIVE TCP 192.168.0.100:4428 207.46.108.63:1863 Success 442 msnmsgr.exe:1140 United States
11:48:17am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:17am CONNECT UDP 192.168.0.100:4431 68.117.60.0:64241 Success msnmsgr.exe:1140 United States
11:48:17am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:17am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:17am CONNECT UDP 192.168.0.100:4432 68.117.60.0:5060 Success msnmsgr.exe:1140 United States
11:48:17am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:17am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:17am CONNECT TCP 192.168.0.100:8212 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:17am SEND TCP 192.168.0.100:8212 192.168.0.1:5678 Success 896 msnmsgr.exe:1140
11:48:18am RECEIVE TCP 192.168.0.100:8212 192.168.0.1:5678 Success 477 msnmsgr.exe:1140
11:48:18am CLOSE TCP 192.168.0.100:8212 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:18am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:18am CONNECT TCP 192.168.0.100:9319 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:18am SEND TCP 192.168.0.100:9319 192.168.0.1:5678 Success 896 msnmsgr.exe:1140
11:48:19am RECEIVE TCP 192.168.0.100:9319 192.168.0.1:5678 Success 477 msnmsgr.exe:1140
11:48:19am CLOSE TCP 192.168.0.100:9319 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:19am CLOSE UDP 192.168.0.100:10663 0.0.0.0:0 Success msnmsgr.exe:1140
11:48:19am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:19am CONNECT TCP 192.168.0.100:42478 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:19am SEND TCP 192.168.0.100:42478 192.168.0.1:5678 Success 615 msnmsgr.exe:1140
11:48:19am RECEIVE TCP 192.168.0.100:42478 192.168.0.1:5678 Success 483 msnmsgr.exe:1140
11:48:19am CLOSE TCP 192.168.0.100:42478 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:19am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:19am CONNECT TCP 192.168.0.100:37794 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:19am SEND TCP 192.168.0.100:37794 192.168.0.1:5678 Success 615 msnmsgr.exe:1140
11:48:20am RECEIVE TCP 192.168.0.100:37794 192.168.0.1:5678 Success 483 msnmsgr.exe:1140
11:48:20am CLOSE TCP 192.168.0.100:37794 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:20am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:20am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:20am CONNECT TCP 192.168.0.100:19784 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:20am SEND TCP 192.168.0.100:19784 192.168.0.1:5678 Success 896 msnmsgr.exe:1140
11:48:21am RECEIVE TCP 192.168.0.100:19784 192.168.0.1:5678 Success 477 msnmsgr.exe:1140
11:48:21am CLOSE TCP 192.168.0.100:19784 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:21am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:21am CONNECT TCP 192.168.0.100:55468 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:21am SEND TCP 192.168.0.100:55468 192.168.0.1:5678 Success 896 msnmsgr.exe:1140
11:48:21am RECEIVE TCP 192.168.0.100:55468 192.168.0.1:5678 Success 477 msnmsgr.exe:1140
11:48:21am CLOSE TCP 192.168.0.100:55468 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:21am RECEIVE UDP 192.168.0.100:38921 0.0.0.0:0 Failed 0 msnmsgr.exe:1140
11:48:21am CONNECT UDP 192.168.0.100:4432 68.117.60.0:5060 Success msnmsgr.exe:1140 United States
11:48:21am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:21am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:21am CONNECT TCP 192.168.0.100:41930 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:21am SEND TCP 192.168.0.100:41930 192.168.0.1:5678 Success 896 msnmsgr.exe:1140
11:48:22am RECEIVE TCP 192.168.0.100:41930 192.168.0.1:5678 Success 477 msnmsgr.exe:1140
11:48:22am CLOSE TCP 192.168.0.100:41930 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:22am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:22am CONNECT TCP 192.168.0.100:45835 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:22am SEND TCP 192.168.0.100:45835 192.168.0.1:5678 Success 896 msnmsgr.exe:1140
11:48:23am RECEIVE TCP 192.168.0.100:45835 192.168.0.1:5678 Success 477 msnmsgr.exe:1140
11:48:23am CLOSE TCP 192.168.0.100:45835 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:23am CLOSE UDP 192.168.0.100:39309 0.0.0.0:0 Success msnmsgr.exe:1140
11:48:23am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:23am CONNECT TCP 192.168.0.100:27035 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:23am SEND TCP 192.168.0.100:27035 192.168.0.1:5678 Success 615 msnmsgr.exe:1140
11:48:23am RECEIVE TCP 192.168.0.100:27035 192.168.0.1:5678 Success 483 msnmsgr.exe:1140
11:48:23am CLOSE TCP 192.168.0.100:27035 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:23am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:23am CONNECT TCP 192.168.0.100:60598 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:23am SEND TCP 192.168.0.100:60598 192.168.0.1:5678 Success 615 msnmsgr.exe:1140
11:48:24am RECEIVE TCP 192.168.0.100:60598 192.168.0.1:5678 Success 483 msnmsgr.exe:1140
11:48:24am CLOSE TCP 192.168.0.100:60598 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:24am OPEN UDP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:24am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:24am CONNECT TCP 192.168.0.100:29458 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:24am SEND TCP 192.168.0.100:29458 192.168.0.1:5678 Success 896 msnmsgr.exe:1140
11:48:25am RECEIVE TCP 192.168.0.100:29458 192.168.0.1:5678 Success 477 msnmsgr.exe:1140
11:48:25am CLOSE TCP 192.168.0.100:29458 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:25am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:25am CONNECT TCP 192.168.0.100:34120 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:25am SEND TCP 192.168.0.100:34120 192.168.0.1:5678 Success 896 msnmsgr.exe:1140
11:48:25am RECEIVE TCP 192.168.0.100:34120 192.168.0.1:5678 Success 477 msnmsgr.exe:1140
11:48:25am CLOSE TCP 192.168.0.100:34120 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:25am RECEIVE UDP 192.168.0.100:38143 0.0.0.0:0 Failed 0 msnmsgr.exe:1140
11:48:25am SEND UDP 192.168.0.100:4431 68.117.60.0:64241 Success 1069 msnmsgr.exe:1140 United States
11:48:25am RECEIVE UDP 192.168.0.100:14821 0.0.0.0:0 Success 314 msnmsgr.exe:1140
11:48:25am RECEIVE UDP 192.168.0.100:14821 0.0.0.0:0 Success 315 msnmsgr.exe:1140
11:48:26am RECEIVE UDP 192.168.0.100:14821 0.0.0.0:0 Success 919 msnmsgr.exe:1140
11:48:26am CLOSE UDP 192.168.0.100:38143 0.0.0.0:0 Success msnmsgr.exe:1140
11:48:26am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:26am CONNECT TCP 192.168.0.100:52365 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:26am SEND TCP 192.168.0.100:52365 192.168.0.1:5678 Success 615 msnmsgr.exe:1140
11:48:27am RECEIVE TCP 192.168.0.100:52365 192.168.0.1:5678 Success 483 msnmsgr.exe:1140
11:48:27am CLOSE TCP 192.168.0.100:52365 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:27am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:27am CONNECT TCP 192.168.0.100:15877 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:27am SEND TCP 192.168.0.100:15877 192.168.0.1:5678 Success 615 msnmsgr.exe:1140
11:48:27am RECEIVE UDP 192.168.0.100:38921 0.0.0.0:0 Failed 44 msnmsgr.exe:1140
11:48:27am RECEIVE TCP 192.168.0.100:15877 192.168.0.1:5678 Success 483 msnmsgr.exe:1140
11:48:27am CLOSE TCP 192.168.0.100:15877 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:27am SEND UDP 192.168.0.100:4431 68.117.60.0:64241 Success 344 msnmsgr.exe:1140 United States
11:48:27am RECEIVE UDP 192.168.0.100:14821 0.0.0.0:0 Success 919 msnmsgr.exe:1140
11:48:27am SEND UDP 192.168.0.100:4431 68.117.60.0:64241 Success 344 msnmsgr.exe:1140 United States
11:48:27am RECEIVE UDP 192.168.0.100:14821 0.0.0.0:0 Success 919 msnmsgr.exe:1140
11:48:27am SEND UDP 192.168.0.100:4431 68.117.60.0:64241 Success 344 msnmsgr.exe:1140 United States
11:48:28am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 48 msnmsgr.exe:1140 United States
11:48:29am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 64 msnmsgr.exe:1140 United States
11:48:30am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 104 msnmsgr.exe:1140 United States
11:48:31am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 28 msnmsgr.exe:1140 United States
11:48:31am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 80 msnmsgr.exe:1140 United States
11:48:33am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 28 msnmsgr.exe:1140 United States
11:48:33am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 104 msnmsgr.exe:1140 United States
11:48:36am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 28 msnmsgr.exe:1140 United States
11:48:36am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 64 msnmsgr.exe:1140 United States
11:48:36am OPEN TCP 0.0.0.0:0 0.0.0.0:0 Success 0 msnmsgr.exe:1140
11:48:36am CONNECT TCP 192.168.0.100:58416 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:36am SEND TCP 192.168.0.100:58416 192.168.0.1:5678 Success 499 msnmsgr.exe:1140
11:48:37am RECEIVE TCP 192.168.0.100:58416 192.168.0.1:5678 Success 608 msnmsgr.exe:1140
11:48:37am CLOSE TCP 192.168.0.100:58416 192.168.0.1:5678 Success msnmsgr.exe:1140
11:48:38am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 28 msnmsgr.exe:1140 United States
11:48:38am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 116 msnmsgr.exe:1140 United States
11:48:42am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 28 msnmsgr.exe:1140 United States
11:48:42am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 80 msnmsgr.exe:1140 United States
11:48:42am SEND TCP 192.168.0.100:4417 207.46.107.49:1863 Success 5 msnmsgr.exe:1140 United States
11:48:42am RECEIVE TCP 192.168.0.100:4417 207.46.107.49:1863 Success 8 msnmsgr.exe:1140 United States
11:48:42am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 28 msnmsgr.exe:1140 United States
11:48:42am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 104 msnmsgr.exe:1140 United States
11:48:44am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 1 msnmsgr.exe:1140 United States
11:48:44am SEND TCP 192.168.0.100:4429 207.68.171.232:80 Success 264 msnmsgr.exe:1140 United States
11:48:44am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 1024 msnmsgr.exe:1140 United States
11:48:44am SEND UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:44am RECEIVE UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:44am RECEIVE TCP 192.168.0.100:4426 207.68.178.239:80 Success 1 msnmsgr.exe:1140 United States
11:48:44am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 1024 msnmsgr.exe:1140 United States
11:48:44am CLOSE TCP 192.168.0.100:4426 207.68.178.239:80 Success msnmsgr.exe:1140 United States
11:48:44am SEND UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:44am RECEIVE UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:44am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 356 msnmsgr.exe:1140 United States
11:48:44am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 1024 msnmsgr.exe:1140 United States
11:48:44am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 332 msnmsgr.exe:1140 United States
11:48:44am RECEIVE TCP 192.168.0.100:4429 207.68.171.232:80 Success 1 msnmsgr.exe:1140 United States
11:48:44am SEND UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:44am RECEIVE UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:44am SEND UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:44am RECEIVE UDP 127.0.0.1:4418 127.0.0.1:4418 Success 1 msnmsgr.exe:1140
11:48:44am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 28 msnmsgr.exe:1140 United States
11:48:44am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 116 msnmsgr.exe:1140 United States
11:48:46am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 28 msnmsgr.exe:1140 United States
11:48:46am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 64 msnmsgr.exe:1140 United States
11:48:47am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 28 msnmsgr.exe:1140 United States
11:48:47am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 104 msnmsgr.exe:1140 United States
11:48:49am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 28 msnmsgr.exe:1140 United States
11:48:49am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 80 msnmsgr.exe:1140 United States
11:48:52am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 28 msnmsgr.exe:1140 United States
11:48:52am SEND UDP 192.168.0.100:38921 68.117.60.0:58711 Success 104 msnmsgr.exe:1140 United States
11:48:52am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 28 msnmsgr.exe:1140 United States
11:48:52am RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 64 msnmsgr.exe:1140 United States

 

[Mikke]

FOLLOW-UP QUESTION:

For a moment, lets assume the Port is not being established for the voice to ravel the other way.

If this is true, how would you open the Port on the XPPro box. Since no routers are involved.

(i.e. Another box was tested via the same cable modem and all works well) It is clear that the problem resides on the XP Pro box.

Thanks again.

 

[linney]

Double check to see if this applies.

308127 - How to Manually Open Ports in Internet Connection Firewall in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;308127&FR=1&PA=1&SD=HSCH

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q308127

If the Settings button is unavailable, ICF is not enabled on this connection and you do not have to open any ports (they are all already open).



What are all these Failures in your log?

RECEIVE UDP 192.168.0.100:38921 68.117.60.0:58711 Failed 28 msnmsgr.exe:1140 United States

 

[Mikke]

UGGGG! I can't beleive that I missed that! The Firewall is set on the XPPro computer, however, I won't beleive that I will be able to test it until Tuesday morning!!!

I'm sure that's it!!!

Regarding the FAILED, I'm not sure yet, I still looking into it. It appears to have little or no effect on the services that are running since we don't notice it.

The FAILED was occuring when voice was not active.

Till next week.

THANKS ALOT FOR ALL OF THE SUPPORT AND HELP!!!!

 

[Mikke]

No luck. We turned off the Firewall and we still have the problem.

I am just simply lost.

Any other ideas?

 

[linney]

Have you rebooted since turning the Firewall off?

 

[Mikke]

Yes. Several times.

 

[Mikke]

WELL WE FOUND THE PROBLEM!!!!

We turned off QoS Scheduler in the Network Properties. It turns out the new ITEL Comm cards are set to the new TCP/IPv6.

Thanks for the help.

HOWEVER NEW PROBLEM: All is the same both ends running 6.1 MSN and now we are getting the following message when we start application sharing. Voice is fine.

There is an unknown problem.

A problem occured while you were trying to place the call. Restart the program and try again.

Error 0x80ee000b
No media is available for this session.

I AM GOING NUTS!!!

 

[linney]

Is Remote Assistance enabled in System Properties/ Remote?

Some similar stories here but not too much help.

http://groups.google.com/groups?hl=...dia+is+available+for+this+session&sa=N&tab=wg

 

[Mikke]

We turned it off and no luck. But an interesting thing is happenning.

If a computer that does work tries to start the application sharing the process, the applciation sharing fails with the following error message.

The programs are not compatible.

The person you are trying to contact may not be running a compatible program. Check that the person you are trying to contact is running a compatible program, and then try again later.

Status code 488 has been returned by the SIP Stack.

We are both running the very latest program, MSN Messenger 6.1 on XP Pro with all the latest patches.

I am going crazy

Thanks for all of your help.

 

[linney]

I think you have to have Remote Assistance on (not turned off). Can you get Remote Assistance working between both of you?

830550 - SIP Communications Service Account Does Not Appear in Windows Messenger 5.0 After You Configure Fixed Port Assignments

http://support.microsoft.com/default.aspx?scid=kb;en-us;830550&FR=1&PA=1&SD=HSCH

http://groups.google.com/groups?hl=...22Status+code+488%22%2Bwhiteboard&sa=N&tab=wg

http://groups.google.com/groups?hl=...avclient&ie=UTF-8&oe=UTF-8&q=sip%2Bwhiteboard

I include this article as it relates to this thread (but not to your already solved problem from earlier).

834481 - Audio or video only works in one direction in a real-time communication session

http://support.microsoft.com/default.aspx?scid=kb;en-us;834481&FR=1&PA=1&SD=HSCH

 

[Mikke]

Remote Assistance works. Were looking at the ports and see no overlaps.

 

[linney]

http://messenger.msn.com/Help/

http://help.msn.com/EN_US/HelpWindow_msg.asp?INI=Messengerv61XP.ini&H_VER=1.7

From the above sites you get these comments - About having two Messenger programs on your computer.

Some programs, such as Outlook, Outlook Express, and Remote Assistance, connect to Windows Messenger by default. When you are signed in to MSN Messenger, you may appear offline to people who connect to these programs and have you listed as a contact.

Both computers need the most recent version of Windows Messenger installed. Windows Messenger is a feature in Windows XP, and it works in conjunction with MSN Messenger to provide application sharing.

I'm not sure of the relevance of these comments as I have only used XP's Window's Messenger not MSN. Do you have to sign in to both versions of Messenger with different accounts to get everything to work properly? And if you haven't Window's XP Messenger running, should it be running?

Have you thought about getting this sorted via Microsoft?

http://messenger.msn.com/Help/ContactUs.aspx

 

[Mikke]

Thanks for all of the help.

We appreciate ALL of your assistance. It is by far the most support that we have gotten.

I think we are at a point of "Frustration" that we need to regroup and begin taking it one building block at a time.

We got voice working ONLY BECAUSE OF YOUR HELP

Let me play a little more over the next several days and I will get back to you to update you on our findings. I wnat to make sure that you get all of our solutions that YOU are the king of knowledge on MSN Messenger.

Thanks again, see you soon with results!!!

 

[tviman]

Forget Messenger and download FireFly at

http://www.virbiage.com.

Great tool, easy to set up, and it's free!

There's always a better way. The fun is trying to find it!

 

[evalesthy]

Mikke - there is much posted here - but did you ever nail down the basic source and fix of your problem? Thanks.