Re: Tutorial?

On 29 May 2006 06:51:05 -0700, mig wrote:

Hi Larry

I am building a visual basic application that uses Netmeeting SDK.


You do realize that NetMeeting is being retired and will be in no future
O/Ss? Microsoft specifically has recommended that users do not develop
applications using NetMeeting as platform.

INM allows you to share the Remote Desktop by:

1. Tools menu-> remote desktop sharing

2. Tools menu -> Sharing (Ctrl+S) -> desktop (Share)

In my opinion the second option works better.

The two options have completely different uses -- the first one is for
unattended desktop control. The second is for sharing while in a attended
call and allows for optionally allowing control (the call can have multiple
parties)




My experience is that you usually don't need to open any firewall port
if you just use the remote desktop thing.


It depends on what "opening" ports means though and what kind of firewall
you and the article is referring to and whether you are talking about
incoming or outgoing calls. Local software firewalls require allowing
listening access to tcp 1503 for NetMeeting for all incoming data
calls(including both kinds of desktop sharing). Incoming(and outgoing)
Audio/video requires tcp 1720 listening access plus some udp ports (that
are not predetermined) so it will be necessary for the firewall to allow
"full server" access to get them to work (different software firewalls have
different ways of specifying this).

If your firewall is a nat or other border firewall it will be necessary to
forward tcp 1503 (for just incoming data access) or usually set a dmz type
feature if you want full audio/video access. Calls are then made to the
border IP.



I tell you this from my experience, I sucessfully established a
netmeeting call from a firewalled pc, I however, could only get my
remote desktop and not video and audio.

Outgoing calls that are data only usually require no firewall changes.
Audio/video calls outgoing require either a H.323 proxy in the firewall
(which a few older devices do have) or use of the dmz type feature.

It is possible to provide two way calling in a firewalled or NATed network
via an H.323 gateway/gatekeeper but implementing such a device is usually
not feasible for smaller networks


--
Brian Sullivan
Courses by Wire (http://www.coursesbywire.com)
.

Relevant Pages

  • Re: Ping pmj
    ... a software firewall to fill the gaps in or you will get intruders!!! ... Software Firewall, or not Forwarded in your Router), then NetMeeting ... *also* Open up some Ports when receiving Calls. ... Such as VNC ...
    (uk.people.silversurfers)
  • Re: Netmeeting works but nothing else does
    ... "Full" NetMeeting calls are really two calls in parallel - and H.323 ... > connections on specific ports and secondary UDP connections on ... > computers outside the firewall and you are able to use the audio ...
    (microsoft.public.internet.netmeeting)
  • Re: Problems with Netmeeting
    ... My friend uses Windows ME. ... assuming the party is running NetMeeting waiting for the call, ... router or firewall or protected by a local software firewall that blocks ...
    (microsoft.public.internet.netmeeting)
  • RE: NetScreen XP and NetMeeting
    ... Let me preface this by saying I know nothing about Netmeeting, ... Are you a client connecting to the internet through a firewall and trying to ... establish a netmeeting connection, or are you setting up a Netmeeting server ... The big scary-looking range of ports are outbound UDP ports, ...
    (Security-Basics)
  • Re: GPO for Remote Desktop and Firewall Settings
    ... Remote Desktop has to be enabled on the target computer and appropriate user ... This is independant of any Firewall ... These settings will work with computers running Windows 2000 SP2 or later, ... > Windows Firewall: ...
    (microsoft.public.win2000.group_policy)