Re: Anyone on NTL Freedom dialup here?
 

The original post was made under the proxies section, as at that time I suspected proxies may be either party or wholly responsible. Having made a certain amount of progress with the help of people in that area, I started a seperate thread under the dialup section to try and find someone on the same connection and solicit their aid in trying to duplicate my problem.

I am fully familiar with forums and their usage and if you look closer at the thread you will see I had already bumped it shortly before I started the 2nd. The 2nd was not intended as a "double post" about the same problem, it's aim was to try and obtain additional information about a specific sub-area of my problem - the ntl dialup account - without moving the entire thread away from those with the best knowledge and experience to help. Although I now agree that it is almost certainly not a proxy issue, I do not feel it is uniquely related to dialup access either and thus not best suited to the dialup area. The proxies area was (at the time of my original post) the best area to begin with the information I had at the time. As there is no "Weird routing problems" area I can't help but feel that combining the threads here under dialup can only reduce the chances of my gaining assistance, since most of the people with relevant knowledge (particularly those that were already helping) will now have no idea where this thread has gone.
__________________

As I noted yesterday, DNS appears to be resolving IP's fine, its after the correct IP is returned that problems start. Like the 6 I ran yesterday, the BBC trace works fine after failing the first hop - I'm sure this is highly significant but I have no idea what of :D. Tracert to the problem IP never gets off the ground - every hop times out, even when set to 10000ms. The way I see it, a normal packet is given a set of directions to get to the destination -

"Go to this ip, then they will tell you where to go next, repeat until you get there."

In my case however, the first direction is a dead end - the packets just pile up and die lol :shocked:

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

C:\Documents and Settings\George>tracert 212.58.228.154

Tracing route to bogons.mh.bbc.co.uk [212.58.228.154]
over a maximum of 30 hops:

1 * * * Request timed out.
2 194 ms 149 ms 149 ms gb-bir-c-r2-ge60.inet.ntl.com [80.1.208.194]
3 157 ms 155 ms 149 ms gb-lth-c-r1-pos150.inet.ntl.com [80.1.209.109]
4 158 ms 149 ms 155 ms gb-lth-c-r2-pos00.inet.ntl.com [80.1.209.222]
5 163 ms 154 ms 149 ms gb-ldk-c-r1-pos150.inet.ntl.com [80.1.209.121]
6 166 ms 155 ms 149 ms pop-ic-1-ge-010-0.inet.ntl.com [62.253.184.249]

7 166 ms 149 ms 149 ms pop-bb-a-ge-701-0.inet.ntl.com [62.253.184.246]

8 184 ms 155 ms 167 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]

9 161 ms 155 ms 155 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
10 161 ms 157 ms 155 ms 212.58.238.129
11 158 ms 154 ms 161 ms 212.58.238.34
12 172 ms 148 ms 155 ms pos6-0.rt0.mh.bbc.co.uk [212.58.239.30]
13 172 ms 161 ms 155 ms bogons.mh.bbc.co.uk [212.58.228.154]

Trace complete.

C:\Documents and Settings\George>tracert 222.122.25.35

Tracing route to 222.122.25.35 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

----------------------------------------------------
__________________

Hmmm...when reviewing my last post I noticed something interesting - the tracert for 212.58.228.154 does a reverse DNS lookup and gives the correct domain name. The tracert for 222.122.25.35 doesnt do that, just has the IP. Again I'm sure this is significant but I'm fresh out of relevant knowledge of how these packets are routed :-(

Re: NTL Freedom problem
 

Bizarre - it does appear to have no route almost from the kick off - can you route to any 222.x.x.x addresses. The rDNS is not really significant, lots of ip addresses do not have a reverse lookup record.

Re: NTL Freedom problem
 

Ok, found about half a dozen 222.x addresses that produced a reverse dns name so should be tracert-able (oooh new word :-) ) - all failed totally, same as the other.

Re: New proxy problem...or is it?
 

While dialup proxies are connection specific, they are set still up through Internet Options rather than through DUN, and like cable proxies won't affects ports other than those specified (e.g. port 80, 81 etc).


My advice would be to email a description of the problem along with the tracert results and the IP address assigned to you at the time you ran them to support@ntlfreedom.com so that the issue can be raised with the faults department.

For reference, here's a partial successful tracert

9 10 ms 10 ms 10 ms tele-ic-1-so-110-0.inet.ntl.com [62.253.185.78]
10 161 ms 170 ms 170 ms kt-london.router.fe1 [195.66.224.147]
11 290 ms * 291 ms 211.48.63.229
12 290 ms 291 ms 300 ms apnc10 [211.216.216.97]
13 290 ms 291 ms 300 ms 220.73.167.182
14 291 ms 300 ms 291 ms 218.145.44.54
15 290 ms 291 ms 300 ms 211.106.158.186
16 291 ms 290 ms 301 ms 211.216.53.117
17 310 ms 561 ms 291 ms 222.122.25.33
18 290 ms 301 ms 290 ms 222.122.25.35

Re: NTL Freedom problem
 

Thanks, I already mailed support last week - no response (shock horror gasp). I'm off home today and back to lovely broadband so I guess this 1 will just have to remain unsolved!

Digitus