Re: NAT traversal problem with Messenger RA.
- From: "Jason Tsang" <jason-onlineDEL@xxxxxxxxxxx>
- Date: Thu, 9 Mar 2006 02:31:51 -0500
Have you tried upgrading to Windows Messenger 5.1?
Windows Messenger 5.1
http://www.microsoft.com/downloads/details.aspx?FamilyID=a8d9eb73-5f8c-4b9a-940f-9157a3b3d774&DisplayLang=en
--
Jason Tsang - Microsoft MVP
Find out about the MS MVP Program -
http://mvp.support.microsoft.com/default.aspx
"Richard Jones" <nobody@xxxxxxxxxxx> wrote in message
news:usD3$Y0QGHA.1688@xxxxxxxxxxxxxxxxxxxxxxx
I'm stumped with a Remote Assistance via Messenger problem. I
have a simple network behind a UPnP enabled Linksys router with two
machines on it. I can do over an RA over the internet to one machine but
not the other. Looking at remote assistance event logs, on one machine,
Messenger gets the public WAN side IP address and sends that, but on the
other machine it fails to get the true public IP and just sends the
192.168.xxx.xxx private IP.
I got to Googling and discovered that Messenger 4.7 uses
DirectPlay for NAT traversal, and not the SSDP discovery service which the
"Internet Gateway" icon in Network Connections uses for UPnP enabled
routers. The Gateway interface works fine and allows you to manually
foward ports via UPnP and all that. But Direct Play is apparently failing
to do the same thing on one machine.
Any ideas on what could be wrong. I'm at my wit's end here.
-Richard
.
- Follow-Ups:
- Re: NAT traversal problem with Messenger RA.
- From: Richard Jones
- Re: NAT traversal problem with Messenger RA.
- From: Richard Jones
- Re: NAT traversal problem with Messenger RA.
- References:
- NAT traversal problem with Messenger RA.
- From: Richard Jones
- NAT traversal problem with Messenger RA.
- Prev by Date: NAT traversal problem with Messenger RA.
- Next by Date: Never give out you password or credit ... in MSN Messenger
- Previous by thread: NAT traversal problem with Messenger RA.
- Next by thread: Re: NAT traversal problem with Messenger RA.
- Index(es):
Relevant Pages
|
|
