Re: [Merged] Manchester Proxies.
 

heres the answer

cache9-mant.server.ntli.net (62.252.192.12)
62.252.192.0 - 62.252.223.255
NTL Internet
Manchester site

Re: [Merged] Manchester Proxies.
 

Weird I have the same one I have had since I first found out I was on proxies again even have a screen shot showing the ip number which didn't change even though I have been swapping cable modems around these last few weeks..


I am also getting DOS attacks from my my proxy according to the modem as its sent me emails saying I was under attack from the ip that is cache1.. The only one I have ever been on..... :shrug:

Re: [Merged] Manchester Proxies.
 

Erm - how is looking up the IP range for Manchester the answer to anything :confused:



Ignore them Kitty - it is just being over sensitive - I get them a few times a week - it is mis-interpreting real traffic.

Re: [Merged] Manchester Proxies.
 

Well what a revelation this thread is ;), I thought the proxies had been buried for ever, at least now I know why browsing has been hit and miss the last couple of days.

BBKing.
To help in your request for backing when you say there are problems I have just spoken to BB tech support to advise that I am having problems with intermittent outages.
Unfortunately I didn't get the guys name but 5 starts to him, very pleasant and helpful and none of the usual c**p about resetting the STB and PC.

If the top managers were forced to spend a month on front line support maybe NTL would fix things properly, or maybe they would just give up.
I feel sorry for TeleWest customers when the long standing rumours come to fruition.

Hope the proxies get fixed, or switched off again real soon.

Re: [Merged] Manchester Proxies.
 

62.252.192.12 is the only one I seem to be going through since they came back on, TBH I have had no real problems and noticed no degradation of service whatsoever.

AllNettools did show it at first but for some reason it now cannot detect it.

Re: [Merged] Manchester Proxies.
 

AllNettools can still detect my proxy might try yours :)

Re: [Merged] Manchester Proxies.
 

It shows its a cache

Re: [Merged] Manchester Proxies.
 

I think i should be upset :) I have not had any of the problems you all say your having. Why have i been left out its not fair :pp


I am on the south manchester cache here in warrington

Re: [Merged] Manchester Proxies.
 

Oh, ok, but then I had already said it was.

Re: [Merged] Manchester Proxies.
 

REMOTE_ADDR 62.254.0.38

Re: [Merged] Manchester Proxies.
 

LMFAO

sorry had to laugh

but seriously you dont pay for a 1mbit connection for sub 56k performance :(

Re: [Merged] Manchester Proxies.
 

So you are using exactly the same as the rest of us in Nottingham & surrounding areas - and they have been stable here for the last few months - very few problems.

Re: [Merged] Manchester Proxies.
 

pem you are saying these proxies have been on for last few months, this is simply not true for me, I maybe using the proxy servers in nottingham but I am not in nottingham so its quite easy my area was turned off, also I can repeat the proxy problems again and again and again. One click to turn of my proxy problem exists, another click to bypass ntl poroxy problem gone, its quite simple really one common factor in my problems and its the ntl trapserent proxy.

Tell me what you make of my report in the speedtest thread next to this, I posted the results.

Re: [Merged] Manchester Proxies.
 

Tracing route to cache9-nott.server.ntli.net [62.254.0.38]
over a maximum of 30 hops:

1 15 ms 15 ms 19 ms 10.146.151.254
2 70 ms 19 ms 19 ms leic-t2cam1-b-ge96.inet.ntl.com [80.7.30.145]
3 20 ms 19 ms 39 ms nott-t2core-b-ge-wan63.inet.ntl.com [80.1.79.197
]
4 110 ms 128 ms 130 ms cache9-nott.server.ntli.net [62.254.0.38]

Trace complete

Re: [Merged] Manchester Proxies.
 

It would seem the problem is with your UBR/gateway - is that a Shepshed area connection? Certainly my routeing seems cleaner:

Tracing route to cache9-nott.server.ntli.net [62.254.0.38]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 9 ms 13 ms 9 ms 10.145.***.***
3 9 ms 9 ms 9 ms nott-t2cam1-b-ge-wan53-137.inet.ntl.com [80.4.46
.193]
4 11 ms 9 ms 10 ms nott-t2core-b-ge-wan72.inet.ntl.com [80.1.79.189
]
5 10 ms 10 ms 11 ms cache9-nott.server.ntli.net [62.254.0.38]

Trace complete.