Does Messenger work as documented or NOT?

[JimC]

I am using OEM-installed Win XP Pro (with all Windows
Updates applied).

I have Windows Messenger Version 4.7 (4.7.2009).

My Internet connection is from NIC to cable-modem
(stand-alone system).

When I activate XP ICF, only the following four ports show
up as ENABLED:
(1) msmsgs (11185 TCP)
(2) msmsgs (12253 UDP)
(3) msmsgs (15311 TCP)
(4) Windows Media Player SDK (3233 UDP)

Since XP ICF is a PnP firewall, why isn't Messenger
configuring ICF to open additional ports? After scouring
<Help & Support> I cannot conclude that any manual
intervention is SUPPOSED to be required in order to open
ports for file transfers, voice, video, whiteboard, etc.

Is the <Help & Support> documentation ICF and Messenger
simply wrong?

What is required?

Are users expected to manually open and close ports before
and after using Messenger features? I should hope not.

Thanks, Jim

[Jonathan Kay [MVP]]

Greetings Jim,

Messenger and the ICF both support Universal Plug and Play (UPnP), which yes, will open the
correct ports -- however, file transfer in Windows Messenger does not support UPnP enabled
file transfer, and as such, the ports do have to be opened manually.

As well, although MSN Messenger 5 supports UPnP file transfer, it does so only for routers
and NATs (IGD), and not the Internet Connection Firewall, so the ports have to be opened
manually for Messenger 5 as well.
____________________________________________
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

"JimC" > wrote in message ...
> I am using OEM-installed Win XP Pro (with all Windows
> Updates applied).
>
> I have Windows Messenger Version 4.7 (4.7.2009).
>
> My Internet connection is from NIC to cable-modem
> (stand-alone system).
>
> When I activate XP ICF, only the following four ports show
> up as ENABLED:
> (1) msmsgs (11185 TCP)
> (2) msmsgs (12253 UDP)
> (3) msmsgs (15311 TCP)
> (4) Windows Media Player SDK (3233 UDP)
>
> Since XP ICF is a PnP firewall, why isn't Messenger
> configuring ICF to open additional ports? After scouring
> <Help & Support> I cannot conclude that any manual
> intervention is SUPPOSED to be required in order to open
> ports for file transfers, voice, video, whiteboard, etc.
>
> Is the <Help & Support> documentation ICF and Messenger
> simply wrong?
>
> What is required?
>
> Are users expected to manually open and close ports before
> and after using Messenger features? I should hope not.
>
> Thanks, Jim
>
>

[JimC]

Thanks Jonathan,

I assume from your helpful post that if I manually open some
or all of ports 6891-6900 for TCP, this will enable file
transfers via Messenger.

What about voice, video, and whiteboard? Will UPnP
compatibility between ICF and Messenger cause the
appropriate ports to be opened and closed in response to
specific service requests as I use Messenger?

--Jim
"Jonathan Kay [MVP]" > wrote
in message ...
> Greetings Jim,
>
> Messenger and the ICF both support Universal Plug and Play
(UPnP), which yes, will open the
> correct ports -- however, file transfer in Windows
Messenger does not support UPnP enabled
> file transfer, and as such, the ports do have to be opened
manually.
>
> As well, although MSN Messenger 5 supports UPnP file
transfer, it does so only for routers
> and NATs (IGD), and not the Internet Connection Firewall,
so the ports have to be opened
> manually for Messenger 5 as well.
> ____________________________________________
> Jonathan Kay
> Windows MVP, Messenger
> Associate Expert
> http://www.microsoft.com/windowsxp/expertzone/
> Messenger Resources - http://messenger.jonathankay.com
>
> "JimC" > wrote in message
...
> > I am using OEM-installed Win XP Pro (with all Windows
> > Updates applied).
> >
> > I have Windows Messenger Version 4.7 (4.7.2009).
> >
> > My Internet connection is from NIC to cable-modem
> > (stand-alone system).
> >
> > When I activate XP ICF, only the following four ports
show
> > up as ENABLED:
> > (1) msmsgs (11185 TCP)
> > (2) msmsgs (12253 UDP)
> > (3) msmsgs (15311 TCP)
> > (4) Windows Media Player SDK (3233 UDP)
> >
> > Since XP ICF is a PnP firewall, why isn't Messenger
> > configuring ICF to open additional ports? After
scouring
> > <Help & Support> I cannot conclude that any manual
> > intervention is SUPPOSED to be required in order to open
> > ports for file transfers, voice, video, whiteboard, etc.
> >
> > Is the <Help & Support> documentation ICF and Messenger
> > simply wrong?
> >
> > What is required?
> >
> > Are users expected to manually open and close ports
before
> > and after using Messenger features? I should hope not.
> >
> > Thanks, Jim
> >
> >
>
>

[Jonathan Kay [MVP]]

Hi Jim,

The whiteboard/app sharing, Remote Assistance, voice/video should automatically have the
ports opened, no configuration necessary.
____________________________________________
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

"JimC" > wrote in message ...
> Thanks Jonathan,
>
> I assume from your helpful post that if I manually open some
> or all of ports 6891-6900 for TCP, this will enable file
> transfers via Messenger.
>
> What about voice, video, and whiteboard? Will UPnP
> compatibility between ICF and Messenger cause the
> appropriate ports to be opened and closed in response to
> specific service requests as I use Messenger?
>
> --Jim
> "Jonathan Kay [MVP]" > wrote
> in message ...
> > Greetings Jim,
> >
> > Messenger and the ICF both support Universal Plug and Play
> (UPnP), which yes, will open the
> > correct ports -- however, file transfer in Windows
> Messenger does not support UPnP enabled
> > file transfer, and as such, the ports do have to be opened
> manually.
> >
> > As well, although MSN Messenger 5 supports UPnP file
> transfer, it does so only for routers
> > and NATs (IGD), and not the Internet Connection Firewall,
> so the ports have to be opened
> > manually for Messenger 5 as well.
> > ____________________________________________
> > Jonathan Kay
> > Windows MVP, Messenger
> > Associate Expert
> > http://www.microsoft.com/windowsxp/expertzone/
> > Messenger Resources - http://messenger.jonathankay.com
> >
> > "JimC" > wrote in message
> ...
> > > I am using OEM-installed Win XP Pro (with all Windows
> > > Updates applied).
> > >
> > > I have Windows Messenger Version 4.7 (4.7.2009).
> > >
> > > My Internet connection is from NIC to cable-modem
> > > (stand-alone system).
> > >
> > > When I activate XP ICF, only the following four ports
> show
> > > up as ENABLED:
> > > (1) msmsgs (11185 TCP)
> > > (2) msmsgs (12253 UDP)
> > > (3) msmsgs (15311 TCP)
> > > (4) Windows Media Player SDK (3233 UDP)
> > >
> > > Since XP ICF is a PnP firewall, why isn't Messenger
> > > configuring ICF to open additional ports? After
> scouring
> > > <Help & Support> I cannot conclude that any manual
> > > intervention is SUPPOSED to be required in order to open
> > > ports for file transfers, voice, video, whiteboard, etc.
> > >
> > > Is the <Help & Support> documentation ICF and Messenger
> > > simply wrong?
> > >
> > > What is required?
> > >
> > > Are users expected to manually open and close ports
> before
> > > and after using Messenger features? I should hope not.
> > >
> > > Thanks, Jim
> > >
> > >
> >
> >
>
>