DJ Dunk

iTrader: (5)

I have real problems connecting to some sites.

They'll work fine most of the time, but after about a day I have to reset my ADSL router to be able to access them again Once reset, I can access fine.

It happens with ScoobyNet as well as another forum I access.

A tracert for the latter reveals:

Tracing route to www.civictype-r.co.uk [12.129.198.135]
over a maximum of 30 hops:

1 42 ms 2 ms 1 ms *.*.*.*
2 364 ms 272 ms 17 ms bbd-07.tcl.planet.net.uk [62.25.200.12]
3 277 ms 274 ms 17 ms pbr-1.tcl.as5388.net [62.25.200.130]
4 27 ms 19 ms 16 ms bnr-2.tcl.as5388.net [195.92.55.105]
5 219 ms 16 ms 18 ms 195.50.116.189
6 221 ms 23 ms 281 ms ae0-15.mp1.London1.Level3.net [212.187.131.129]
7 271 ms 279 ms 279 ms so-1-0-0.mp1.London2.Level3.net [212.187.128.49]
8 92 ms 303 ms 346 ms unknown.Level3.net [212.187.128.138]
9 119 ms 357 ms 541 ms so-3-0-0.mp1.Chicago1.Level3.net [64.159.1.33]
10 503 ms 271 ms 323 ms so-6-0-.edge1.Chicago1.Level3.net [209.244.8.10]
11 225 ms 338 ms 343 ms ATT-Level3-oc48.Chicago1.Level3.net [209.0.227.7
8]
12 * * * Request timed out.
13 408 ms 165 ms 275 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
14 182 ms 256 ms 547 ms gbr5-p100.sffca.ip.att.net [12.122.11.74]
15 422 ms 330 ms 347 ms gar3-p360.sffca.ip.att.net [12.123.13.157]
16 434 ms 340 ms 533 ms mdf1-gsr12-2-pos-5-0.lax1.attens.net [12.122.255
.254]
17 510 ms 274 ms 394 ms mdf1-bi8k-2-gig-1-1.lax1.attens.net [12.129.192.
242]
18 * * * Request timed out.

Any ideas ? Should I inform my ISP ?

[Edited by DJ Dunk - 3/7/2003 5:10:25 PM]

[Edited by DJ Dunk - 3/7/2003 5:12:01 PM]

Jeff Wiltshire

I get the same thing....

1 217.31.140.145 1ms 1ms 1ms TTL: 0 (No rDNS)
2 194.207.236.1 * 20ms 313ms TTL: 0 (Net_194-207-236.corerouter.a4.dfm3.thn-lon.pipemedia.net ok)
3 217.31.143.18 21ms 20ms 218ms TTL: 0 (eth2.bgp2.a5.dfm3.thn-lon.pipemedia.net ok)
4 212.187.197.193 301ms 22ms 120ms TTL: 0 (lvl3gw.thn.packetexchange.net probable bogus rDNS: No DNS)
5 212.113.0.114 194ms 335ms 25ms TTL: 0 (so-1-2-0.gar1.London1.level3.net ok)
6 212.113.3.1 76ms 237ms 34ms TTL: 0 (so-7-0-0.mp1.London1.Level3.net ok)
7 212.187.128.49 26ms 142ms 23ms TTL: 0 (so-1-0-0.mp1.London2.Level3.net ok)
8 212.187.128.138 98ms 118ms 92ms TTL: 0 (unknown.Level3.net fraudulent rDNS)
9 64.159.1.33 113ms 171ms 115ms TTL: 0 (so-3-0-0.mp1.Chicago1.Level3.net ok)
10 209.244.8.10 117ms 151ms 137ms TTL: 0 (so-6-0-0.edge1.Chicago1.Level3.net ok)
11 209.0.227.78 120ms 115ms 112ms TTL: 0 (ATT-Level3-oc48.Chicago1.Level3.net ok)
12 12.123.6.34 117ms 114ms 123ms TTL: 0 (tbr1-p014001.cgcil.ip.att.net probable bogus rDNS: No DNS)
13 12.122.10.6 431ms 179ms 455ms TTL: 0 (tbr1-cl1.sffca.ip.att.net probable bogus rDNS: No DNS)
14 12.122.11.78 458ms 166ms 358ms TTL: 0 (gbr6-p100.sffca.ip.att.net probable bogus rDNS: No DNS)
15 12.123.13.161 333ms 166ms 424ms TTL: 0 (gar3-p370.sffca.ip.att.net probable bogus rDNS: No DNS)
16 12.122.255.254 205ms 500ms 354ms TTL: 0 (mdf1-gsr12-2-pos-5-0.lax1.attens.net ok)
17 12.129.192.242 176ms 391ms 263ms TTL: 0 (mdf1-bi8k-2-gig-1-1.lax1.attens.net ok)
18 No Response * * *
19 No Response * * *
20 No Response * * *


Although I can get to the site itself.

DJ Dunk

iTrader: (5)

Odd. Any ideas why this is happenning ?

kamikaze

change ure isp
my old isp for whatever reason could only access this this site intermittently.

orbv

What does trace route have to do with DNS?

The machine resolved the name www.civictype-r.co.uk to the ip address (12.129.198.135) dns worked in your example.

From what you have posted I would assume you have noticed that not all hosts are responding to the traceroute packets. Sometimes hosts and routers are configured to not respond to this type of packet (firewall??) so what you are seeing looks normal!

There are lots of different traceroute protocols so type traceroute into google and read the night away.

DJ Dunk

iTrader: (5)

The point is that I am not getting to the site that I am after . . . .

The tracert shows how far I am getting and where it is failing.

Jeff Wiltshire

Are there any other sites that don't work ?

You say that when you reset your ADSL router it works ? Who is your ISP (I assume looking at the trace it's Planet). If you have to reset your router than it maybe that the router (or your browser) is caching some information??

There is only one traceroute protocol but many traceroute programs.

Apple

DJ Dunk

"I have to reset my ADSL router" how do you do this or is it a reboot?

I've got the frog (Alcatel one - not a router tho) and every so often seems to drop the connection and only a reboot will sort it even though pc doesn't recognise connection dropped - the connection software just keeps saying it's working but no lights lit on front

Apple

DJ Dunk

iTrader: (5)

My ISP is Freeserve ADSL. All other sites work fine. Its just these ones that seem to drop off.

To reset I am switching off and on again, but it can be done through the firmware.

[Edited by DJ Dunk - 3/7/2003 11:05:00 PM]

Andrewza

Traceroute isn't a protocol, it's an abuse of various protocols
Windows sends ICMP echos with increasing TTLs and listens for ICMP Time Exceeded whereas most unices send UDP packets with increasing TTLs and listen for ICMP "time exceeded" or ICMP "port unreachable". So no it's not a protocol, it's an abuse of TTL to extract responses from intermediate hosts, of course some can ignore the TTL and pass on regardless so there may be more hops that you're not seeing.


Back to the original problem. No it's not DNS, everyone else has already resolved it to the same IP, so it's not a problem you can fix. The whois record for the domain says it was lasted updated 12-Jan and the name servers listed are in the same subnet as the site itself, so it looks like it's pointing to the right IP, it's just the server itself was not responding. As far as I can see this has nothing to do with your ADSL modem unless it mysteriously likes to start dropping connections to port 80 on that particular IP.

The site seems to be up now...

[Edited by Andrewza - 3/7/2003 11:20:03 PM]