Re: Ping pmj

<corbei@xxxxxxxx> wrote in message
news:0l1ja2l0q3nt7qd6389vs693a5ebplride@xxxxxxxxxx
On 3 Jul 2006 20:22:55 GMT,
"Jeff Gaines" <jgaines_newsid@xxxxxxxxxxx> wrote:

If you are going to dig holes in your router then you should use
a software firewall to fill the gaps in or you will get intruders!!!

Yep, but you'll still need to then make sure that the *Software*
Firewall (on the PC) is Set to allow the Incoming Call Requests - which
are on TCP Port 1720 1503 - If you have them Blocked (either in your
Software Firewall, or not Forwarded in your Router), then NetMeeting
won't be able to Accept Incoming Call Requests.

I have ZA running.

See above.

The job of the Firewall is to *Block* any *Unwanted* Incoming
Connection attempts - but it's job is *also* to *allow* any
Incoming Connection attempts that you *do* want!

If you only ever want to make outgoing NetMeeting Calls, then you
don't have to Open up any Ports [*1]

[*1]
But note that with *some* Firewalls (& Routers) - i.e. ones that
don't use SPI - Stateful Packet Inspection - you may well need to
*also* Open up some Ports when receiving Calls.

Normally those Ports are Opened up "Dynamically" (as & when needed)
by (or rather in response to) NetMeeting, using the H323 Protocol,
during the initial stages of the call Setup & most Firewalls/Routers
can handle that, but some (such as the Draytex one that Jeff Gaines
uses), seem to have some probs with the H323 Protocol.

I went through this process to get NM working but decided in the
end it wasn't worth the security risk so I reset everything. As far
as GRC is concerned my PC doesn't exist on the Internet.

& if you have NetMeetin gRunning, waiting for an Incoming Call
(& your Firewall & Router correctly Set up), then the *only* Ports
which any Port Scanning Site, such as GRC.com should show as being
"Open" are Ports 1720 & 1503

You may be correct and I may end up doing the same, I have a job in
mind and netmeeting would simplify it but it is not that important.

If you only want to do/use the "Desktop & Application Sharing" bits
of NetMeeting (&/or the "Remote Control" Bits) & don't need the VoIP
(Voice over Internet Protocol) stuff (or the Text Chat facility),
then it may be an idea to use something else?

Such as VNC
http://realvnc.com/
http://realvnc.com/what.html

or...
http://tightvnc.com/
http://tightvnc.com/intro.html

The only (or main?) reason that most people who want to do that sort
of thing seem to use M$ NetMeeting (instead of VNC) is because
NetMeeting comes already Installed with windoze - both WinXP & W2K
& w98 & WinMe - so it can easily be Set up & used by people who have
no idea about (or experience of) Downloading, Installing & Running
Applications & Utilities such as "Server" type stuff.

So it's just a matter of Opening it (NetMeeting) up & using it.
(& Setting the Port Forwarding/Firewall on the Machine that is going
to be accepting *Incoming* Call Requests)

But to use VNC, you need to go & Download the Install File from their
Website & then UnZip it & Install it & Set the VNC Server Running
(on the Machine that is to be *Viewed*/Controlled) & then Run the
VNC Viewer Utility (or use a Web Browser) on the Machine doing the
Viewing. - All of which is actually very quick & easy, but in my
experience, many people don't seem to want to get involved with that -
all they want is to have the problems on their PC sorted out, which
is (mainly) why we use anything like NetMeeting or VNC in the first
place!
:-)

But that (VNC) will *still* need a Port (Port 5900 or 5800 normally)
to be Open in the Firewall &/or Router (on the Machine that is
being Viewed/Controlled) But it only needs that one Port Open
& nothing else.

HTH

--
pmj


.

Relevant Pages

  • Re: How to Establish NetMeeting Connections Through a Firewall
    ... > firewall or not, and what ports you should pass through ... It does provide information on port usage in NetMeeting but from I can tell ... You said you strongly recommend a software firewall, ... > communication on all the ports described in the article. ...
    (microsoft.public.internet.netmeeting)
  • Re: NetMeeting and NAT firewall
    ... > Is it possible to support NetMeeting via a NAT firewall, ... firewall because you have to open LOTS of ports. ... 389 Internet Locator Server (TCP) ...
    (comp.security.firewalls)
  • Re: Port forwarding/open ports?
    ... > To be able for another person to connect to my Netmeeting in ... > Windows XP and share applications I would need to open the ports 1720 ... > and 1503 in my router firewall. ...
    (alt.computer.security)
  • 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)
  • [opensuse] Re: Remote Administration Client
    ... There seems to be a plethora of Clients, The Support side client will be ... Well, if you're just using VNC, then all you need is a VNC client. ... ports through your firewall. ...
    (SuSE)