Re: Net Meeting and Ports
- From: "pmj" <post@xxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 05 Aug 2005 00:01:51 GMT
"Jeff Gaines" <jgaines_newsid@xxxxxxxxxxx> wrote in message
> On 04/08/2005 pmj wrote:
>> Yep, that TCPView Utility (from SysInternals.com) is very useful
>> for that sort of thing.
> I'm picking up a sort of rumour that SysInternals.com is your
> second home :-)
They have a whole bundle of really very useful Utilities, that can
very often Help with all sorts of probs!
>>> '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.
> TCPView was also showing various TCP Ports from 1358 to 1363 which is
> outside the 'normal' range used by NM, and I don't have them open.
> Wondering if I need to open them as well?
Yes, that's how it works...
I dunno how to explain it, but I think I have a (reasonable) grasp
With TCP, when your PC Connects (makes an Outbound, TCP Connection)
*to* some other thing, the *Remote* Port is the one that is (for
example) 1503 or 1720 & the *Local* Port is whatever the Application (&
Operating System) decides to use.
Vice-versa, when your PC is *listening*, it has a particular (range of)
Local Ports Open...
& when an (Incoming, TCP) Connection is Established, (to, through) that
Listening Port, the *local* Port will be, say 1503 or 1720 & the
*Remote* Port will be whatever the *other* end decides.
>>> I opened up a range of ports on the router and tried calling Aries
>>> again, without success.
Now that was (almost definitely) simply cos *she* hasn't got the
relevant, necessary Ports (1503 TCP & 1720 TCP & 1731 TCP) & Opened
(& Forwarded) in *her* Firewall.
She will be able to Call *you*, (or anybody else) but won't be able to
Receive Incoming Calls, until she sorts that out.
>> 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?
> Not a sausage, no invitation received.
That's easily sorted out (in her Firewall/Router).
>> OK - now we do seem to have established some kind of Pattern
>> to the prob?
> Yes, it's narrowed down to - I can be called no probs but calling out
> means one way speech.
& when someone (anybody) calls you, you always get 2 way Speech OK?
(assuming *they* have no probs, their end).
>> 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.
> Yes indeed :-(
> The issue is the same with both Toshiba (XP Pro) and Sony (XP Home)
> laptops (both wireless connections),
Using the same Router?
>... I could also test the main PC which is wired to the network,
But again, I presume still using the same Router for the actual Internet
> I don't want to put NM on the Media Centre PC which is headless,
> mouseless and keyboardless or the server which is bare of apps
> except for some utils.
Fair enough, but NetMeeting actually comes *already* Installed with
WinXP - it just doesn't have an Entry in the Start Menu.
The first time you Run it (by Running conf.exe), it then Runs through
> I do have an old laptop which I think works, is it worth putting,
> say, W98SE on that and trying it?
It may well be...
What other OS does it have then?
W98 (both SE & Original) work fine with NetMeeting V3.01 - but w98
doesn't actually come with V3.01 - it only comes with V2.1 - you would
have to Install it on w98 - W98SE does have V3.01 (but a previous Build)
>... If it works it may point to XP as the stopper,
But that would be *your* particular WinXP, cos generally it's all fine.
>... if it doesn't it's probably back to the router.
Or the Internet Connection?
*Some* ISPs Block *some* Ports.
> I used a Linksys modem/router today, opened the ports and that was
> a total disaster, couldn't establish a connection in either direction.
Cos I know people using LinkSys Routers with NetMeeting perfectly OK.
Can we try that some time?
We could use Skype (or the Phone?) to Talk, while we get it sorted?
& VNC, (if needs be) to do the other stuff, such as the Desktop Sharing.
>... I don't have any more modems.
No ordinary, standalone USB ADSL Modem then?
> I have logged a support request directly with Draytek, a TickettyBoo
> suggestion, be interesting to see if they have any ideas.
But I suspect they will just say something like "Yes, we know that it
doesn't (always?) work properly (or at all) - tough!"
I'd be interested to hear what the say.
& if they have any bright & Helpful suggestions.
>... At least the other toys like Skype an MSN Messenger work OK
> so I am not isolated
With a PC & an Internet Connection, you need never be isolated!
BTW - If you use M$N Messenger through a Router, when it comes
to File Transfer you may have probs - sometimes you end up with the File
having to go through the M$N/Hotmail Servers, which is *very* slow.
If you don't allow Port 7000 & 7001 UDP (I can't remember which Port
is used in which Direction), which is what the "Echo" thingy checks
through, it assumes that it has to use the Servers for the Transfer.
> I don't want to get obsessed by this but it would be good to find
> an answer....
Yes, of course.
It is puzzling, though, isn't it?
- Re: Net Meeting and Ports
- From: Jeff Gaines
- Re: Net Meeting and Ports
- Prev by Date: Little LOA
- Next by Date: Re: Little LOA
- Previous by thread: Re: Net Meeting and Ports
- Next by thread: Re: Net Meeting and Ports