solap troubles

muman42 · Post by **muman42** » Mon Sep 21, 2009 3:53 pm

Hmmm, still no joy, upgraded and shortened my modem cable. Karoo is my service provider, yorkshire the location, think its worth ringing my provider still? Thx 4 all assistance.

Mu

Post by **FreeBeer** » Mon Sep 21, 2009 11:14 pm

Probably Sgt_Baker is the best one to answer that. He's more likely to be familiar with UK-based ISPs and routings than I am.

(Note how I deftly passed the buck

)

sgt_baker · Post by **sgt_baker** » Tue Sep 22, 2009 9:01 am

I think I've identified a problem which evaded my attention initially. Solap's IP is 66.36.240.92, not the IP address you're tracing and pinging in your previous post. You appear to have managed to trace to a host address which doesn't exist (solap.fe.co.uk), which should have resulted in the message "Unable to resolve target system name solap.fe.co.uk." The proper address is solap.fe23.co.uk, which should resolve to the IP mentioned previously.

Please re-ping and trace to the correct address.

Code: Select all

ping solap.fe23.co.uk
tracert solap.fe23.co.uk

Cheers!

muman42 · Post by **muman42** » Tue Sep 22, 2009 10:42 am

Here's the new results just in...]

ping solap.fe23.co.uk

Pinging solap.fe23.co.uk [66.36.240.92] with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for 66.36.240.92:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

tracert solap.fe23.co.uk

Tracing route to solap.fe23.co.uk [66.36.240.92]
over a maximum of 30 hops:

1 Destination host unreachable.

Trace complete.

even worse than the results from pinging a non existant server.

ta boodah's

sgt_baker · Post by **sgt_baker** » Tue Sep 22, 2009 11:57 am

In that case it appears that you have a totally dead route on your hands. Fortunately, this is something you can call your ISP about. It's their responsibility to ensure you have uninterrupted access to the entire internet. Should simply be a matter of a quick call to tech and giving them Solap's address with a brief description of the problem.

For that matter, such issues, whilst rare, usually resolve themselves once the ISPs and transit providers realise that something is wrong. Either way, a phone call to the relevant parties wouldn't hurt in this instance.

Edit: This situation usually arises when there is either a dispute or plain mistake between a pair of the top-level bandwidth providers from whom you ISP buys bandwidth. Alternatively, your ISP may have misconfigured a router somewhere. What I'm getting at here is this: For once (woohoo) the problem has nothing to do with Solap or Solap's HSP... which is a pleasing breath of fresh air!

P.S. Where are you in Yorkshire? I ask because I'm 50% Yorkshirian myself.

muman42 · Post by **muman42** » Tue Sep 22, 2009 12:57 pm

woooo. 1 phone call later and hey presto.... don't know the technical details only i asked them to do ping solap and they couldn't, half an hour later and we're on, Hull be the domain of mu. All i need now is time for a game

thx again

tracert solap.fe23.co.uk

Tracing route to solap.fe23.co.uk [66.36.240.92]
over a maximum of 30 hops:

1 9 ms 8 ms 9 ms 10.0.0.2
2 11 ms 10 ms 10 ms 77.86.56.254
3 10 ms 10 ms 11 ms 10.102.240.129
4 39 ms 10 ms 9 ms 10.102.240.221
5 13 ms 12 ms 13 ms 10.102.59.6
6 13 ms 13 ms 13 ms 195.50.119.5
7 22 ms 22 ms 22 ms ae-4-4.ebr1.London1.Level3.net [4.69.133.102]
8 21 ms 22 ms 22 ms ae-100-100.ebr2.London1.Level3.net [4.69.141.166
]
9 90 ms 91 ms 91 ms ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]

10 95 ms 106 ms 107 ms ae-3-3.ebr4.Washington1.Level3.net [4.69.132.93]

11 103 ms 108 ms 108 ms ae-74-74.csw2.Washington1.Level3.net [4.69.134.1
82]
12 96 ms 95 ms 96 ms ae-21-79.car1.Washington1.Level3.net [4.68.17.67
]
13 * * * Request timed out.
14 * * * Request timed out.
15 95 ms 95 ms 94 ms 66.36.240.92

Trace complete.

ping solap.fe23.co.uk

Pinging solap.fe23.co.uk [66.36.240.92] with 32 bytes of data:

Reply from 66.36.240.92: bytes=32 time=94ms TTL=114
Reply from 66.36.240.92: bytes=32 time=93ms TTL=114
Reply from 66.36.240.92: bytes=32 time=93ms TTL=114
Reply from 66.36.240.92: bytes=32 time=93ms TTL=114

Ping statistics for 66.36.240.92:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 94ms, Average = 93ms

sgt_baker · Post by **sgt_baker** » Tue Sep 22, 2009 1:01 pm

Cool beans. Hull and South Cave are the domains of the Bakers too. My sis is currently at uni in your exact location, and half of the family is in Cave. Small world, eh?