RE: Re: [OT]ish Router +modem problem

["Peter Church" <yahoo@xxxxxxxxxxxxxxxx>]

Yes, my thinking exactly!



I might try changing the DNS on the router side to default to the modem
192.168.2.101 rather than the router to see if it can divert the traffic
directly to the modem (which works when the modem is the DHCP/default
gateway)



Any other thoughts?



Thanks


Pete



From: ukha_d@xxxxxxx [mailto:ukha_d@xxxxxxx] On Behalf Of
Nick Austin
Sent: 29 August 2011 15:33
To: ukha_d@xxxxxxx
Subject: Re: [ukha_d] Re: [OT]ish Router +modem problem





Hi Peter,

The timeout (asterisks) is probably an ISP-owned router configured not
to reply ICMPs. As long as you are getting replies from routers
further down the chain it isn't a problem.

Also the 90ms+ round trips are typical for 3G broadband so further
confirmation that ICMPs are being sent and received over the Internet.

So as I see it a summary so far:
DHCP is working
DNS is working
DNS RELAY is working
TRACERT is working.

So really I can't see any reason for it not working at all.

Nick.

On Sun, Aug 28, 2011 at 7:28 PM, Peter Church <yahoo@xxxxxxx
<mailto:yahoo%40petechurch.co.uk>
> wrote:
> Nick,
>
>
>
> Yes the numbers changed slightly as I switched the 3rd digit of the
subnet,
> but the problem remains the same.
>
>
>
> Here are the results of the Trace Routes:
>
>
>
>>tracert -h 4 192.168.1.1
>
>
>
> Tracing route to 192.168.1.1 over a maximum of 4 hops
>
>  1    <1 ms    <1 ms    <1 ms  192.168.1.1
>
> Trace complete.
>
>
>
>>tracert -h 4 192.168.2.101
>
> Tracing route to e.home [192.168.2.101] over a maximum of 4 hops:
>
>  1    <1 ms    <1 ms    <1 ms  192.168.1.1
>
>  2     2 ms     2 ms     2 ms  e.home [192.168.2.101]
>
> Trace complete.
>
>
>
>>tracert -h 4 212.58.246.94
>
> Tracing route to bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94] over a
maximum
> of 4 hops:
>
>  1    <1 ms    <1 ms    <1 ms  192.168.1.1
>
>  2     2 ms     1 ms     1 ms  e.home [192.168.2.101]
>
>  3     *        *        *     Request timed out.
>
>  4    87 ms    88 ms    99 ms  193.120.29.125
>
> Trace complete.
>
>
>
> I also checked this over more hops and it does get there in 13 hops. 
It
is
> interesting that the domain name is listed which means DNS is working,
but
I
> guess it is that 3rd hop that is causing the problem.  Any idea what
that
> means?
>
>
>
> I disabled DNS on the modem and gave the router a fixed IP address and
the
> ISP supplied DNS IPs and the same result occurs.
>
>
>
> Out of interest I ran a trace route with the Modem acting as the DHCP
(when
> I can get the internet to work) and received this result:
>
>
>
>  1    <1 ms    <1 ms    <1 ms  e.home [192.168.2.101]
>
>  2     *        *        *     Request timed out.
>
>  3    98 ms    99 ms    99 ms  217.112.145.125.gvnx.com
[217.112.145.125]
>
>  4   127 ms   139 ms   138 ms  xe1-2-0-10.tcr1.thn.lon.as8218.eu
> [213.152.31.16
>
>
>
> So it looks like that Time Out is consistent, but not a killer! 
Perhaps
> interesting that the next hop IP is in a different range to the
others?
>
>
>
>
>
> The current status of the modem is:
>
> DHCP - Off - fixed IP address
>
> Firewall - Off
>
> DMZ - Disabled
>
> Virtual Servers (port routings) - None
>
> UPnP - Enabled
>
>
>
> Any thoughts?
>
>
> Thanks for your time reading this!
>
>
>
> Cheers
>
>
>
> Pete





[Non-text portions of this message have been removed]



------------------------------------

<*> Join the Automated Home Forums
http://www.automatedhome.co.uk/vbulletin/