Archived from groups: microsoft.public.broadbandnet.hardware (More info?)
Application triggered is only if you send on one port range & get a
response on a different range such as FTP, SMTP, or POP3. For your
application and most applications you need persistent port forwarding.
Also in the application triggered you can in that one field enter ranges.
Ron Bower wrote:
> I'm using an MN-100 Base Station with a cable modem and a
> PC running XP. I use MSN Messenger for audio
> communications with family members.
>
> The MN-100 Firewall is stopping MSN Messenger from
> connecting with remote PCs for audio communications.
>
> A message from the MSN Messenger help desk states:
> "you need to open 5004-65535 UDP ports in order to allow
> audio capabilities for MSN Messenger"
>
> 1. I assume they mean "application-triggered port
> forwarding". Is that correct ?
>
> 2. The firewall setup screen anly allows me to enter one
> outbound port at a time -- I'm not sure I can make
> 60,000+ entries.
>
> How do I setup the firewall for used with MSG Messenger
> audio capabilities ?
>
> ronbower@comcast.net
>
Archived from groups: microsoft.public.broadbandnet.hardware (More info?)
Actually, the latest versions of MSN Messenger
automatically open the ports (you can see in the security
logs).
Make sure that you are not running a software firewall on
one of the PCs (would need to open ports in that firewall
then, not the router).
>-----Original Message-----
>I'm using an MN-100 Base Station with a cable modem and
a
>PC running XP. I use MSN Messenger for audio
>communications with family members.
>
>The MN-100 Firewall is stopping MSN Messenger from
>connecting with remote PCs for audio communications.
>
>A message from the MSN Messenger help desk states:
>"you need to open 5004-65535 UDP ports in order to allow
>audio capabilities for MSN Messenger"
>
>1. I assume they mean "application-triggered port
>forwarding". Is that correct ?
>
>2. The firewall setup screen anly allows me to enter one
>outbound port at a time -- I'm not sure I can make
>60,000+ entries.
>
>How do I setup the firewall for used with MSG Messenger
>audio capabilities ?
>
>ronbower@comcast.net
>
>.
>
Archived from groups: microsoft.public.broadbandnet.hardware (More info?)
>-----Original Message-----
>Actually, the latest versions of MSN Messenger
>automatically open the ports (you can see in the security
>logs).
>
>Make sure that you are not running a software firewall on
>one of the PCs (would need to open ports in that firewall
>then, not the router).
>
>>-----Original Message-----
>>I'm using an MN-100 Base Station with a cable modem and
>a
>>PC running XP. I use MSN Messenger for audio
>>communications with family members.
>>
>>The MN-100 Firewall is stopping MSN Messenger from
>>connecting with remote PCs for audio communications.
>>
>>A message from the MSN Messenger help desk states:
>>"you need to open 5004-65535 UDP ports in order to allow
>>audio capabilities for MSN Messenger"
>>
>>1. I assume they mean "application-triggered port
>>forwarding". Is that correct ?
>>
>>2. The firewall setup screen anly allows me to enter one
>>outbound port at a time -- I'm not sure I can make
>>60,000+ entries.
>>
>>How do I setup the firewall for used with MSG Messenger
>>audio capabilities ?
>>
>>ronbower@comcast.net
>>
>>.
>>
>.
>Thanks for that info. Actually, I've been running Zone
Alarm Pro for a long time and usually just turn it off
when I make a voice conversation. I did that, but still
could not connect to the distant PC.
This is becoming very frustrating and hope that the group
here can help me out. I will try the last suggestion and
hope to test this weekend.
Archived from groups: microsoft.public.broadbandnet.hardware (More info?)
I said it before I'll say it again since you were not reading my
previous post.
(Begin copy of my previous post to you on this issue.)
"Application triggered is only if you send on one port range & get a
response on a different range such as FTP, SMTP, or POP3.
For your application and most applications you need persistent port
forwarding.
Also in the application triggered you can in that one field enter ranges."
(End copy of my previous post to you on this issue.)
What that means is you want to browse to
http://192.168.2.1/persistent_port_forwarding.htm and enter in one line
the required information. If you need help there are directions on
configuring "Persistent Port Forwarding" in the manual.
Ron Bower wrote:
>>-----Original Message-----
>>Actually, the latest versions of MSN Messenger
>>automatically open the ports (you can see in the security
>>logs).
>>
>>Make sure that you are not running a software firewall on
>>one of the PCs (would need to open ports in that firewall
>>then, not the router).
>>
>>
>>>-----Original Message-----
>>>I'm using an MN-100 Base Station with a cable modem and
>>
>>a
>>
>>>PC running XP. I use MSN Messenger for audio
>>>communications with family members.
>>>
>>>The MN-100 Firewall is stopping MSN Messenger from
>>>connecting with remote PCs for audio communications.
>>>
>>>A message from the MSN Messenger help desk states:
>>>"you need to open 5004-65535 UDP ports in order to allow
>>>audio capabilities for MSN Messenger"
>>>
>>>1. I assume they mean "application-triggered port
>>>forwarding". Is that correct ?
>>>
>>>2. The firewall setup screen anly allows me to enter one
>>>outbound port at a time -- I'm not sure I can make
>>>60,000+ entries.
>>>
>>>How do I setup the firewall for used with MSG Messenger
>>>audio capabilities ?
>>>
>>>ronbower@comcast.net
>>>
>>>.
>>>
>>
>>.
>>Thanks for that info. Actually, I've been running Zone
>
> Alarm Pro for a long time and usually just turn it off
> when I make a voice conversation. I did that, but still
> could not connect to the distant PC.
>
> This is becoming very frustrating and hope that the group
> here can help me out. I will try the last suggestion and
> hope to test this weekend.
>
> Thanks again.
>
Archived from groups: microsoft.public.broadbandnet.hardware (More info?)
Thank you. I have set the persistent port forwarding as
you suggest and hope to test this weekend.
>-----Original Message-----
>I said it before I'll say it again since you were not
reading my
>previous post.
>
>(Begin copy of my previous post to you on this issue.)
>
>"Application triggered is only if you send on one port
range & get a
>response on a different range such as FTP, SMTP, or POP3.
>
>For your application and most applications you need
persistent port
>forwarding.
>
>Also in the application triggered you can in that one
field enter ranges."
>
>(End copy of my previous post to you on this issue.)
>
>What that means is you want to browse to
>http://192.168.2.1/persistent_port_forwarding.htm and
enter in one line
>the required information. If you need help there are
directions on
>configuring "Persistent Port Forwarding" in the manual.
>
>Ron Bower wrote:
>
>>>-----Original Message-----
>>>Actually, the latest versions of MSN Messenger
>>>automatically open the ports (you can see in the
security
>>>logs).
>>>
>>>Make sure that you are not running a software firewall
on
>>>one of the PCs (would need to open ports in that
firewall
>>>then, not the router).
>>>
>>>
>>>>-----Original Message-----
>>>>I'm using an MN-100 Base Station with a cable modem
and
>>>
>>>a
>>>
>>>>PC running XP. I use MSN Messenger for audio
>>>>communications with family members.
>>>>
>>>>The MN-100 Firewall is stopping MSN Messenger from
>>>>connecting with remote PCs for audio communications.
>>>>
>>>>A message from the MSN Messenger help desk states:
>>>>"you need to open 5004-65535 UDP ports in order to
allow
>>>>audio capabilities for MSN Messenger"
>>>>
>>>>1. I assume they mean "application-triggered port
>>>>forwarding". Is that correct ?
>>>>
>>>>2. The firewall setup screen anly allows me to enter
one
>>>>outbound port at a time -- I'm not sure I can make
>>>>60,000+ entries.
>>>>
>>>>How do I setup the firewall for used with MSG
Messenger
>>>>audio capabilities ?
>>>>
>>>>ronbower@comcast.net
>>>>
>>>>.
>>>>
>>>
>>>.
>>>Thanks for that info. Actually, I've been running Zone
>>
>> Alarm Pro for a long time and usually just turn it off
>> when I make a voice conversation. I did that, but
still
>> could not connect to the distant PC.
>>
>> This is becoming very frustrating and hope that the
group
>> here can help me out. I will try the last suggestion
and
>> hope to test this weekend.
>>
>> Thanks again.
>>
>
>.
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.