Quote:
|
Originally Posted by Aragorn
Yes, telnet needs to be run from command prompt as well.Another thing to try, if you haven't already, is downloading Firefox on to a memory stick/cd at work and loading that as an alternate browser.
|
I already have firefox on my pc at home - why would that make a difference - its my default browser
---------- Post added at 10:47 ---------- Previous post was at 10:46 ----------
Quote:
|
Originally Posted by jem
If you can ping an address ping www.bbc.co.uksay and get a response then DNS name resolution is working ok. Just to be sure try something a little more unusual just in case the address has been cached. I tend to use www.cisco.com on the grounds that unless you happen to work in IT it's very unlikely that the website has been recently viewed and the address has been cached.If the ping responses fail then you have a DNS problem.If this is ok then in the command prompt try the telnet command. If you get a successful connection then the internet connection is basically working.Lastly try entering www.bbc.co.uk into the web browser. If it fails then the problem is almost certainly a failed proxy. If you don't manually specify a proxy then your web traffic is routed via a transparent proxy which is supposed to be set up in such a way that NTL can load balence. Generally it works just fine but can sometime go a bit wrong. I recently had a real problem with Proxies in the south London area and had to work around them but it all seems to be fixed now.There is a help guide somewhere on how to manually set a proxy for IE and Firefox etc. and what addresses to put in. I can't remember where it is but I'm sure someone else will have the info and post it. Don't forget to try taking the manual proxy setting off after a few days though.Good Luck |
thanks - will give it a try later
i think the url with the proxies you are thinking of is:
http://homepage.ntlworld.com/robin.d...cache.html#ntl
i have noted some down to try later