:? Ok guys I know a little about IPs,TCP,UDP, and routers but this one has me stumped. I can not use my voice chat on windows messenger 4.7 now. I think it is due to a shared file with the new version of MSN 6. I could use the voice chat priot to that. I have tried to open all the suggest ports and have seen articles one opening more ports but there a lot and I am not sure if this is what I need to do. I know LFM and some of you guys are well versed in this type stuff and any help would be appreciated!

 

Here is what I have:

 

DSL modem connected to a Linksys BEFW11S4 V.2 with firmware version 1.45. I am also running WinXP Pro and CAN use UPnP to my router however I do not like to or at least when gaming...It causes real bad pink spikes even when HL ports or opened completely.

 

I have opened the following ports with no succes:

 

IN TCP 6891 - 6900

 

IN TCP 1863

 

IN UDP 1863

 

IN UDP 5190

 

IN UDP 6901

 

IN TCP 6901

 

I have found a article at MS http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/deploy/worki01.asp

 

Part of the article says the following but I am not so sure 60,531+ ports being opened:

 

Audio and Video

 

When negotiating an audio-video session, dynamic ports were chosen for the audio-video (AV) stream. Dynamic ports are used to enable the application to work regardless of what other applications are running on the system and using port resources. In the .NET Messenger case the session invitation was sent by station B to the address it received for station A.

 

The following issues might arise if a firewall or NAT were present in these scenarios:

 

The address provided by A in either the session invite for session signaling, or in the session acceptance for the UDP streams, might be an internal address that is translated by a NAT device an invalid (or fake) address for B to use to contact A. In other scenarios with the 4.5 client, A might initiate the session, but the same or similar addressing issues will exist.

 

When B sends the session invitation to A, this invitation is sent using the IP address and port passed from A to B. For this to work, this port must be enabled to pass through any firewall between A and B.

 

The actual Real-time Transport Protocol (RTP) streams are sent using dynamically allocated UDP ports in the range of 5004 65535. Without a way to open these UDP ports on any firewall in the path dynamically, the streams will fail to reach their destination.

Hm...I'd update to MSN 6.0. Also, maybe open port 8000-8001? I've heard that port was used for broadcasting, and voice chat is sort of broadcasting.

to get my 6.0 to work i took 4.7 off my computer and downloaded the verison 6.0 .go to control panel then add and remove windows components i think this will work for you

I will try that...but I like the windows messenger better.

6.0 is awesomeit lets u add pics to ur convs and webcam convs and lotsa more smilelys!

Windows Messenger also has those annoying pop-ups, yes I know how to disable them, but I'd rather leave it shut off to avoid the risk.MSN Messenger > Windows Messenger.

Paradigm: Windows Messenger is NOT the cause of those popups. Silly Microsoft named the process and the program similarly, but, again, Windows Messenger does NOT cause the popups.StateCop: On October 15th, every MSN Messenger User will have to have 6.0 or higher anyway. better go ahead and bite the bullet on that bit, yo'.

-StateCop]I will try that...but I like the windows messenger better.

 

they are the same darn thing cop MICRO CRAP has just made it so it works independent of the OS,,Same thing differant name windows messenger is now MSN Messenger ver 6.0

They maybe the same thing which you are right basically they are BUT the new one doesnt work for me.

-StateCop]They maybe the same thing which you are right basically they are BUT the new one doesnt work for me.

 

Ok, let me know it turns out ,,