Re: Ping pmj

<corbei@xxxxxxxx> wrote in message
news:8echa2ddsb63308ofcedf2qn8o5fet544j@xxxxxxxxxx
On Mon, 03 Jul 2006 06:49:27 +0100, corbei@xxxxxxxx wrote:
<snip>
On the box it says eTec adsl 2/2+ modem/router 4port and on the
router it says PTI-845. I have a small quickstart guide which is
not very informative but one page does stress that when you change
settings it is necessary to "save all"
The manual mostly deals with basic settings and I just ran with
the defaults.

Yep, the Defaults (which work for ordinary Web Borowing & Mail/News
etc,) are (& should be) to completely *Block* any UnSolicited InComing
Connections - in other words, to just Drop them & *not* to "Forward"
them to any of the PCs on your own Network.

But if you *do* want to be able to have an InComing Connection Request
(on a particular Port) being Forwarded to a particular PC on your
Network - which you would, if you wanted to be able to Receive
Incoming MetMeeting Call Requests - then you do have to explicitly
Set up a Rule (or some Rules) in the "Port Forwarding" Section of
the Firewall Admin Pages.

To just make *Outgoing* NetMeeting Call Requests, you don't (normally,
with most Routers) need to Set up any Port Forwardding Rules.

Seems to work OK except I have just checked and the stuff you did
yesterday has (Netmeeting) has gone so I will try to reset it.

Further to this I have just looked and there is a section
for neetmeeting which gives the following rule

Yep I saw that it does actually have some "Pre-Defined" Rules,
for thinsg such as NetMeeting etc, but (in my experience, on most
Routers), it's just as quick & easy to simply Set up a rule to do it -
also the Pre-Defined Rules usually Open up more Ports than are actually
needed...

Protocol Port Start Port End Port Map
TCP,UDP 1024 1064 1024
TCP 1503 1503 1503
TCP 1720 1720 1720
TCP 1731 1731 1731
TCP 522 522 522
TCP 389 389 389

There - see?

I've found that you *don't* actually need all of those Ports to be
opened (Forwarded) for netmeeting to be able to Receive Incoming Calls
& to be able to Establish the Call.

& especially you don't need Ports 522 & 389 - they are only needed if
you are using the various "Directory" Services" that NetMeeting can use.
& you don't need to use any of those - you just make your Call directly
to the other Machine, or they Call you directly.

I will give you a call

Yep, please do.
& we'll have another look at it.

--
pmj


.

Relevant Pages

  • Re: Port Forwarding
    ... > Just found a site with detailed advice for port forwarding for ... For instance it says that some Routers ... can't be Set to Open sufficient Ports to allow NetMeeting ... & all the NetMeeting Functions work, as intended,, ...
    (uk.people.silversurfers)
  • Re: Remote Assistance not working
    ... AFAIK UPnP is supposed bypass the need, yet stranger things do happen and if using port forwarding makes it work that's one of those times. ... Brian A. Sesko ... Both routers have> UPnP ...
    (microsoft.public.windowsxp.general)
  • Re: Remote Assistance not working
    ... I haven't tried configuring port forwarding yet. ... Both routers have UPnP ...
    (microsoft.public.windowsxp.general)
  • Re: Network from home to office, etc.
    ... I have an 8 port router at the office ... This entails finding out if those routers have static or dynamic IPs. ... I suggest port 3389 for remote desktop to be your easiest solution. ... (Of course, that assumes Windows XP Professional, Windows 2000 Server ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Xbox initiates but loses connection
    ... The BEFW11S4 v2 WAP w/ 4 port switch is not a WAP. ... Incompatible Routers ...
    (microsoft.public.windows.mediacenter)