Having problems accessing most websites ...

[pow]

Hi all, I still can't access most websites despite re-installing windows, buying a speedtouch 546 router, new hard drive and carrying out all the test I could think of. This problem started after having my Broadband speed increased from 2 to 8Mb. BT says all is fine from their end. Strangely my line could take up to 5.5Mb as I'm under 1.7km from the exchange.

I have done a trace route on most of these websites, tested my new router from the master socket and configured all my setting without joy.

Please help as I'm now worst than when I was on 2Mb. I know I could get up to 5mb which I did from my previous ISP.

Please as many suggestions would be useful, as i can only access this site from work and I need to sort this out this weekend.

many thanks

[Nerval]

Have you made sure you  let the router set up its own connection (without using the supplied disk) so it sorts out your IP and DNS for you?
And made sure that on the computer, Windows Network Connections in Control Panel refers only to LAN and doesn't try and control the Internet in any way that could interfere with the router.

MTU is sometimes thought of as a problem, so use DRTCP to make sure it's set to 1500.

[pow]

Thanks for the reply.

Well, i used the supplied CD to set it up. So you saying I should just connect up the router without loading the supplied software and the correct setting should be picked up automatically.

[Nerval]

That's best.

I always recommend ignoring supplied CDs with everything.

I'd poke a small object in the reset hole of the back of it to reset it to factory settings, then just put in your username and ID and let it pick up your IP and DNS for you.
That way you don't risk telling it to pick up the wrong things.

It's actually easier to setup that way.

[Rik]

It might also be worthing flushing the DNS:

Start > Run > CMD [enter]

then type

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

If problems persist, do an ipconfig /all, cut and paste the results here.

[pow]

Thanks Rikbean and Nerval for the suggestions, I will give it a try. I am very keen to have my internet up and running again over the weekend so any more suggestions would be appreciated.

Thanks again..

[Nerval]

It would be worth your while ringing IDNet support and telling them the problem, and see if they have any other suggestions to go on your list.
Explain that you can't ring them while it's happening as they're shut tomorrow.

[pow]

It would be worth your while ringing IDNet support and telling them the problem, and see if they have any other suggestions to go on your list.
Explain that you can't ring them while it's happening as they're shut tomorrow.

Yes I have been working with IDNet support for the last 14 days and they have been very helpful in trying to resolve this problem. Their last suggestion was I try a new router from the master socket and re-install windows. Hence i'm trying to get as many suggestions to try out over the weekend.

Many thanks

[Nerval]

Only other place might be worth asking is Think Broadband Technical Forum (ADSL Guide as was).

There seem to be lots of knowledgeable people there, but they do usually want a lot of detail about the problem.

[Rik]

Their last suggestion was I try a new router from the master socket and re-install windows. Hence i'm trying to get as many suggestions to try out over the weekend.

Sounds like they suspect a problem with Windows (I assume) DNS resolution.

Try also:

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

[pow]

Thanks guys.

If all fails, I might just give up and go back to my stable 2Mb 

[Rik]

Max should work for you, as it does for the vast majority. Typical problems are to do with line stability, eg frequent disconnects, not accessing websites. The latter is more likely to be down to a DNS or MTU problem. I see that people have suggested changing MTU over on the TB forum, 1458 works well for me, but 1430 is another figure to try.

Can you identify the exact moment at which the problem started, ie was it when the line re-graded or did something else coincide, eg a software change.

I've been helping a friend through a similar issue this week, it transpires that he allowed IE to automatically update to IE7, but as it was running in the background, it didn't complete and completely messed his DNS.

[pow]

My MTU is currently set at 1458. I might try out 1430 as you suggested.
Yes it all started when my line was re-graded. I was getting 1.7 - 1.8Mb on my 2Mb line. I'm getting less than that now.
I still using IE6 and firefox (new version)

[Nerval]

I see you posted on the IDnet bit of TB.  I'd have tried the technical bit where more people read.  I don't think it's an IDNet problem.

[Rik]

He has, Nerv, I've put a crosspost marker on it.

[Rik]

Yes it all started when my line was re-graded. I was getting 1.7 - 1.8Mb on my 2Mb line. I'm getting less than that now.
I still using IE6 and firefox (new version)

Sorry, can you clarify the problem for me? Is it that you can't access websites or that your speeds are slow? If the latter, I presume you are still in your 'training' period. Have you done a test with the BT tester here. That will give your profile, which is the 'speed limit' that BT are applying to your line.

Have you tested from the test socket, behind the master socket, assuming you have an NTE5. This will disconnect all your internal phone wiring and give us the clearest picture of your connection. Post your router stats there and in your normal connection place so we can compare.

[pow]

Sorry, can you clarify the problem for me? Is it that you can't access websites or that your speeds are slow? If the latter, I presume you are still in your 'training' period. Have you done a test with the BT tester here. That will give your profile, which is the 'speed limit' that BT are applying to your line.

Have you tested from the test socket, behind the master socket, assuming you have an NTE5. This will disconnect all your internal phone wiring and give us the clearest picture of your connection. Post your router stats there and in your normal connection place so we can compare.

The main problem is not being able to access majority of the websites (98%) apart from a handful I frequently visit i.e. homepage, google/speed test site and a couple of online stores and they also take ages to load. The reference to speed was a recent speedtest I did that says I'm getting 1.3mb

I can't even access the BT tester, and I have the router plugged behind the master socket as mentioned too. 

Below are some recent test I did if it makes any sense to you

Testing Ethernet connection   PASS   
Testing ADSL line for sync   PASS   
Testing Ethernet connection to ATM   PASS   
Testing Telco Connectivity
Testing ATM OAM segment ping   PASS   
Testing ATM OAM end to end ping   PASS   
Testing ISP Connectivity
Testing PPPoE server connectivity   N.A.   
Testing PPPoE server session   N.A.   
Testing authentication with server   PASS   
Validating assigned IP address 212.69.**.***   PASS   
Testing Internet Connectivity
Ping default gateway 212.69.63.**   FAIL   
Ping Primary Domain Name Server   PASS   
Query DNS for www.bt.com   PASS   


DSL Parameters and Status
Vendor ID:   00B5GSPN
Revision Number:   Y1921a
Serial Number:   1234567abcdx
Local Tx Power:   11.95 dB
Remote Tx Power:   19.38 dB
Local Line Atten.:   34.0 dB
Remote Line Atten.:   22.0 dB
Local SNR Margin:   16.0 dB
Remote SNR Margin:   20.0 dB
Self Test:   Passed
DSL Standard:   G.dmt
Trellis Coding:   Disable
Framing Structure:   Framing-3


Tracing route to www.idnet.net [212.69.36.10]
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.

Thank you again

[Rik]

The failure to ping the default gateway is odd, as is your tracert, mine shows thus:

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    33 ms    28 ms    28 ms  telehouse-gw-msdp.idnet.net [212.69.63.41]
  3    31 ms    31 ms    28 ms  212.69.63.10
  4    33 ms    30 ms    31 ms  redbus-gw.idnet.net [212.69.63.1]
  5    33 ms    33 ms    33 ms  www.idnet.net [212.69.36.10]

Trace complete.

Have you tried manually pinging your router, does that work? What produced that list of tests. You said you'd bought a new router, have you tried with the old one. I think I also read, was it over on TB, that you'd bought a new HD - why was that?

[pow]

Have you tried manually pinging your router, does that work? What produced that list of tests. You said you'd bought a new router, have you tried with the old one. I think I also read, was it over on TB, that you'd bought a new HD - why was that?

I'm not sure how to manually ping the router. The old and my new router produced almost similar results. Well I did a fresh install and used the opportunity to get a new HD.

I have been offered to call out a BT engineer to check that all is ok. However I maybe to be charged £68.75 if the problem turns out to be my hardware.

All is turning out to be more expensive than i anticipated...

[Rik]

I'm not sure how to manually ping the router.

Start > Run > type CMD [enter]

in the resulting window, type:

ipconfig /all

You'll get something like this:

        Host Name . . . . . . . . . . . . :  (whatever)
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Generic Marvell Yukon Chipset based
Ethernet Controller
        Physical Address. . . . . . . . . : 00-15-58-73-6F-85
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.0.2
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.1
        DHCP Server . . . . . . . . . . . : 192.168.0.1
        DNS Servers . . . . . . . . . . . : 192.168.0.1
        Lease Obtained. . . . . . . . . . : 02 February 2007 07:57:27
        Lease Expires . . . . . . . . . . : 03 February 2007 07:57:27

The IP address is your computer, the default gateway/DHCP/DNS servers is the router.


PING <router IP>

In the case above, you'll get something like this:

C:\WINDOWS\system32>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time=2ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255

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

The old and my new router produced almost similar results. Well I did a fresh install and used the opportunity to get a new HD.

OK, so we can rule out hardware, though not necessarily your Windows installation. Try doing another ping, this time to www.bbc.co.uk

I have been offered to call out a BT engineer to check that all is ok. However I maybe to be charged £68.75 if the problem turns out to be my hardware.

All is turning out to be more expensive than i anticipated...

That's a minimum charge. If he finds your wiring is at fault, he will offer you the choice of having it disconnected (which I believe is free) or fixed. If you opt for the latter, it depends how long it takes. Mine cost £75.

[pow]

Thanks for the great response. I wil try and exhaust every option b4 calling out an engineer.

I will keep you posted..

[Rik]

Good luck. I'll be around over the weekend (rugby aside) both here and over on TB.

[pow]

Have you made sure you  let the router set up its own connection (without using the supplied disk) so it sorts out your IP and DNS for you?
And made sure that on the computer, Windows Network Connections in Control Panel refers only to LAN and doesn't try and control the Internet in any way that could interfere with the router.

MTU is sometimes thought of as a problem, so use DRTCP to make sure it's set to 1500.

Morning Nerval tried the above and no luck

[pow]

Hi,

Here are some test results from the weekend.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : dr1
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : lan

Ethernet adapter Local Area Connection 2:

        Connection-specific DNS Suffix  . : lan
        Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
        Physical Address. . . . . . . . . : 00-01-29-F5-DB-3E
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.64
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.254
        DHCP Server . . . . . . . . . . . : 192.168.1.254
        DNS Servers . . . . . . . . . . . : 192.168.1.254
        Lease Obtained. . . . . . . . . . : 04 February 2007 11:15:42
        Lease Expires . . . . . . . . . . : 05 February 2007 11:15:42



Pinging [193.10.252.19] with 32 bytes ->bytes=32 time=57ms TTL=245
Pinging [193.10.252.19] with 32 bytes ->Request Timed Out
Pinging [193.10.252.19] with 32 bytes ->bytes=32 time=51ms TTL=245
Pinging [218.32.192.112] with 32 bytes ->bytes=32 time=321ms TTL=46
Pinging [218.32.192.112] with 32 bytes ->bytes=32 time=314ms TTL=46
Pinging [218.32.192.112] with 32 bytes ->bytes=32 time=316ms TTL=46
Pinging [204.127.135.135] with 32 bytes ->Request Timed Out
Pinging [204.127.135.135] with 32 bytes ->Request Timed Out
Pinging [204.127.135.135] with 32 bytes ->Request Timed Out
Pinging [207.155.248.45] with 32 bytes ->Request Timed Out
Pinging [207.155.248.45] with 32 bytes ->Request Timed Out
Pinging [207.155.248.45] with 32 bytes ->Request Timed Out
Pinging [66.230.207.58] with 32 bytes ->Request Timed Out
Pinging [66.230.207.58] with 32 bytes ->Request Timed Out
Pinging [66.230.207.58] with 32 bytes ->Request Timed Out
Ping statistics for above hosts:
  Packets: Sent = 15, Received = 5, Lost = 10 (67% loss)
Approximate round trip times (RTT) in milli-seconds:
  Minimum = 51ms, Maximum =  321ms, Average =  70ms


What do you make out from these test results?

Many thnaks

[Nerval]

Well your ipconfig looks just the same as mine, so that's OK.

I suppose you really need to rule out the components one by one.

So you need first to try a different router/modem and see if you still get it.
Then a different computer - borrow a laptop - and see if you still get it.

If it's there with both a different router and computer, then it's BT/IDnet - doesn't matter which as IDNet are your contact anyway.