| Author |
Message |
Ickis99
Guest
|
 Posted:
Tue Mar 22, 2005 2:05 pm Post subject:
Netmeeting Remote Desktop Sharing over Firewall |
|
|
Hi!
I try to establish a Netmeeting Remote Desktop Connection to different
Clients. My job is to open all ports on the client firewall to make
this connection possible. The MS Knowledgebase says that only Port
3389 is necessary to use Remote Desktop Sharing. But i see that he
always uses the port 1720 and many others. Furthermore he uses dynamic
UDP-Ports due to the H.323 Protocol.
As far as i know H.323 is only used for Audio/Video Conferencing which
i dont need. Of course i do not want to open the whole 1024-65xxx port
range. My question is, how can i convince Netmeeting to use only the
Ports that are needed for the Remote Desktop Connection?
Thanks in advance.
Regards
Jürgen Winter |
|
| Back to top |
|
 |
Brian Sullivan MVP
Guest
|
| Posted:
Tue Mar 22, 2005 7:27 pm Post subject:
Re: Netmeeting Remote Desktop Sharing over Firewall |
|
|
On Tue, 22 Mar 2005 10:05:39 +0100, Ickis99 wrote:
| Quote: | Hi!
I try to establish a Netmeeting Remote Desktop Connection to different
Clients. My job is to open all ports on the client firewall to make
this connection possible. The MS Knowledgebase says that only Port
3389 is necessary to use Remote Desktop Sharing. But i see that he
always uses the port 1720 and many others. Furthermore he uses dynamic
UDP-Ports due to the H.323 Protocol.
|
NetMeeting uses two protocols for call connections -- H.323 for audio/video
and T.120 for data transfer. H.323 listens for incoming calls on tcp 1720
and then on connection uses udp ports that are negotiated ( from the range
32767+). T.120 listens on tcp 1503.
tcp 3389 is not used by NetMeeting.
| Quote: |
As far as i know H.323 is only used for Audio/Video Conferencing which
i dont need. Of course i do not want to open the whole 1024-65xxx port
range. My question is, how can i convince Netmeeting to use only the
Ports that are needed for the Remote Desktop Connection?
|
Tcp 1503 is all that is required for any data call in NetMeeting -- RDS is
a data call.
--
Brian Sullivan (MVP)
Meeting by Wire ( www.meetingbywire.com) |
|
| Back to top |
|
|
Ickis99
Guest
|
| Posted:
Tue Mar 22, 2005 8:39 pm Post subject:
Re: Netmeeting Remote Desktop Sharing over Firewall |
|
|
On Tue, 22 Mar 2005 09:27:30 -0500, Brian Sullivan MVP
<brians@WORMTIREDmeetingbywire.com> wrote:
| Quote: | On Tue, 22 Mar 2005 10:05:39 +0100, Ickis99 wrote:
Hi!
I try to establish a Netmeeting Remote Desktop Connection to different
Clients. My job is to open all ports on the client firewall to make
this connection possible. The MS Knowledgebase says that only Port
3389 is necessary to use Remote Desktop Sharing. But i see that he
always uses the port 1720 and many others. Furthermore he uses dynamic
UDP-Ports due to the H.323 Protocol.
NetMeeting uses two protocols for call connections -- H.323 for audio/video
and T.120 for data transfer. H.323 listens for incoming calls on tcp 1720
and then on connection uses udp ports that are negotiated ( from the range
32767+). T.120 listens on tcp 1503.
tcp 3389 is not used by NetMeeting.
As far as i know H.323 is only used for Audio/Video Conferencing which
i dont need. Of course i do not want to open the whole 1024-65xxx port
range. My question is, how can i convince Netmeeting to use only the
Ports that are needed for the Remote Desktop Connection?
Tcp 1503 is all that is required for any data call in NetMeeting -- RDS is
a data call.
|
You are right, 1503 is the first Port i can see in the Firewall Log.
But after opening that port he is requesting 1720 and after that the
dynamic udp Port. But only after opening ALL of this ports i can
establish the Remote Desktop Connection. But i do not need Audio or
Video.
Regards
Jürgen Winter |
|
| Back to top |
|
|
Brian Sullivan MVP
Guest
|
| Posted:
Tue Mar 22, 2005 9:06 pm Post subject:
Re: Netmeeting Remote Desktop Sharing over Firewall |
|
|
On Tue, 22 Mar 2005 16:39:04 +0100, Ickis99 wrote:
| Quote: | On Tue, 22 Mar 2005 09:27:30 -0500, Brian Sullivan MVP
brians@WORMTIREDmeetingbywire.com> wrote:
On Tue, 22 Mar 2005 10:05:39 +0100, Ickis99 wrote:
Hi!
I try to establish a Netmeeting Remote Desktop Connection to different
Clients. My job is to open all ports on the client firewall to make
this connection possible. The MS Knowledgebase says that only Port
3389 is necessary to use Remote Desktop Sharing. But i see that he
always uses the port 1720 and many others. Furthermore he uses dynamic
UDP-Ports due to the H.323 Protocol.
NetMeeting uses two protocols for call connections -- H.323 for audio/video
and T.120 for data transfer. H.323 listens for incoming calls on tcp 1720
and then on connection uses udp ports that are negotiated ( from the range
32767+). T.120 listens on tcp 1503.
tcp 3389 is not used by NetMeeting.
As far as i know H.323 is only used for Audio/Video Conferencing which
i dont need. Of course i do not want to open the whole 1024-65xxx port
range. My question is, how can i convince Netmeeting to use only the
Ports that are needed for the Remote Desktop Connection?
Tcp 1503 is all that is required for any data call in NetMeeting -- RDS is
a data call.
You are right, 1503 is the first Port i can see in the Firewall Log.
But after opening that port he is requesting 1720 and after that the
dynamic udp Port. But only after opening ALL of this ports i can
establish the Remote Desktop Connection. But i do not need Audio or
Video.
|
AFAIK if you force a data only call ( and easy way is to specify a "secure"
call) only tcp 1503 will be used.
RDS calls are by design data only.
--
Brian Sullivan (MVP)
Meeting by Wire ( www.meetingbywire.com) |
|
| Back to top |
|
|
Ickis99
Guest
|
| Posted:
Wed Mar 23, 2005 2:16 pm Post subject:
Re: Netmeeting Remote Desktop Sharing over Firewall |
|
|
On Tue, 22 Mar 2005 11:06:17 -0500, Brian Sullivan MVP
<brians@WORMTIREDmeetingbywire.com> wrote:
| Quote: | Tcp 1503 is all that is required for any data call in NetMeeting -- RDS is
a data call.
You are right, 1503 is the first Port i can see in the Firewall Log.
But after opening that port he is requesting 1720 and after that the
dynamic udp Port. But only after opening ALL of this ports i can
establish the Remote Desktop Connection. But i do not need Audio or
Video.
AFAIK if you force a data only call ( and easy way is to specify a "secure"
call) only tcp 1503 will be used.
RDS calls are by design data only.
|
I´ve already tried to secure the connection with the option "Secure
outgoing calls" but it makes no difference. After 1503 he tries port
1720. |
|
| Back to top |
|
|
Brian Sullivan MVP
Guest
|
| Posted:
Wed Mar 23, 2005 7:49 pm Post subject:
Re: Netmeeting Remote Desktop Sharing over Firewall |
|
|
On Wed, 23 Mar 2005 10:16:24 +0100, Ickis99 wrote:
| Quote: | On Tue, 22 Mar 2005 11:06:17 -0500, Brian Sullivan MVP
brians@WORMTIREDmeetingbywire.com> wrote:
Tcp 1503 is all that is required for any data call in NetMeeting -- RDS is
a data call.
You are right, 1503 is the first Port i can see in the Firewall Log.
But after opening that port he is requesting 1720 and after that the
dynamic udp Port. But only after opening ALL of this ports i can
establish the Remote Desktop Connection. But i do not need Audio or
Video.
AFAIK if you force a data only call ( and easy way is to specify a "secure"
call) only tcp 1503 will be used.
RDS calls are by design data only.
I´ve already tried to secure the connection with the option "Secure
outgoing calls" but it makes no difference. After 1503 he tries port
1720.
|
I am not sure why that would be the case with a data only call (a secure
call will definitely not *connect* the audio/video portion( H.323) of a
NetMeeting call). It may be a peculiarity of the way NetMeeting works. What
happens if you open 1503 and 1720 and make a secure call?
--
Brian Sullivan (MVP)
Meeting by Wire ( www.meetingbywire.com) |
|
| Back to top |
|
|
Ickis99
Guest
|
| Posted:
Fri Mar 25, 2005 9:39 pm Post subject:
Re: Netmeeting Remote Desktop Sharing over Firewall |
|
|
On Wed, 23 Mar 2005 09:49:47 -0500, Brian Sullivan MVP
<brians@WORMTIREDmeetingbywire.com> wrote:
| Quote: | On Wed, 23 Mar 2005 10:16:24 +0100, Ickis99 wrote:
On Tue, 22 Mar 2005 11:06:17 -0500, Brian Sullivan MVP
brians@WORMTIREDmeetingbywire.com> wrote:
Tcp 1503 is all that is required for any data call in NetMeeting -- RDS is
a data call.
You are right, 1503 is the first Port i can see in the Firewall Log.
But after opening that port he is requesting 1720 and after that the
dynamic udp Port. But only after opening ALL of this ports i can
establish the Remote Desktop Connection. But i do not need Audio or
Video.
AFAIK if you force a data only call ( and easy way is to specify a "secure"
call) only tcp 1503 will be used.
RDS calls are by design data only.
I´ve already tried to secure the connection with the option "Secure
outgoing calls" but it makes no difference. After 1503 he tries port
1720.
I am not sure why that would be the case with a data only call (a secure
call will definitely not *connect* the audio/video portion( H.323) of a
NetMeeting call). It may be a peculiarity of the way NetMeeting works. What
happens if you open 1503 and 1720 and make a secure call?
|
If i remember correctly, he wants a third port an this is the dynamic
one. But i will do more testing next week to answer your question. |
|
| Back to top |
|
|
Brian Sullivan MVP
Guest
|
| Posted:
Fri Mar 25, 2005 10:15 pm Post subject:
Re: Netmeeting Remote Desktop Sharing over Firewall |
|
|
On Fri, 25 Mar 2005 17:39:43 +0100, Ickis99 wrote:
| Quote: |
I am not sure why that would be the case with a data only call (a secure
call will definitely not *connect* the audio/video portion( H.323) of a
NetMeeting call). It may be a peculiarity of the way NetMeeting works. What
happens if you open 1503 and 1720 and make a secure call?
If i remember correctly, he wants a third port an this is the dynamic
one. But i will do more testing next week to answer your question.
|
I know that in my setup I can forward tcp 1503 from my router/gateway to
machine running NetMeeting RDS and by calling the router public IP in a
secure call connect to and control the target internal machine. I have
never actually examined the traffic that takes place during that process
though.
--
Brian Sullivan (MVP)
Meeting by Wire ( www.meetingbywire.com) |
|
| Back to top |
|
|
Ickis99
Guest
|
| Posted:
Tue Mar 29, 2005 7:18 pm Post subject:
Re: Netmeeting Remote Desktop Sharing over Firewall |
|
|
On Fri, 25 Mar 2005 12:15:46 -0500, Brian Sullivan MVP
<brians@WORMTIREDmeetingbywire.com> wrote:
| Quote: | On Fri, 25 Mar 2005 17:39:43 +0100, Ickis99 wrote:
I am not sure why that would be the case with a data only call (a secure
call will definitely not *connect* the audio/video portion( H.323) of a
NetMeeting call). It may be a peculiarity of the way NetMeeting works. What
happens if you open 1503 and 1720 and make a secure call?
If i remember correctly, he wants a third port an this is the dynamic
one. But i will do more testing next week to answer your question.
I know that in my setup I can forward tcp 1503 from my router/gateway to
machine running NetMeeting RDS and by calling the router public IP in a
secure call connect to and control the target internal machine. I have
never actually examined the traffic that takes place during that process
though.
|
Ok, thanks for your help. Iam giving up. We are using Dameware
from now on.
Regards
Jürgen Winter |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in