NTL woes.

Anyone else having problems with certain webpages no resolving ? I can type
in a site and I get page cannot be displayed, but at work they work fine.

On Mon, 29 Sep 2003 10:00:52 +0100 and in article <Zj2dnbV-WL9baeqiU-
(E-Mail Removed)>, Bulla said...
: Anyone else having problems with certain webpages no resolving ? I can type
: in a site and I get page cannot be displayed, but at work they work fine.
:
Use another DNS.

--
chris

On Mon, 29 Sep 2003 10:00:52 +0100, Bulla wrote:

> Anyone else having problems with certain webpages no resolving ? I can type
> in a site and I get page cannot be displayed, but at work they work fine.

Hi

As Chris already mentioned use another DNS server *or* install your own,
have a look here http://tinyurl.com/p10m

HTH

Regards

Bill

In article <1gsmkossglky9$.1901mguojv1en$.(E-Mail Removed)>,
phoenix <(E-Mail Removed)> wrote:
>> Anyone else having problems with certain webpages no resolving ? I can type
>> in a site and I get page cannot be displayed, but at work they work fine.
>
>As Chris already mentioned use another DNS server *or* install your own,
>have a look here http://tinyurl.com/p10m

Not especially useful, as the ntl: web proxies use the same DNS servers,
so after your PC's looked up the IP address from the FQDN and makes the
port 80 connection, it's intercepted by the web proxies and looked up
again -- where it will fail.

Bypassing ntl's DNS servers is only useful for non-HTTP traffic.

More likely to work is to explicitly set a web proxy in the browser.

Zane.

"Zane Wilson" <abuse@DO_NOT_SEND_UCEwilson.st> wrote in message
news:uril41-(E-Mail Removed)...
> In article <1gsmkossglky9$.1901mguojv1en$.(E-Mail Removed)>,
> phoenix <(E-Mail Removed)> wrote:
> >> Anyone else having problems with certain webpages no resolving ?
I can type
> >> in a site and I get page cannot be displayed, but at work they
work fine.
> >
> >As Chris already mentioned use another DNS server *or* install your
own,
> >have a look here http://tinyurl.com/p10m
>
> Not especially useful, as the ntl: web proxies use the same DNS
servers,
> so after your PC's looked up the IP address from the FQDN and makes
the
> port 80 connection, it's intercepted by the web proxies and looked
up
> again -- where it will fail.
>
> Bypassing ntl's DNS servers is only useful for non-HTTP traffic.
>
> More likely to work is to explicitly set a web proxy in the browser.

Not quite correct as if you stipulate which server to use (in your
connection properties) you can effectively sidestep the one NTL tries
to fob you off with..

Yes it does work...

goto http://www.nthellworld.com/

JPD

"Bulla" <(E-Mail Removed)> wrote in message
news:Zj2dnbV-WL9baeqiU-(E-Mail Removed)...
> Anyone else having problems with certain webpages no resolving ? I can
type
> in a site and I get page cannot be displayed, but at work they work fine.
>
>


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.521 / Virus Database: 319 - Release Date: 23/09/03

"Bulla" <(E-Mail Removed)> wrote in message
news:Zj2dnbV-WL9baeqiU-(E-Mail Removed)...
> Anyone else having problems with certain webpages no resolving ? I can
type
> in a site and I get page cannot be displayed, but at work they work fine.
>
>

Try the advice here
http://homepage.ntlworld.com/robin.d...trancache.html about
explicitly setting your web proxy as this is likely to be the problem.
There are a large number of NTL users currently experiencing the same
problems you are having and in the majority of cases the instructions
contained on this page will resolve it.

Raist.

In article <NLZdb.2753$(E-Mail Removed)>,
Kraftee <(E-Mail Removed)> wrote:
>> Bypassing ntl's DNS servers is only useful for non-HTTP traffic.
>>
>> More likely to work is to explicitly set a web proxy in the browser.
^^^^^^^^^^^^^^^^^^^^^^^^^^
>Not quite correct as if you stipulate which server to use (in your
>connection properties) you can effectively sidestep the one NTL tries
>to fob you off with..
>
>Yes it does work...

Yes I know - that's exactly what I said! (see above). Been there, done
that since October 1999. Many is the time I've cursed not keeping a copy
of Robin Walker's proxy list handy for the odd occasion when my
transparent one plays up. Then I have to try to remember the format of the
FQDNs for the proxies.

Using a non-ntl: dns but still using their transparent proxy won't work if
ntl:'s dns is broken, after the successful non-ntl: dns lookup your
browser does the request will be intercepted by the transparent proxy, and
because the transparent proxy will then nslookup, which will fail. Setting
an explicit proxy will cause the browser to send the http request direct
to the proxy *without* first trying its own dns lookup, so that will work
even if ntl:'s dns is flakey and you haven't pointed at a different one.

Zane.

Raistlin wrote:
> "Bulla" <(E-Mail Removed)> wrote in message
> news:Zj2dnbV-WL9baeqiU-(E-Mail Removed)...
>> Anyone else having problems with certain webpages no resolving ? I
>> can type in a site and I get page cannot be displayed, but at work
>> they work fine.
>>
>>
>
> Try the advice here
> http://homepage.ntlworld.com/robin.d...trancache.html
> about explicitly setting your web proxy as this is likely to be the
> problem. There are a large number of NTL users currently experiencing
> the same problems you are having and in the majority of cases the
> instructions contained on this page will resolve it.

My mother in law is on NTL. Last week she had problems viewing the
Sainsbury's home shopping site. She phoned the Sainsbury's helpline, and
when she stated she was on NTL, the chap the other end said that was the problem,
and talked her through the procedure for altering her proxy settings.
(or that's what I can gather from her descriptions :-) )

"Bulla" <(E-Mail Removed)> wrote in message news:<Zj2dnbV-WL9baeqiU-(E-Mail Removed)>...
> Anyone else having problems with certain webpages no resolving ? I can type
> in a site and I get page cannot be displayed, but at work they work fine.

My parents were having the same problem last night. I e-mailed NTL
helpline since they couldn't get through to them on the phone (always
busy). I received an automatic response saying the message was
rejected since the user's (i.e. helpline's) inbox was full!.

They definitely know how to treat customers.