PIPEX ADSL Problem - Please help...!
Discussion
I have been using PIPEX ADSL at home for about 9 months now and it's been great, but the past two weeks a problem has come to light.
As a member of the Ford RS Owners Club and the show season upon us, I need to get access to the website and forums to keep up to speed on what's happening. The past two weeks I have not been able to access the website or forums. The address is www.rsownersclub.co.uk for the site and http://bbs.rsownersclub.co.uk for the forums. All I get is 'Page Cannot Be Displayed - Server not Found' or whatever. No other sites that I visit seem affected.
A traceroute shows that the DNS lookup is fine, but the route stops after just 2 or 3 hops from my house somewhere in the PIPEX network.
I recently installed PIPEX ADSL at our Hotel in Warwickshire (some 150+ miles from home) and I Remote Desktop'd into the server there and it has exactly the same problem - Perfect DNS lookup but failing traceroute.
The site loads fine over GPRS, on my Brother's Wanadoo ADSL, Gaffer's Virgin ADSL and at my Dad's on his Wanadoo dialup so it's definitely a PIPEX issue.
Obviously I have mentioned it to them but they seem stumped (but I think in reality they are giving me the runaround).
I have provided them with traces showing where it stopped and suggested they investigate the particular device where it conks out, but so far nothing.
Suffice to say, there have been no system changes at 'my end' nor have there been at the hotel so that's not the issue.
PIPEX support asked me to use some different DNS servers (although I told them the DNS lookup was fine) and this, no surprise, made no difference at all. I have modified the MTU to all the usual settings with no effect.
So, has anyone any ideas on what to do and secondly, if you are a PIPEX user, can you please try loading up www.rsownersclub.co.uk and let me know what happens.
Thanks in advance,
Roop
PS : Tracert is below... :
Tracing route to www.rsownersclub.co.uk 62.73.174.121] over a maximum of 30 hops:
1 5 ms 3 ms 2 ms . [192.168.0.1]
2 21 ms 21 ms 19 ms loopback1.ar2.gs1.systems.pipex.net [62.241.161.244]
3 20 ms 18 ms 20 ms ge-2-0-0.cr1.gs1.systems.pipex.net [62.241.161.102]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 etc etc ...
>> Edited by roop on Monday 16th May 13:31
As a member of the Ford RS Owners Club and the show season upon us, I need to get access to the website and forums to keep up to speed on what's happening. The past two weeks I have not been able to access the website or forums. The address is www.rsownersclub.co.uk for the site and http://bbs.rsownersclub.co.uk for the forums. All I get is 'Page Cannot Be Displayed - Server not Found' or whatever. No other sites that I visit seem affected.
A traceroute shows that the DNS lookup is fine, but the route stops after just 2 or 3 hops from my house somewhere in the PIPEX network.
I recently installed PIPEX ADSL at our Hotel in Warwickshire (some 150+ miles from home) and I Remote Desktop'd into the server there and it has exactly the same problem - Perfect DNS lookup but failing traceroute.
The site loads fine over GPRS, on my Brother's Wanadoo ADSL, Gaffer's Virgin ADSL and at my Dad's on his Wanadoo dialup so it's definitely a PIPEX issue.
Obviously I have mentioned it to them but they seem stumped (but I think in reality they are giving me the runaround).
I have provided them with traces showing where it stopped and suggested they investigate the particular device where it conks out, but so far nothing.
Suffice to say, there have been no system changes at 'my end' nor have there been at the hotel so that's not the issue.
PIPEX support asked me to use some different DNS servers (although I told them the DNS lookup was fine) and this, no surprise, made no difference at all. I have modified the MTU to all the usual settings with no effect.
So, has anyone any ideas on what to do and secondly, if you are a PIPEX user, can you please try loading up www.rsownersclub.co.uk and let me know what happens.
Thanks in advance,
Roop
PS : Tracert is below... :
Tracing route to www.rsownersclub.co.uk 62.73.174.121] over a maximum of 30 hops:
1 5 ms 3 ms 2 ms . [192.168.0.1]
2 21 ms 21 ms 19 ms loopback1.ar2.gs1.systems.pipex.net [62.241.161.244]
3 20 ms 18 ms 20 ms ge-2-0-0.cr1.gs1.systems.pipex.net [62.241.161.102]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 etc etc ...
>> Edited by roop on Monday 16th May 13:31
I am on Pipex, same issue except stops at a different IP
Tracing route to www.rsownersclub.co.uk [62.73.174.121]
over a maximum of 30 hops:
1 51 ms 30 ms 46 ms 81-86-224-1.dsl.pipex.com [81.86.224.1]
2 93 ms 46 ms 108 ms eth3-1.cr1.uk5.systems.pipex.net [62.241.161.41]
3 * * * Request timed out.
4 * * * Request timed out.
5 ^C
Tracing route to www.rsownersclub.co.uk [62.73.174.121]
over a maximum of 30 hops:
1 51 ms 30 ms 46 ms 81-86-224-1.dsl.pipex.com [81.86.224.1]
2 93 ms 46 ms 108 ms eth3-1.cr1.uk5.systems.pipex.net [62.241.161.41]
3 * * * Request timed out.
4 * * * Request timed out.
5 ^C
Thanks guys,
As far as I can ascertain PL, it's not a DNS issue as the IP resolves just fine. Well, that's not quite true, it could well be a DNS issue, but at the node where the traceroute is failing, I have no access to the configuration of that node of course.
Thanks Cuneus, glad it's not just me. With you down in the South West that's three very different locations where it's failing on PIPEX. My ticket's still open so I'll send them a reminder and copy in your traceroute as well.
Cheers,
Roop
As far as I can ascertain PL, it's not a DNS issue as the IP resolves just fine. Well, that's not quite true, it could well be a DNS issue, but at the node where the traceroute is failing, I have no access to the configuration of that node of course.
Thanks Cuneus, glad it's not just me. With you down in the South West that's three very different locations where it's failing on PIPEX. My ticket's still open so I'll send them a reminder and copy in your traceroute as well.
Cheers,
Roop
my tracert said:
C:>tracert www.rsownersclub.co.uk
Tracing route to www.rsownersclub.co.uk [62.73.174.121]
over a maximum of 30 hops:
1 <snipped> Me!
2 24 ms 23 ms 23 ms gxnetworks-hg1.ilford.broadband.bt.net [217.41.2
08.72]
3 22 ms 22 ms 24 ms 217.41.208.2
4 23 ms 26 ms 23 ms 217.41.208.110
5 24 ms 26 ms 26 ms adsl.he4.core.rtr.gxn.net [195.147.14.99]
6 25 ms 26 ms 28 ms akamai.HE.core.rtr.gxn.net [195.224.252.33]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
etc
We're on GX networks, which I think were taken over by Pipex, but I'm not sure.
There's definitely a misconfigured router out there somewhere.
roop said:
Well, that's not quite true, it could well be a DNS issue, but at the node where the traceroute is failing, I have no access to the configuration of that node of course.
No DNS lookups occur except on your PC. It uses the IP for the entire journey.
I assume you've tried rebooting your router? I had a similar problem with Pipex and this cured it.
Bliarout to the rescue
It is a DNS thang.... The site has moved and the DNS records aren't updated. Your site is actually http://62.73.174.122 It doesn't load quite correctly, but as soon as you click the links, there it all is!
Edit: Apart from the forums.... The club need to get their ISP to update their DNS records and it'll take about 72 hours from then to propogate to all the other DNS's.
Just a bit of educated guesswork!
>> Edited by BliarOut on Monday 16th May 15:35
It is a DNS thang.... The site has moved and the DNS records aren't updated. Your site is actually http://62.73.174.122 It doesn't load quite correctly, but as soon as you click the links, there it all is!
Edit: Apart from the forums.... The club need to get their ISP to update their DNS records and it'll take about 72 hours from then to propogate to all the other DNS's.
Just a bit of educated guesswork!
My cunning bit of detective work said:
C:>tracert 62.73.174.122
Tracing route to eul0000568-sip.eu.verio.net [62.73.174.122]
over a maximum of 30 hops:
1 <snip> Moi!
2 41 ms 24 ms 23 ms gxnetworks-hg1.ilford.broadband.bt.net [217.41.2
08.72]
3 26 ms 23 ms 23 ms 217.41.208.1
4 27 ms 24 ms 24 ms 217.41.208.106
5 25 ms 26 ms 25 ms adsl.he4.core.rtr.gxn.net [195.147.14.99]
6 27 ms 32 ms 26 ms akamai.HE.core.rtr.gxn.net [195.224.252.33]
7 26 ms 29 ms 24 ms g1-1-2.cr02.hx2.bb.pipex.net [194.143.163.34]
8 25 ms 25 ms 33 ms p0-0.cr02.tn5.bb.pipex.net [62.72.137.5]
9 27 ms 31 ms 24 ms ge-0-1-1.r20.londen03.uk.bb.verio.net [217.79.16
1.10]
10 27 ms 26 ms 26 ms ge-1-5.c00.londen02.uk.wh.verio.net [213.130.47.
182]
11 23 ms 26 ms 30 ms v-10.d07-r0.londen02.uk.wh.verio.net [213.130.32
.208]
12 27 ms 31 ms 31 ms eul0000568-sip.eu.verio.net [62.73.174.122]
Trace complete.
>> Edited by BliarOut on Monday 16th May 15:35
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff