Re: Netmeeting port forwarding over SSH
From: JM (jm@jaxmeier.com)
Date: 02/25/03
- Previous message: Jared Subman: "Netmeeting port forwarding over SSH"
- In reply to: Jared Subman: "Netmeeting port forwarding over SSH"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "JM" <jm@jaxmeier.com> Date: Tue, 25 Feb 2003 10:05:58 -0500
I believe Netmeeting requires more than just the one port.
http://www.microsoft.com/windows/NetMeeting/Corp/reskit/Chapter4/default.asp
>From Microsoft...
Establishing a NetMeeting Connection with a Firewall
When you use NetMeeting to call other users over the Internet, several IP
ports are required to establish the outbound connection. The following table
shows the ports, their functions, and the resulting connection.
Port Function Outbound Connection
389 Internet Locator Service (ILS) TCP
522 User Location Service TCP
1503 T.120 TCP
1720 H.323 call setup TCP
1731 Audio call control TCP
Dynamic H.323 call control TCP
Dynamic H.323 streaming Real-Time Transfer Protocol (RTP) over UDP
If you use a firewall to connect to the Internet, it must be configured so
that the IP ports are not blocked.
To establish outbound NetMeeting connections through a firewall, the
firewall must be configured to do the following:
a.. Pass through primary TCP connections on ports 389, 522, 1503, 1720,
and 1731.
b.. Pass through secondary TCP and UDP connections on dynamically assigned
ports (1024-65535).
The H.323 call setup protocol dynamically negotiates a TCP port for use by
the H.323 call control protocol. Also, both the audio call control protocol
and the H.323 call setup protocol dynamically negotiate UDP ports for use by
the H.323 streaming protocol, called the Real-Time Transfer Protocol (RTP).
In NetMeeting, two UDP ports are determined on each side of the firewall for
audio and video streaming, for a total of four ports for inbound and
outbound audio and video. These dynamically negotiated ports are selected
arbitrarily from all ports that can be assigned dynamically.
NetMeeting directory services require port 389. Microsoft Internet Locator
Service (ILS) servers, which support the Lightweight Directory Access
Protocol (LDAP) for NetMeeting, also require port 389.
"Jared Subman" <jaredsubman@removethis.yahoo.com> wrote in message
news:Xns932D5F998780Djaredsubmannospamyah@127.0.0.1...
> I thought it would be possible to forward Netmeeting's Remote Desktop
> 1503 port like I forward VNC's 5901 port so that I could access my home
> desktop remotely, however when I try the following command, the port
> seems to forward okay, but I can't get Netmeeting to place the call.
>
> ssh -N -f -l username -L 1503:homeip:1503 homeip
>
> Then when I start Netmeeting, I get the message "Netmeeting could not
> start. Please restart your computer and try again."
>
> Any ideas on why this is?
- Next message: S. Eng: "openssh's sshd for windows. Do I need an autho file?"
- Previous message: Jared Subman: "Netmeeting port forwarding over SSH"
- In reply to: Jared Subman: "Netmeeting port forwarding over SSH"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
