jrtking73 wrote:
Hello.
I did the steps outlined in your post Lapastenague, thanks very much. Interesting things occurred. First thing, I am not sure if I have a crossover cable or switch between cable modem and TC. What I do have as a connection is a ethernet cable connecting the two, is that what you mean?
Crossover cables were required in the olden days but have long since dropped out for using standard ethernet cables with the electronics in the ethernet ports working out which is the send and which is the receive.. but Apple seem to have made some issues on the latest AC model that causes issues which a crossover can occasionally help. Especially if you are running a cable modem the TC has issues with.
I gather from your post you are using the new AC version TC.
I downloaded an app which tests internet speed and it says I am getting 35 MBps download and about 10 MBps upload speed. It feels intuitively to me that there is a problem with the TC talking to the cable modem but that is just a feeling my (inexpert) brain has.
I also changed the IP address this AM before I came to work and so far I don't think that has changed anything. It was a slightly different process than you outlined (not to pick at you, just letting you know) probably changed with firmware update?
OK I think that covers what I have done so far, thanks for your help, I actually kind of like working on this its interesting.
Look forward to next step thanks!!!
Jeremy
You download and upload speed are fine so it does sound like there is some other issue happening.
Can you please post a screenshot or two of the current setup of the TC.
Exactly like the ones I posted.. that is the real advantage of this forum as it gives us the ability to post pics without using a service outside. I do need to see what is going on.
Hmm just had an interesting conversation with an IT gentleman at my work. Before he had to run away he suggested it could be an issue with the browser software and a matter of adding some DNS or server lines to the web browser preferences.
You do need to make sure the DNS is resolving correctly but I doubt that is the issue for such slow page loading. I think he is referring to ISP that use proxy address but again I doubt that is your problem.
Testing most of these things is fairly easy.
Open terminal and do a traceroute to a website you are having issues with.
The command is simple
traceroute www.apple.com say
traceroute www.apple.com
traceroute to e3191.dscc.akamaiedge.net (184.31.205.15), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 0.533 ms 0.348 ms 0.264 ms
2 192.168.2.1 (192.168.2.1) 0.569 ms 0.574 ms 0.399 ms
3 adsl1.mel02.eftel.com (203.123.69.176) 18.662 ms 17.687 ms 17.586 ms
4 te0-0-0-306.core0.mel02.eftel.com (203.123.72.65) 18.743 ms 18.712 ms 17.891 ms
5 203.123.69.134 (203.123.69.134) 19.275 ms 19.146 ms 19.230 ms
6 bundle-ether11.win24.melbourne.telstra.net (165.228.21.137) 20.170 ms 26.255 ms 23.792 ms
7 bundle-ether2.***76.melbourne.telstra.net (203.50.11.60) 20.465 ms 26.523 ms 24.384 ms
8 akamai2.lnk.telstra.net (120.151.255.150) 18.941 ms 18.943 ms 19.091 ms
9 * * *
10 * * *
It may not complete and you can stop it with control + c keys.
But it should resolve the address and begin testing each hop quickly. You are looking for slow down in the first hop or at some later point if this is your ISP issue.
I would btw still like you to move the TC to 192.168.x.x address range if you did not manage that.
You can see my double NAT here.. which is just a test setup.. but is a problem.. you can see I have to different IP ranges.