Re: Net Meeting Update (may be boring to some)
- From: "pmj" <post@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 08 Aug 2005 15:06:34 GMT
"Jeff Gaines" <jgaines_newsid@xxxxxxxxxxx> wrote in message
news:xn0e5r0hk4mtj4000@xxxxxxxxxxxxxxxxxxxxxx
>
> Another session in the bike shed with pmj yesterday, I hope you got
> your dinner in the end pmj :-)
Yes I did, thanks!
:-)
Well, it was my Breakfast, I think! (I count Breakfast as the first meal
that I eat after I get up, rather than being at a particular time of
Day - morning)
:-)
> We found the Kerio connection screen very useful in diagnostics,
> so thanks again to the young lady who recommended it to me (was it
> Tickettyboo?).
Yes it was - & yes, the Kerio Personal Firewall does seem to be a very
good (Free!) Firewall - it does all that it should do & includes various
things (such as that "Connections Status" Screen, that can Help with
sorting out various probs - it shows you "what's what".
TCPView (from SysInternals.com) is a (standalone), 3rd Party Utility
which does a similar job of showing the connections - what
IP Address(es) & Ports are Connected & what Ports are Listening, etc.
> The only problem I have is that when I call pmj I can't hear him.
Yes, that's a bummer!
Yet it works fine (Sound OK, both ways) if I call you.
>... Kerio shows *no* incoming connections on the UDP ports that we
> need for communication. These ports are shown as being connected when
> pmj calls me.
& when we tried it in one particular Configuration, it showed that the
Remote IP Address (yours0 *was* there, but it was the *wrong* IP
Address - it showed your Internal Network Address, rather than the
Public (Internet) IP Address.
> When I put my laptop in the DMZ (i.e. it has no protection from the
> router firewall) it works fine both ways. That seems to imply that it
> is a routing/configuration problem on the router.
Definitely!!!
> pmj looked at incoming packets and saw that a request from me was
> asking him to respond to 192.168.1.11 which was the IP address of my
> laptop, and as an internal address not contactable from outside the
> network.
Yep, that's definitely the problem...
>... So my router may be telling pmj my internal IP address rather
> than my public IP address. Words like masquerading and NAT passed
> pmj's lips, I will spend some time today finding out what they mean.
The NAT (Network Address Translation) - in The Router - is *s'posed*
to handle that, keeping track of which PC (on the Internal network)
to Send the Incoming Packets to, when it receives them & telling the
Remote Connection the *Public* (Internet IP Address to send them to,
but for some reason, it was telling it the *Internal* (& therefore
UnRoutable) IP Address.
> I had what I thought was a brain wave after I went to bed.
>
> I use a Linksys Router/WAP to give me a wireless connection
> throughout the bungalow, it is connected to the Draytek by a long
> cat5e cable and I communicate through it from the laptop, which has
> a wireless connection. On checking this morning I noticed that the
> Linksys firewall is on and that it has some forwarding rules in it.
Ah!!!
Yes, I didn't realise that you had *2* Routers in place!!!
Surely, you would need to *also* Set up the Relevant Port Forwarding
(NAT) Rules in the LinkSys Router as well, then?...
>... I am struggling to think through the significance of this because
> when the laptop was in the DMZ we could communicate fine so the
> Linksys didn't interfere.
Hmm, odd...
>... My feeling is it may be a factor but I don't have the knowledge
> to know in what way.
But we now know to have a look at that?
> I am pretty sure I didn't put the forwarding rules in the Linksys,
> I have a feeling that the other Linksys I used temporarily the other
> day may have the same IP address as the Linksys WAP. That would
> explain why I had such a problem connecting to it and it may be
> I was adding rules to Linksys 1 when I thought I was connected to
> Linksys 2.
Sounds very confuzzling!
> I have now turned off the security and rules in the Linksys WAP.
>
> Apologies if you did find this boring :-(
Not boring at all!
It's fascinating! (& very interesting)
& I'm sure we will be able to get to the bottom of it & suss it out OK.
> If it has triggered any ideas then please let me know, my brain hurts!
I reckon we need to have a look at the Settings in the *LinkSys* Router
(the other one - that's what's connected to the actual Internet?
& it needs to Forward the stuff to the right IP Address & *also* the
right Ports.
--
pmj
.
- Follow-Ups:
- Re: Net Meeting Update (may be boring to some)
- From: Flyiñg Ñuñ 2°°5 +
- Re: Net Meeting Update (may be boring to some)
- References:
- Net Meeting Update (may be boring to some)
- From: Jeff Gaines
- Net Meeting Update (may be boring to some)
- Prev by Date: Re: G.M.T. Monday 8th August 2005
- Next by Date: Re: Dial up connections in XP
- Previous by thread: Re: Net Meeting Update (may be boring to some)
- Next by thread: Re: Net Meeting Update (may be boring to some)
- Index(es):
Relevant Pages
|
