Having problems accessing most websites ...

Started by pow, Feb 02, 2007, 09:51:57

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Rik

Quote from: pow on Feb 05, 2007, 10:17:23
Here are some test results from the weekend.

What happens if you ping the router, Pow?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Ray

Pow have you tried disabling web browsing interception in your router System Configuration.
The setting for my Speedtouch 585 are shown below and these work fine for me.

System Configuration   

This page summarizes the current configuration of your SpeedTouch.

   Service Configuration

This section contains information regarding the service configuration currently applying to your SpeedTouch.
         
Service Name:   Data (Default) (modified by user)

   Time Configuration
         
Time Source:   Automatic
Date:   05-02-2007
Time:   11:01:47
Timezone:   (UTC) GMT: Dublin, Edinburgh, London
Summer Time:   No
Time Since Power-on:   18 days, 19:57:00
Time Server 1:   time.windows.com
Time Server 2:   time.nist.gov
Time Server 3:   time.nist.com

   System Configuration
         
Web Browsing Interception:   Disabled
Ray
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Nerval

I've got that router and my Web Browser Interception is set to Automatic - the default I assume - and that works OK.

pow

Quote from: rikbean on Feb 05, 2007, 10:38:40
What happens if you ping the router, Pow?

Hi Rik, the result was something like this:

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

pow

Quote from: Sheltieuk on Feb 05, 2007, 11:11:51
Pow have you tried disabling web browsing interception in your router System Configuration.


I think mine is set to Automatic too. I will give your suggestiona try.

Many thanks

Rik

Hi Pow

If you can ping the router, then you know that the connection is OK, that suggests that it may be a DNS issue.

Try pinging www.bbc.co.uk, if that doesn't work, try pinging 212.58.224.55, if that works then your DNS is the issue. OTOH, if the first one works, DNS is working.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pow

Thanks Rik. I will try that when I get home from work.

Rik

We'll get you there if it kills us, though preferably that would be everyone else but me. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

But then you wouldn't have anyone else to give help and support to Rik! Plus the forum would be a lonely place!
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

pow

Quote from: rikbean on Feb 05, 2007, 12:46:21
We'll get you there if it kills us, though preferably that would be everyone else but me. :)

Thanks Rik, that's the spirit we all need to see with customer services..

Rik

I come under the heading of customer dis-service. :) :out:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Quote from: lance on Feb 05, 2007, 13:47:41
But then you wouldn't have anyone else to give help and support to Rik! Plus the forum would be a lonely place!

I'd have to persuade Sue to let me work on her, Lance! :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pow

Quote from: rikbean on Feb 05, 2007, 11:49:35
Hi Pow

If you can ping the router, then you know that the connection is OK, that suggests that it may be a DNS issue.

Try pinging www.bbc.co.uk, if that doesn't work, try pinging 212.58.224.55, if that works then your DNS is the issue. OTOH, if the first one works, DNS is working.


Hey Rik just got a friend back to mine place to try it out. Yes the DNS is the problem. Now how do i resolve this. I'm excited as I'm getting somewhere at last

Many thanks

Rik

This is the third DNS problem I've come across in a week. Do you have IE7 on the machine by any chance?

Try the things I suggested earlier in the thread:

Flush the DNS

Start > Run > CMD [enter]

then type

ipconfig /flushdns [enter]
ipconfig /registerdns [enter]

If problems persist, try -

Start > Run > CMD [enter]

then type:

netsh int ip reset C:\resetlog.txt [enter]

If you get an error message, use interface instead of int. Re-boot, then check your hosts file, usually in C:\windows\system32\drivers\etc. Open it with Notepad and check that there's no entries in there other than:

127.0.0.1       localhost

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pow

Quote from: rikbean on Feb 05, 2007, 14:44:56
Do you have IE7 on the machine by any chance?

Try the things I suggested earlier in the thread:

Flush the DNS



I still have the IE6 on, and flushed the DNS as suggested. I hope this is not sounding too silly to ask but I'm a complete novice with this.

I did open the file with notebook, and this is a sample of the entry:

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.78 rhino.acme.com          # source server
#       38.21.63.10     x.acme.com              # x client host

127.0.0.1       localhost


So, is this right or it only has to be:  127.0.0.1       localhost

I hope I'm not becoming a pain, but really appreciate your help.



Rik

Pow

The only silly people are the ones who don't ask for help or pretend they know everything when they don't. My favourite word is why, so you'll never outdo me in the questions stakes. :)

Your hosts file is perfect, all the stuff on lines starting with # is comment, and can be ignored. I didn't quote it to avoid complicating the issue, but looking back, perhaps I complicated the issue by not posting it. ;)

Don't worry, you're not being or becoming a pain. If we didn't want to try and help, we wouldn't be here. No guarantees of success, but we'll all try.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pow

Quote from: rikbean on Feb 05, 2007, 15:26:49
Pow

The only silly people are the ones who don't ask for help or pretend they know everything when they don't. My favourite word is why, so you'll never outdo me in the questions stakes. :)

Your hosts file is perfect, all the stuff on lines starting with # is comment, and can be ignored. I didn't quote it to avoid complicating the issue, but looking back, perhaps I complicated the issue by not posting it. ;)

Don't worry, you're not being or becoming a pain. If we didn't want to try and help, we wouldn't be here. No guarantees of success, but we'll all try.

Thanks mate.

Ok my host file is all good, what next?

Rik

Have you done everything else I suggested?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pow

Quote from: rikbean on Feb 05, 2007, 16:00:59
Have you done everything else I suggested?

Yes Rik, infact I re-installed windows just in case. I have also maually set the router to pick up IP, flushed DNS, connected to master (test) socket and disconnected all other phone device.

If there's nothing else to do, I guess i have to go back to my 2mb  :(

Thank you for all your all your support

Rik

I don't feel that this is a Max-related problem, the issue is much more likely to be in your network setup.

Can you either (a) get your computer to a friend's house and see if it will work there, or (b) get a friend with a known good configuration to bring his machine to your place. That will eliminate everything except the router or the connection itself, so add moving routers to (a) & (b) above to eliminate that possibility.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Nerval

Or as I said above, you need to eliminate things  one at a time.

So try a different router or modem and see if the problem persists.  If so, it's not your router.
Then try a different computer/laptop.
You will then know where the problem is.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Nerval

I wonder how many karmas it is for an IDNet paid trip to nirvana?

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pow

Quote from: rikbean on Feb 05, 2007, 11:49:35
Hi Pow

If you can ping the router, then you know that the connection is OK, that suggests that it may be a DNS issue.

Try pinging www.bbc.co.uk, if that doesn't work, try pinging 212.58.224.55, if that works then your DNS is the issue. OTOH, if the first one works, DNS is working.


Howdy

Had some spare last nite to get more grey hair on my never ending problem. I did a number of pings on non accessible sites using both IP address and URL, and both didn't work. I also tested this with an old PC which produced similar results.
So would this suggest a problem from BT or IdNet?

Many thanks