Having problems accessing most websites ...

pow · Feb 02, 2007, 09:51:57

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 · Feb 02, 2007, 09:59:06

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 · Feb 02, 2007, 10:11:49

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 · Feb 02, 2007, 10:15:18

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 · Feb 02, 2007, 10:49:40

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 · Feb 02, 2007, 10:55:51

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 · Feb 02, 2007, 10:58:54

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 · Feb 02, 2007, 11:16:43

Quote from: Nerval on Feb 02, 2007, 10:58:54
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 · Feb 02, 2007, 11:21:47

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 · Feb 02, 2007, 11:45:25

Quote from: pow on Feb 02, 2007, 11:16:43
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 · Feb 02, 2007, 12:11:38

Thanks guys.

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

Rik · Feb 02, 2007, 12:21:18

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 · Feb 02, 2007, 12:39:21

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 · Feb 02, 2007, 12:49:55

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 · Feb 02, 2007, 13:56:45

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

Rik · Feb 02, 2007, 14:02:06

Quote from: pow on Feb 02, 2007, 12:39:21
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 · Feb 02, 2007, 14:30:36

Quote from: rikbean on Feb 02, 2007, 14:02:06
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 · Feb 02, 2007, 14:44:55

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 · Feb 02, 2007, 15:41:18

Quote from: rikbean on Feb 02, 2007, 14:44:55

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 · Feb 02, 2007, 15:52:35

Quote from: pow on Feb 02, 2007, 15:41:18
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

QuoteThe 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

QuoteI 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 · Feb 02, 2007, 16:08:28

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

I will keep you posted..

Rik · Feb 02, 2007, 16:38:31

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

pow · Feb 05, 2007, 10:10:20

Quote from: Nerval on Feb 02, 2007, 09:59:06
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 · Feb 05, 2007, 10:17:23

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 · Feb 05, 2007, 10:24:15

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.

Rik · Feb 05, 2007, 10:38:40

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?

Ray · Feb 05, 2007, 11:11:51

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

Nerval · Feb 05, 2007, 11:17:05

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

pow · Feb 05, 2007, 11:17:51

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 · Feb 05, 2007, 11:22:32

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 · 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.

pow · Feb 05, 2007, 12:29:08

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

Rik · Feb 05, 2007, 12:46:21

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

Lance · 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!

pow · Feb 05, 2007, 14:00:48

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 · Feb 05, 2007, 14:09:26

I come under the heading of customer dis-service.

Rik · Feb 05, 2007, 14:10:15

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!

pow · Feb 05, 2007, 14:15:43

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 · Feb 05, 2007, 14:44:56

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

pow · Feb 05, 2007, 15:18:46

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 · 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.

pow · Feb 05, 2007, 15:52:43

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 · Feb 05, 2007, 16:00:59

Have you done everything else I suggested?

pow · Feb 05, 2007, 16:31:52

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 · Feb 05, 2007, 16:39:50

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.

Nerval · Feb 05, 2007, 16:57:43

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 · Feb 05, 2007, 17:59:19

Many paths leads to Nirvana, Nerv.

Nerval · Feb 05, 2007, 18:01:30

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

Rik · Feb 05, 2007, 18:12:39

That would be a chameleon load.

pow · Feb 09, 2007, 11:01:58

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

Rik · Feb 09, 2007, 11:05:31

If neither the url or the IP address work, it isn't DNS (I'm reasonably sure, anyway). Can you try to do a tracert to one of the addresses and paste the results back here. You may also want to give a few of the addresses, which we can try for you and see what happens.

pow · Feb 09, 2007, 11:54:14

This is the same tracert result i got last nite on idNet

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.

Sites visited were:
http://www.goldsmiths.ac.uk/, www.argos.co.uk, www.scan.co.uk, www.idnetters.co.uk, http://www.thinkbroadband.com to name a few.

Also I can't even get my email on Outlook without erroring out

Rik · Feb 09, 2007, 12:02:10

All those sites are working fine here, so it's not an issue with IDNet. TBH, I'm at a loss. If some sites work for you, your DNS is OK.

The only thing left that I can think of is that your MTU/RWIN settings are causing the problem. What do you have them at?

pow · Feb 09, 2007, 12:12:21

I have tried my MTU at 1500, 1458, 1438 and even 1400 and that didn't make much difference. I must say I'm probably only able to access just a fraction of sites and they are quite slow loading.

I'm really not sure what to do now, but I might have to make a very radical decision as I've been without connection for over 2 weeks now

Rik · Feb 09, 2007, 12:16:54

Have you talked to CS recently, Pow? I can't think of anything else to try, sorry.

pow · Feb 09, 2007, 12:20:12

Quote from: rikbean on Feb 09, 2007, 12:16:54
Have you talked to CS recently, Pow? I can't think of anything else to try, sorry.

Well I might give them a quick call. Thanks though you have been a great help

Rik · Feb 09, 2007, 12:26:07

I'm just sorry I couldn't come up with a solution. Let me know if you get to the bottom of it, it'll be one for the database.

pow · Apr 06, 2007, 21:39:09

Hi everyone,

Good to see you are all still around helping distressed folks like me. Yeah recently went away hoping this problem will do too but guess what it's still here. A brief recap of my situation is that most web pages say 90% are not loading hence timing out, and IDNet has confirmed that all is fine with my line. They say the next stage would be to call out a BT engineer, and I have taken it upon myself to check the call out charge which is £169.20

I have done that following so far: tested from master socket, new computer & SpeedTouch 546 router, and re-installed OS. I now have some doubts about my Gateway connectivity so I have pasted this below if it makes more sense to anyone.

Test Results

DSL.......Pass

ATM.....Pass

PPP......Pass

IP......Pass

Internet....Fail
Connectivity to Gateway [Gateway removed, IP revealed - Rik]

Please, please can anyone help

Many thanks

Rik · Apr 07, 2007, 11:00:48

Is there any chance you could borrow another router, or even a USB modem, to eliminate any fault there? Given it appears to be picking up your IP, I'm a bit puzzled by the fail message. It would be nice to eliminate a possible hardware fault before you get landed with a bill from BT.

pow · Apr 11, 2007, 15:06:42

Hi

I have tested my connection with a couple of modem (USB and router) but still have the same problem. Strangely I am now only able to access fewer sites than before and couple i wasn't able to access. I'm really getting very frustrated

Help !

Lance · Apr 11, 2007, 15:11:27

I would suggest calling support again and see what they say. I'm not sure if anyone here is able to help you. Sorry!

Rik · Apr 11, 2007, 15:31:40

I have to go with Lance. We've covered all the self-help angles that I can think of, you really need to talk to support who can 'see' your connection and work out what is happening. Sorry.