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

[Nick Austin <nick.w.austin@xxxxxxxxx>]

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> wrot=
e:
> Nick,
>
>
>
> Yes the numbers changed slightly as I switched the 3rd digit of the
subne=
t,
> 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
>
> =A01 =A0 =A0<1 ms =A0 =A0<1 ms =A0 =A0<1 ms =A0192.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:
>
> =A01 =A0 =A0<1 ms =A0 =A0<1 ms =A0 =A0<1 ms =A0192.168.1.1
>
> =A02 =A0 =A0 2 ms =A0 =A0 2 ms =A0 =A0 2 ms =A0e.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
maximu=
m
> of 4 hops:
>
> =A01 =A0 =A0<1 ms =A0 =A0<1 ms =A0 =A0<1 ms =A0192.168.1.1
>
> =A02 =A0 =A0 2 ms =A0 =A0 1 ms =A0 =A0 1 ms =A0e.home [192.168.2.101]
>
> =A03 =A0 =A0 * =A0 =A0 =A0 =A0* =A0 =A0 =A0 =A0* =A0 =A0 Request timed
ou=
t.
>
> =A04 =A0 =A087 ms =A0 =A088 ms =A0 =A099 ms =A0193.120.29.125
>
> Trace complete.
>
>
>
> I also checked this over more hops and it does get there in 13 hops.
=A0I=
t is
> interesting that the domain name is listed which means DNS is working,
bu=
t I
> guess it is that 3rd hop that is causing the problem. =A0Any idea what
th=
at
> means?
>
>
>
> I disabled DNS on the modem and gave the router a fixed IP address and
th=
e
> ISP supplied DNS IPs and the same result occurs.
>
>
>
> Out of interest I ran a trace route with the Modem acting as the DHCP
(wh=
en
> I can get the internet to work) and received this result:
>
>
>
> =A01 =A0 =A0<1 ms =A0 =A0<1 ms =A0 =A0<1 ms =A0e.home
[192.168.2.101]
>
> =A02 =A0 =A0 * =A0 =A0 =A0 =A0* =A0 =A0 =A0 =A0* =A0 =A0 Request timed
ou=
t.
>
> =A03 =A0 =A098 ms =A0 =A099 ms =A0 =A099 ms
=A0217.112.145.125.gvnx.com [=
217.112.145.125]
>
> =A04 =A0 127 ms =A0 139 ms =A0 138 ms
=A0xe1-2-0-10.tcr1.thn.lon.as8218.e=
u
> [213.152.31.16
>
>
>
> So it looks like that Time Out is consistent, but not a killer!
=A0Perhap=
s
> 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


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

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