Cannot Make Voice or Video (V&V) with Messenger 4.7, 5, or 6

[Mark Abrams]

Config: XP Professional, no fire wall, network or direct
cable modem (comcast) connection.

Chat works.
voice and video (V&V) do not work
I recieve a message that the network I am trying to cooect
to is having dificulties.
However, on a 2nd PC I have no dificulties.

This PC worked fine last week before reformating and
reloading XP. I am convinced I have an OS config problem
or one of the new MS updates has caused a conflict.

What do I need to do to fix V&V?


I have read the knowlege base (see below) and still have a
problem with V&V on a new PC. However, I am able to
useV&V on a second PC without a problem so my network and
provide are not blocking any UDPs.


You Cannot Make Phone Calls or Start Voice or Video
Conversations with Windows Messenger
The information in this article applies to:
Microsoft Windows Messenger 4.0
Microsoft Windows Messenger 4.5
Microsoft Windows Messenger 4.6
Microsoft Windows XP Professional
Microsoft Windows XP Home Edition

This article was previously published under Q324214
SYMPTOMS
You may not be able to make phone calls or start voice or
video conversations with Windows Messenger. For example,
you may receive the following error message when you try
to make a phone call:

Your network is configured such that you can not make
phone calls.
CAUSE
This behavior may occur for any of the following reasons:
You are not running the latest version of Windows
Messenger or you have not applied Windows XP Real-Time
Communication Client Support for Network Address
Translation (NAT).
You are running the Zone Labs ZoneAlarm program.
Your home or corporate network or ISP uses a firewall or
NAT device that does not support Universal Plug and Play
(UPnP).

 

[richard]

Do you have an intel network card?

 

[Mark Abrams]

YES, Intel PRO / 100

-----Original Message-----
Do you have an intel network card?
.

 

[richard]

That is your problem most likely. Many of us have the
same problem and Microsoft and intel will not address
it. I have spoekn extensively with customer support at
both companies and they both point the finger at the
other. You can look back through the threads and try the
things that people tell you but my bet is that you will
have to replace your network card.

 

[richard]

However, if you can, you might try reverting to an older
driver version as some people have had success with that.

 

[Mark Abrams]

This computer worked fine 2 weeks ago - voice & video and
the same network card was used.

When I rebuilt the PC the same install cd was used and the
same network drivers were used.

I can recieve V&V but I can not send. Why would a network
drive do only half the job?

 

[richard]

All I can tell you is that people with Intel network
cards have the identical problem including myself and
those who can use an older driver fixed the problem. I
cannot do so because my card is new and no older driver
is available. And after you did the install with the
disk did the windows site then upgrade your driver?
Those who replaced their network cards also fixed the
problem. You can go back though and find the threads and
read for yourself. If you figure out a fix please temm
us.

 

[Mark Abrams]

Richard, Thank you. I checked the driver for the Intel
PRO/100 VE and found it was dated 3/4/03 - I then
rolled back the driver to the original dated 2/25/02.

I found that I had upgraded the driver from the MS Windows
Update / Driver Update section "Intel network software
update released on March 04 2003."
Download size: 152 KB, < 1 minute

I also downloaded direct x 9. I will isolate the problem -
I am 99% confident that the driver is the problem. Once
confirmed I will notify Intel.

Thank you again.
Mark

 

[richard]

No problem glad you fixed it. As I said I have been
going around and around with this for a month now with no
resolution as my card is new and built onto the board. I
paid MS technical support but when they could not fix it
I got my money back at least. I have another network
card I could easily put in but don't think I should have
to do that when it is a known problem that they should
have fixed already. They just ignore me now on here! I
have talked with intel and Microsoft but they just refuse
to do anything. At one point a member of the Messenger
team said he would look at it but we never heard another
word out of him. It is clearly the driver though.