mike
October 2nd 06, 08:03 AM
I am having trouble getting MSN Messenger's shared services (App Sharing,
Whiteboard, and Remote Assistance) working behind a newly added LinkSys
BEFSX41 UPnP NAT Router/Firewall and have just about run out of things to
try. The config is as follows:
Side A has a Comcast cable modem, the newly added Linksys UPnP router, and a
PC running Win XP, MSN Messenger 7.5.0324, Windows Messenger 5.1.07 (for
Shared app support which is not enabled to run either in foreground or the
background), and DirectX 9.0c.
Side B has a RoadRUnner cable Modem and a NetGear FR114P UPnP FW/Router and
the same software as side A.
Configured per above, everything works (including video, voice, and file
sharing)
except for shared services (App Sharing, Whiteboard, and Remote Assistance)
which won't start. If the Linksys router on side A is removed, all the shared
services work properly between the systems. Removing the NetGear router at
side B has no effect. Remote Desktop (outside of MSN) works fine with both
routers in place. The problem seems to be with session initiation stalling.
The following things have been verified on both sides:
The XP Internet Gateway Device Discovery and UPnP user interface software
are installed. The XP firewall is disabled (just to be sure), and the SSDP
DIscovery and UPnP Hosting Services are in Auto and started. UPnP is enabled
on both routers which have the latest software versions. Both machines show
the Internet Connection icon in the Network Connections window and both MSN
Messenger clients indicate they are connected through a UPnP Restricted NAT
as administrators so UPnP services appear to be running at both ends. The
following related XP services are confirmed running: NetMeeting Remote
Desktop Sharing, Remote Desktop Help Session Mgr, SSDP Discovery, and UPnP
Device Host.
In addition to UPnP enabled, the LinkSys router has ports 1503, 1863, 3389,
and 6891-6901 ports forwarded and even turning on its DMZ feature which opens
all internet ports has been tried with no success.
The symptoms are curiously asymmetric but both directions stall during the
shared service initiation process. When A invites a Whiteboard session and B
accepts it, A goes to Waiting in the service startup window and stalls on
Waiting... without ever loading the app. Nothing happens at B.
When B invites a whiteboard session and A accepts, B never gets A's
acceptance on Messenger and nothing at all happens on either end and the
Invite from B eventually times out (both on the UI and confirmed with the MSN
Messenger log file).
Is there anything I might have missed? Isn't this configuration what UPnP
is supposed to support? Why does the session initiation hang on shared
services? How I can get this to work short of chucking the Linksys and
hoping another NetGear will work?
Whiteboard, and Remote Assistance) working behind a newly added LinkSys
BEFSX41 UPnP NAT Router/Firewall and have just about run out of things to
try. The config is as follows:
Side A has a Comcast cable modem, the newly added Linksys UPnP router, and a
PC running Win XP, MSN Messenger 7.5.0324, Windows Messenger 5.1.07 (for
Shared app support which is not enabled to run either in foreground or the
background), and DirectX 9.0c.
Side B has a RoadRUnner cable Modem and a NetGear FR114P UPnP FW/Router and
the same software as side A.
Configured per above, everything works (including video, voice, and file
sharing)
except for shared services (App Sharing, Whiteboard, and Remote Assistance)
which won't start. If the Linksys router on side A is removed, all the shared
services work properly between the systems. Removing the NetGear router at
side B has no effect. Remote Desktop (outside of MSN) works fine with both
routers in place. The problem seems to be with session initiation stalling.
The following things have been verified on both sides:
The XP Internet Gateway Device Discovery and UPnP user interface software
are installed. The XP firewall is disabled (just to be sure), and the SSDP
DIscovery and UPnP Hosting Services are in Auto and started. UPnP is enabled
on both routers which have the latest software versions. Both machines show
the Internet Connection icon in the Network Connections window and both MSN
Messenger clients indicate they are connected through a UPnP Restricted NAT
as administrators so UPnP services appear to be running at both ends. The
following related XP services are confirmed running: NetMeeting Remote
Desktop Sharing, Remote Desktop Help Session Mgr, SSDP Discovery, and UPnP
Device Host.
In addition to UPnP enabled, the LinkSys router has ports 1503, 1863, 3389,
and 6891-6901 ports forwarded and even turning on its DMZ feature which opens
all internet ports has been tried with no success.
The symptoms are curiously asymmetric but both directions stall during the
shared service initiation process. When A invites a Whiteboard session and B
accepts it, A goes to Waiting in the service startup window and stalls on
Waiting... without ever loading the app. Nothing happens at B.
When B invites a whiteboard session and A accepts, B never gets A's
acceptance on Messenger and nothing at all happens on either end and the
Invite from B eventually times out (both on the UI and confirmed with the MSN
Messenger log file).
Is there anything I might have missed? Isn't this configuration what UPnP
is supposed to support? Why does the session initiation hang on shared
services? How I can get this to work short of chucking the Linksys and
hoping another NetGear will work?