Re: Net Meeting and Ports
- From: "pmj" <post@xxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 04 Aug 2005 22:00:49 GMT
"Jeff Gaines" <jgaines_newsid@xxxxxxxxxxx> wrote in message
news:xn0e5lhuc1bduh8002@xxxxxxxxxxxxxxxxxxxxxx
>
> When I was trying to call Aries this a.m. I had TCPView open to try
> and see what was happening.
Yep, that TCPView Utility (from SysInternals.com) is very useful for
that sort of thing.
Also, some FireWalls (such as Tiny/Kerio KPF & Sygate Personal) show
a View of the Porst & Endpoints, with the state of the Connections etc.
> 'conf.exe' seemed to be using a range of TCP ports on my PC from
> 1358 to 1363 to call the destination ports of 1720 and 1503.
Yep - Ports 1720 & 1503 are the Ports used by NetMeeting to establish
the Call.
It Negotiates through them, which other Ports & Protocols to use.
It also (apparently) uses Port 1731 (TCP) to Set up the Audio (VoIP),
which actually uses a Range of Ports, using the UDP Protocol.
> I opened up a range of ports on the router and tried calling Aries
> again, without success.
Did she not receive the Call Invitation?
Or did she receive it, but then the Call wouldn't Start?
Or did the Call start, but then there was no Voice?
All of those will Help us to identify the prob.
> I then went to the GRC Shields Up test which warned me that I had
> a range of TCP ports open, so I seem to have managed to do the
> 'right' thing on the Draytek.
Yep, you *do* need to have those Ports "Open" (& with the right
Protocol - TCP or UDP), to be able to both Initiate & also Receive &
Establish
a NetMeeting Connection.
> This laptop uses a wireless network which is not firewalled.
>
> Just had a test with another of our young ladies (thank you Boo, my
> social life has improved a million% since subscribing to this group!).
> When Boo called me we had 2 way working, when I called her it was the
> usual problem, she could hear me but I couldn't hear her. MSN
> Messenger
> was fine with Boo though.
OK - now we do seem to have established some kind of Pattern to the
prob?
So, I would suggest that you need to try NetMeeting on another PC
your end (still using the same Router & internet Connection)
& then, try it using a *different* Router & also, possibly using
a normal (USB) ADSL Modem.
You have to establish whether the prob is with the PC, the Router
or the Internet Connection.
> In TCPView my PC name is sometimes jgport and others JGPORT.
Yep, I've noticed that - I dunno the significance of it.
Sometimes it shows as being the Local IP Address & sometimes as my
External (Internet) IP Address, but I'm not using a Router, so they
are both the same Machine.
>... In addition there is no status against the UDP connections but
> there is for the TCP connections.
That's cos of the way that UDP works - there's no "Connection" as such -
it doesn't have any "Established" state.
It just Listens (or Sends stuff) - it (the UDP Protocol) doesn't need
(or allow for) an "Acknowledgement" as such, unlike TCP which *does*
work that way.
> Sorry for the rambling, this is just a gathering of data in case it
> helps with clues, I am open to suggestions or comments :-)
& I hope some of the points & Comments I have made might Help.
Do try an alternative PC &/or Router/Connection.
Then we will know where the prob is & what's causing it.
HTH
--
pmj
.
- Follow-Ups:
- Re: Net Meeting and Ports
- From: Jeff Gaines
- Re: Net Meeting and Ports
- References:
- Net Meeting and Ports
- From: Jeff Gaines
- Net Meeting and Ports
- Prev by Date: Re: Port Forwarding
- Next by Date: Re: ..to Troy's Human...
- Previous by thread: Net Meeting and Ports
- Next by thread: Re: Net Meeting and Ports
- Index(es):
Relevant Pages
|