Problem accessing site
Posted: Tue Feb 14, 2006 9:22 amI'm having trouble accessing this site through the .net (timing out) but I can get in through the .com anyone else having this problem?
DSLRUsers.com
A discussion forum - and more - for users of Digital Single Lens Reflex cameras.
https://d70users.net/
Problem accessing site
Page 1 of 2
Posted: Tue Feb 14, 2006 9:22 amPosted: Tue Feb 14, 2006 9:25 amYep, I did this morning. Exactly the same fault.
Posted: Tue Feb 14, 2006 9:32 amI've had to use .com as well
Posted: Tue Feb 14, 2006 9:38 amIt's a DNS problem at DH.
They're aware of it, and are working on a resolution.
I also cannot access the site via FTP, and because it's the .net site that's affected, Glen's unable to post his PotW.
As soon as it's fixed, it'll be fixed.
But ye, use the .com site for the time being; it's mostly a mirror, and all should be fine.
They're aware of it, and are working on a resolution.
I also cannot access the site via FTP, and because it's the .net site that's affected, Glen's unable to post his PotW.
As soon as it's fixed, it'll be fixed.
But ye, use the .com site for the time being; it's mostly a mirror, and all should be fine.
Posted: Tue Feb 14, 2006 9:50 amdid they give any time frame for DNS to be RESOLVED??
Steve
Steve
Posted: Tue Feb 14, 2006 9:57 amPosted: Tue Feb 14, 2006 10:01 amactually garry that was my poor attempt at humour!!
Pun on the nature of the fault.
Which is why I am a computer dude and not a comedian.
Steve
Pun on the nature of the fault.
Which is why I am a computer dude and not a comedian.
Steve
Posted: Tue Feb 14, 2006 10:05 amSteve,
I know.
On both counts.
I know.
On both counts.
Posted: Tue Feb 14, 2006 10:10 amPosted: Tue Feb 14, 2006 3:38 pmSteve
I got the joke once you'd said it was a joke. (DNS resolved
)
I got the joke once you'd said it was a joke. (DNS resolved
)Posted: Tue Feb 14, 2006 4:52 pmSadly, the resolution of this remains unresolved, and I've sent off a follow-up emaiil, all the while watching my FTP client spinning its wheels whilst failing to connect.
Posted: Tue Feb 14, 2006 5:49 pmThis appears to actually be a routing issue at Optus.
Running a trace from here, the two sites try to take very different paths once they hit Optus. .com completes, .net times out.
Running a similar trace from an overseas site confirms that the trace to the .net site works perfectly.
Will a couple of out optus users please call their so-called technical support people and bitch, whine and moan very loudly?
Don't accept a bullshit answer, but simply point out the facts. local traces to .net fail. remote traces to .net succeed, therefore the target site is fine.
Local traces to .com succeed, yet the .net site should be sharing the same, or very similar, routing. It doesn't.
Running a trace from here, the two sites try to take very different paths once they hit Optus. .com completes, .net times out.
Running a similar trace from an overseas site confirms that the trace to the .net site works perfectly.
Will a couple of out optus users please call their so-called technical support people and bitch, whine and moan very loudly?
Don't accept a bullshit answer, but simply point out the facts. local traces to .net fail. remote traces to .net succeed, therefore the target site is fine.
Local traces to .com succeed, yet the .net site should be sharing the same, or very similar, routing. It doesn't.
Posted: Tue Feb 14, 2006 6:13 pmWhat a pain - it took me all day to figure out i needed to try .com site.
Hope it is fixed soon - thanks for all your hard work Gary
Hope it is fixed soon - thanks for all your hard work Gary
Posted: Tue Feb 14, 2006 6:33 pmI hate using com. It stands for common. 
Posted: Tue Feb 14, 2006 6:47 pmI'd been trying for hours to log on and no go - couldn't work it out.
I ended up contacting Rel (Blacknstormy) to see if she was having similar problems and she told me to use old address (i.e. .com), hence the post.
Thanks Rel
Cheers
Michael
I ended up contacting Rel (Blacknstormy) to see if she was having similar problems and she told me to use old address (i.e. .com), hence the post.
Thanks Rel
Cheers
Michael
Posted: Tue Feb 14, 2006 7:30 pmI just tried two traceroutes and it seems to be misrouted in verio.net in the USA, ie right before it plugs into dreamhost.
traceroute dslrusers.com seems to work fine:
traceroute dslrusers.net dies in verio.net:
Why do you think it's Optus?
traceroute dslrusers.com seems to work fine:
- Code: Select all
...
4 gi0-0.bdr1.syd7.agile.on.net (150.101.199.231) 172.941 ms 171.861 ms 172.318 ms
5 pos2-0.bdr1.sjc2.agile.on.net (203.16.213.41) 170.945 ms 172.966 ms 174.365 ms
6 ge-3-7.r02.snjsca04.us.bb.verio.net (129.250.11.97) 171.942 ms 171.143 ms 170.239 ms
7 xe-1-2-0.r20.snjsca04.us.bb.verio.net (129.250.2.30) 173.461 ms 170.754 ms 173.856 ms
8 p64-0-0-0.r20.plalca01.us.bb.verio.net (129.250.2.70) 175.209 ms 174.713 ms 174.588 ms
9 ge1-gx.dreamhost.com (67.17.162.162) 184.899 ms 179.638 ms 198.191 ms
10 basic-blow.laurel.dreamhost.com (64.111.120.59) 182.296 ms 180.295 ms 179.750 ms
traceroute dslrusers.net dies in verio.net:
- Code: Select all
...
4 gi0-0.bdr1.syd7.agile.on.net (150.101.199.231) 171.972 ms 170.741 ms 174.115 ms
5 pos2-0.bdr1.sjc2.agile.on.net (203.16.213.41) 170.263 ms 172.540 ms 173.091 ms
6 ge-3-7.r02.snjsca04.us.bb.verio.net (129.250.11.97) 170.945 ms 171.813 ms 171.944 ms
7 xe-1-2-0.r20.snjsca04.us.bb.verio.net (129.250.2.30) 174.564 ms 174.121 ms 171.533 ms
8 p64-0-0-0.r20.plalca01.us.bb.verio.net (129.250.2.70) 173.885 ms 173.753 ms 179.437 ms
9 * * *
10 * * *
11 * * *
12 * * *
Why do you think it's Optus?
Posted: Tue Feb 14, 2006 9:02 pmmy trace route to .net times out at a US server LAX9.Alter.net
my trace to .com also goes via lax9.alter.net then into lax2.gblix2.net and on to dreamhost.
not sure how optus comes into it either.
looks more like some issues in the us to me.
Steve
my trace to .com also goes via lax9.alter.net then into lax2.gblix2.net and on to dreamhost.
not sure how optus comes into it either.
looks more like some issues in the us to me.
Steve
Posted: Tue Feb 14, 2006 9:04 pmFozzie cant seem to log into site either at the moment.
Posted: Tue Feb 14, 2006 9:10 pmdepending on how long this lasts, we may be able to get a few members to generate trace routes from different parts of the country, elsewhere in the world and a common failure may show up, although the nature of the net generally means more than one path to different destinations.
Steve
Steve
Posted: Tue Feb 14, 2006 9:23 pmThank you BBJ, I'm back
BBJ wrote:Fozzie cant seem to log into site either at the moment.
Posted: Tue Feb 14, 2006 9:25 pmNo Probs mate, read Gary's post so then thought we try the .com bit, well back up and rinning so that's a +.
Posted: Wed Feb 15, 2006 12:10 amGary, more than happy to complain, but Thaddeus trace is at odds with initial thoughts. Is there a trace I can do from my PC which I could then forward to Optus (if they are the culprit)?
Posted: Wed Feb 15, 2006 10:28 amWhy do you think it's Optus?
It dies in my traces at a Singtel - which is Optus routing - link.
In this morning's test, I can accessthe site through a PT connection, but not through Exetel, and from what I can tell, none of out Optus users can either.
Exetel uses Optus, PT don't.
Spot the common element here.
Posted: Wed Feb 15, 2006 10:30 amGlen wrote:Gary, more than happy to complain, but Thaddeus trace is at odds with initial thoughts. Is there a trace I can do from my PC which I could then forward to Optus (if they are the culprit)?
Glen,
just load up a command prompt, and enter
tracert http://www.dslrusers.net
and/or
tracert http://www.dslrusers.com
Grab a screen dump of the output and post it to this thread. That'll give us more of a clue.
Posted: Wed Feb 15, 2006 10:42 amMicrosoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>tracert http://www.dslrusers.net
Tracing route to http://www.dslrusers.net [64.111.112.203]
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.
Trace complete.
C:\Documents and Settings\Owner>
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>tracert http://www.dslrusers.net
Tracing route to http://www.dslrusers.net [64.111.112.203]
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.
Trace complete.
C:\Documents and Settings\Owner>
Posted: Wed Feb 15, 2006 10:49 amMicrosoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>tracert http://www.dslrusers.com
Tracing route to http://www.dslrusers.com [64.111.120.59]
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 254 ms * * basic-blow.laurel.dreamhost.com [64.111.120.59]
12 198 ms 184 ms 196 ms basic-blow.laurel.dreamhost.com [64.111.120.59]
Trace complete.
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>tracert http://www.dslrusers.com
Tracing route to http://www.dslrusers.com [64.111.120.59]
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 254 ms * * basic-blow.laurel.dreamhost.com [64.111.120.59]
12 198 ms 184 ms 196 ms basic-blow.laurel.dreamhost.com [64.111.120.59]
Trace complete.
Posted: Wed Feb 15, 2006 10:50 amwe aint getting a whole heap of useful info from that trace glen. !!
Steve
Steve
Posted: Wed Feb 15, 2006 10:52 amAnything more I can do (remembering I am a not a computer programmer)
Posted: Wed Feb 15, 2006 10:57 amWhen I do a tracrt on the .net address it isn't even resolving. the .com works fine
Posted: Wed Feb 15, 2006 11:06 amSo this probably isn't the time to mention that I can't view the thumbnails for PoTW on the frontpage (I'm banned from the .net site).
Posted: Wed Feb 15, 2006 11:07 amjust to be safe,
it is sometimes worth clearing out dns cache on your computer, just in case.
the command is :
ipconfig /flushdns cache
at the command line
the system will respond with windows ip configuration
successfully flushed the DNS Resolver Cache.
I am going to terminal service into some sites I know with different ISP
and see which way that goes.
Might make an optus one first go.
Stay tuned.
Steve
it is sometimes worth clearing out dns cache on your computer, just in case.
the command is :
ipconfig /flushdns cache
at the command line
the system will respond with windows ip configuration
successfully flushed the DNS Resolver Cache.
I am going to terminal service into some sites I know with different ISP
and see which way that goes.
Might make an optus one first go.
Stay tuned.
Steve
Posted: Wed Feb 15, 2006 11:12 amGlen,
That is exactly the information that you need to supply to Optus. As seless as it is.
For some reason they're blocking some aspects of the trace, but both traces should yield almost identical results. One resolves, the other goes into never-never land.
Give them a hoy, and try to speak with somebody beyond the drone that you'll get as the first line of support. The problem is in their upstream routing.
Chi,
who's your upstream provider? If you could see the POTW images last week you should still be able to see them unless you're affected by this issue.
What happens when you try a trace to the two sites, as Glen has?
That is exactly the information that you need to supply to Optus. As seless as it is.
For some reason they're blocking some aspects of the trace, but both traces should yield almost identical results. One resolves, the other goes into never-never land.
Give them a hoy, and try to speak with somebody beyond the drone that you'll get as the first line of support. The problem is in their upstream routing.
Chi,
who's your upstream provider? If you could see the POTW images last week you should still be able to see them unless you're affected by this issue.
What happens when you try a trace to the two sites, as Glen has?
Posted: Wed Feb 15, 2006 11:14 amavkomp wrote:I am going to terminal service into some sites I know with different ISP and see which way that goes.
That's how I figured out that PT works, but Exetel doesn't.
flushdns doesn't help in this case, it's the upstream resolvers that are corrupt.
Posted: Wed Feb 15, 2006 11:15 amI just terminal serviced into a site. they are using optus for adsl
route traced for .com to dreamhost via singapore, arizona, la and to dreamhost.
.net initially unresolvable.
I flashed the server dns cache, and now resolvable but gets lost at singapore somewhere.
the upsteam DNS server for this site is 61.88.88.88 an optus name server
Stay tuned for telstras version
Steve
route traced for .com to dreamhost via singapore, arizona, la and to dreamhost.
.net initially unresolvable.
I flashed the server dns cache, and now resolvable but gets lost at singapore somewhere.
the upsteam DNS server for this site is 61.88.88.88 an optus name server
Stay tuned for telstras version
Steve
Posted: Wed Feb 15, 2006 11:19 amwell now I am sitting in a terminal session of a site with bigpond adsl
not only does tracert work for both .com and .net but the .net website is working perfectly here.
Steve
not only does tracert work for both .com and .net but the .net website is working perfectly here.
Steve
Posted: Wed Feb 15, 2006 11:37 amSteve,
Exactly. The common denominator through almost everything that I've seen thus far is Optus.
The bottom line is that there's a problem, somewhere, upstream from the hosts that some of us use.
We need to have a few Optus users complain to Optus to have them clear and refresh their resolvers, and I believe that that will solve a lot of the problems.
Exactly. The common denominator through almost everything that I've seen thus far is Optus.
The bottom line is that there's a problem, somewhere, upstream from the hosts that some of us use.
We need to have a few Optus users complain to Optus to have them clear and refresh their resolvers, and I believe that that will solve a lot of the problems.
Posted: Wed Feb 15, 2006 11:40 amOK. This is interesting. Did an ipconfig /flushdns (I'm at work). tracert on .net didn't work before that. After the flush here is what I got for .net (I thought we used Optus, but seems we are now using Telstra since it went through a Telstra gateway):
4 7 ms 6 ms 7 ms g1-27.switch1.syd2.pacific.net.au [210.23.140.245]
5 8 ms 6 ms 7 ms GigabitEthernet4-5.ken17.Sydney.telstra.net [139.130.91.113]
6 8 ms 7 ms 7 ms 10GigabitEthernet15-0.ken-core4.Sydney.telstra.net [203.50.20.1]
7 6 ms 7 ms 7 ms 10GigabitEthernet3-0.pad-core4.Sydney.telstra.net [203.50.6.86]
8 7 ms 7 ms 6 ms 10GigabitEthernet2-2.syd-core02.Sydney.net.reach.com [203.50.13.42]
9 8 ms 6 ms 7 ms i-4-0.syd-core01.net.reach.com [202.84.221.89]
10 155 ms 154 ms 155 ms i-3-0.wil-core01.net.reach.com [202.84.140.29]
11 155 ms 155 ms 153 ms i-3-4.wil03.net.reach.com [202.84.251.162]
12 168 ms 168 ms 169 ms ge-6-20.car3.LosAngeles1.Level3.net [4.68.111.133]
13 166 ms 167 ms 168 ms ge-4-2.ipcolo2.LosAngeles1.Level3.net [4.68.102.139]
14 166 ms 167 ms 167 ms 4.78.195.170
15 173 ms 172 ms 172 ms basic-emu.laurel.dreamhost.com [64.111.112.203]
I get an identical trace on the .com address.
I'm Optus @ home so I'll try from there later.
4 7 ms 6 ms 7 ms g1-27.switch1.syd2.pacific.net.au [210.23.140.245]
5 8 ms 6 ms 7 ms GigabitEthernet4-5.ken17.Sydney.telstra.net [139.130.91.113]
6 8 ms 7 ms 7 ms 10GigabitEthernet15-0.ken-core4.Sydney.telstra.net [203.50.20.1]
7 6 ms 7 ms 7 ms 10GigabitEthernet3-0.pad-core4.Sydney.telstra.net [203.50.6.86]
8 7 ms 7 ms 6 ms 10GigabitEthernet2-2.syd-core02.Sydney.net.reach.com [203.50.13.42]
9 8 ms 6 ms 7 ms i-4-0.syd-core01.net.reach.com [202.84.221.89]
10 155 ms 154 ms 155 ms i-3-0.wil-core01.net.reach.com [202.84.140.29]
11 155 ms 155 ms 153 ms i-3-4.wil03.net.reach.com [202.84.251.162]
12 168 ms 168 ms 169 ms ge-6-20.car3.LosAngeles1.Level3.net [4.68.111.133]
13 166 ms 167 ms 168 ms ge-4-2.ipcolo2.LosAngeles1.Level3.net [4.68.102.139]
14 166 ms 167 ms 167 ms 4.78.195.170
15 173 ms 172 ms 172 ms basic-emu.laurel.dreamhost.com [64.111.112.203]
I get an identical trace on the .com address.
I'm Optus @ home so I'll try from there later.
Posted: Wed Feb 15, 2006 11:49 ampeter, thats similar to what happened for me when I tested via some clients sites.
so accordingly I guess the .net site works perfectly for you at work??
flushing the cache and having it working can sometimes suggest that upstream stuff is starting to fix itself up.
The biggest problem may turn out to be convincing the large company that they have an issue.
I have a site once who changed mail hosting between companies and could not get mail from one client.
We traced it to being invalid DNS records kept by one of the telcos. Finally I send some guy in supprt the ip address he was supposed to get when pinging the mail server and when it came up with the old one, they finally believed me and fixed it in minutes.
Bastards
so accordingly I guess the .net site works perfectly for you at work??
flushing the cache and having it working can sometimes suggest that upstream stuff is starting to fix itself up.
The biggest problem may turn out to be convincing the large company that they have an issue.
I have a site once who changed mail hosting between companies and could not get mail from one client.
We traced it to being invalid DNS records kept by one of the telcos. Finally I send some guy in supprt the ip address he was supposed to get when pinging the mail server and when it came up with the old one, they finally believed me and fixed it in minutes.
Bastards
Posted: Wed Feb 15, 2006 11:52 amTracert for .com and .net -
Tracing route to http://www.dslrusers.com [64.111.120.59]
over a maximum of 30 hops:
1 854 ms 129 ms 139 ms r220-101-40-1.gwy.unwired.net.au
2 133 ms 139 ms 139 ms v1679-cr1.equ.syd.bbn.unwired.net.au
3 170 ms 149 ms 139 ms ge-2-1.br1.equ.syd.bbn.unwired.net.au
4 130 ms 149 ms 149 ms fastethernet2-0-7.cor8.syd.connect.com.au
5 161 ms 149 ms 149 ms ge-0-1-0.bdr5.syd.connect.com.au
6 143 ms 149 ms 149 ms p5-0.sybr3.global-gateway.net.nz
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * 292 ms 269 ms sl-st20-la-6-3.sprintlink.net
11 306 ms 309 ms 339 ms so1-2-0-2488M.ar1.LAX2.gblx.net
12 275 ms 289 ms 279 ms so0-3-0-622M.ar1.LAX3.gblx.net
13 275 ms 279 ms 279 ms GE1-GX.dreamhost.com
14 319 ms 309 ms 299 ms basic-blow.laurel.dreamhost.com
Tracing route to http://www.dslrusers.net [64.111.112.203]
over a maximum of 30 hops:
1 127 ms 129 ms 139 ms r220-101-40-1.gwy.unwired.net.au
2 455 ms 149 ms 139 ms v1679-cr1.equ.syd.bbn.unwired.net.au
3 1715 ms 129 ms 139 ms ge-2-1.br1.equ.syd.bbn.unwired.net.au
4 * * 203 ms fastethernet2-0-17.cor8.syd.connect.com.au
5 127 ms 139 ms 139 ms ge-0-1-0.bdr5.syd.connect.com.au
6 116 ms 139 ms 139 ms p5-0.sybr3.global-gateway.net.nz
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 393 ms 289 ms 319 ms sl-st20-la-6-2.sprintlink.net
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
....Time out ad infinium until 30 hops.
Tracing route to http://www.dslrusers.com [64.111.120.59]
over a maximum of 30 hops:
1 854 ms 129 ms 139 ms r220-101-40-1.gwy.unwired.net.au
2 133 ms 139 ms 139 ms v1679-cr1.equ.syd.bbn.unwired.net.au
3 170 ms 149 ms 139 ms ge-2-1.br1.equ.syd.bbn.unwired.net.au
4 130 ms 149 ms 149 ms fastethernet2-0-7.cor8.syd.connect.com.au
5 161 ms 149 ms 149 ms ge-0-1-0.bdr5.syd.connect.com.au
6 143 ms 149 ms 149 ms p5-0.sybr3.global-gateway.net.nz
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * 292 ms 269 ms sl-st20-la-6-3.sprintlink.net
11 306 ms 309 ms 339 ms so1-2-0-2488M.ar1.LAX2.gblx.net
12 275 ms 289 ms 279 ms so0-3-0-622M.ar1.LAX3.gblx.net
13 275 ms 279 ms 279 ms GE1-GX.dreamhost.com
14 319 ms 309 ms 299 ms basic-blow.laurel.dreamhost.com
Tracing route to http://www.dslrusers.net [64.111.112.203]
over a maximum of 30 hops:
1 127 ms 129 ms 139 ms r220-101-40-1.gwy.unwired.net.au
2 455 ms 149 ms 139 ms v1679-cr1.equ.syd.bbn.unwired.net.au
3 1715 ms 129 ms 139 ms ge-2-1.br1.equ.syd.bbn.unwired.net.au
4 * * 203 ms fastethernet2-0-17.cor8.syd.connect.com.au
5 127 ms 139 ms 139 ms ge-0-1-0.bdr5.syd.connect.com.au
6 116 ms 139 ms 139 ms p5-0.sybr3.global-gateway.net.nz
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 393 ms 289 ms 319 ms sl-st20-la-6-2.sprintlink.net
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
....Time out ad infinium until 30 hops.
Posted: Wed Feb 15, 2006 12:00 pmavkomp wrote:The biggest problem may turn out to be convincing the large company that they have an issue.
Which is why everybody who is experiencing this issue needs to log a fault at their ISP, citing the trace results as evidence.
As multiple faults flow upstream, something will, eventually, hopefully get done and the problems will be resolved.
Chi, call Unwired and complain that there are routing issues.
Posted: Wed Feb 15, 2006 12:04 pmI have been reading this thread with much interest (although I have no idea as to what you are doing!) and I have to say that I have had absolutely no problems at all
Posted: Wed Feb 15, 2006 12:08 pmout of curiosity, chris : who is your isp??
Posted: Wed Feb 15, 2006 12:16 pmavkomp wrote:peter, thats similar to what happened for me when I tested via some clients sites.
so accordingly I guess the .net site works perfectly for you at work??
flushing the cache and having it working can sometimes suggest that upstream stuff is starting to fix itself up.<snip>
Steve
The .net site did not originally work at work (as the unresolvable tracrt would suggest), but once I'd flushed the cache it is now working from work. Strong evidence of what Gary suggests - there is a DNS caching problem and it's upstream, but NOT if it's Telstra
As an aside, Gary does that mean you actually like Telstra in this case
Posted: Wed Feb 15, 2006 12:19 pmPeter,
Don't make me throw up.
Steve,
I think Chris is accessing the site through the .com.
Don't make me throw up.
Steve,
I think Chris is accessing the site through the .com.
Posted: Wed Feb 15, 2006 3:15 pmThat’s funny, I just had a look and I am accessing through .net and I am using Helstra broadband - mind you, this geeky stuff is really beyond my feeble brain
Posted: Wed Feb 15, 2006 3:59 pmaccording to the testing I did this morning, telstra would appear to be working fine.
Steve
Steve
Posted: Wed Feb 15, 2006 4:34 pmI got this when I put Steve's command in, think I am out of my depth and cant be of any help with this process. Will just ring optus and tell them it is rooted 
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>ipconfig /flushdns cache
Error: unrecongnized or incomplete command line.
USAGE:
ipconfig [/? | /all | /renew [adapter] | /release [adapter] |
/flushdns | /displaydns | /registerdns |
/showclassid adapter |
/setclassid adapter [classid] ]
where
adapter Connection name
(wildcard characters * and ? allowed, see examples)
Options:
/? Display this help message
/all Display full configuration information.
/release Release the IP address for the specified adapter.
/renew Renew the IP address for the specified adapter.
/flushdns Purges the DNS Resolver cache.
/registerdns Refreshes all DHCP leases and re-registers DNS names
/displaydns Display the contents of the DNS Resolver Cache.
/showclassid Displays all the dhcp class IDs allowed for adapter.
/setclassid Modifies the dhcp class id.
The default is to display only the IP address, subnet mask and
default gateway for each adapter bound to TCP/IP.
For Release and Renew, if no adapter name is specified, then the IP address
leases for all adapters bound to TCP/IP will be released or renewed.
For Setclassid, if no ClassId is specified, then the ClassId is removed.
Examples:
> ipconfig ... Show information.
> ipconfig /all ... Show detailed information
> ipconfig /renew ... renew all adapters
> ipconfig /renew EL* ... renew any connection that has its
name starting with EL
> ipconfig /release *Con* ... release all matching connections,
eg. "Local Area Connection 1" or
"Local Area Connection 2"
C:\Documents and Settings\Owner>
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>ipconfig /flushdns cache
Error: unrecongnized or incomplete command line.
USAGE:
ipconfig [/? | /all | /renew [adapter] | /release [adapter] |
/flushdns | /displaydns | /registerdns |
/showclassid adapter |
/setclassid adapter [classid] ]
where
adapter Connection name
(wildcard characters * and ? allowed, see examples)
Options:
/? Display this help message
/all Display full configuration information.
/release Release the IP address for the specified adapter.
/renew Renew the IP address for the specified adapter.
/flushdns Purges the DNS Resolver cache.
/registerdns Refreshes all DHCP leases and re-registers DNS names
/displaydns Display the contents of the DNS Resolver Cache.
/showclassid Displays all the dhcp class IDs allowed for adapter.
/setclassid Modifies the dhcp class id.
The default is to display only the IP address, subnet mask and
default gateway for each adapter bound to TCP/IP.
For Release and Renew, if no adapter name is specified, then the IP address
leases for all adapters bound to TCP/IP will be released or renewed.
For Setclassid, if no ClassId is specified, then the ClassId is removed.
Examples:
> ipconfig ... Show information.
> ipconfig /all ... Show detailed information
> ipconfig /renew ... renew all adapters
> ipconfig /renew EL* ... renew any connection that has its
name starting with EL
> ipconfig /release *Con* ... release all matching connections,
eg. "Local Area Connection 1" or
"Local Area Connection 2"
C:\Documents and Settings\Owner>
Posted: Wed Feb 15, 2006 4:35 pmGlen wrote:I got this when I put Steve's command in, think I am out of my depth and cant be of any help with this process. Will just ring optus and tell them it is rooted
Nice work Glen
Posted: Wed Feb 15, 2006 4:36 pmglenn:
the command is
ipconfig /flushdns (enter)
nothing else. the extra word is what did you over.
Steve
the command is
ipconfig /flushdns (enter)
nothing else. the extra word is what did you over.
Steve
Posted: Wed Feb 15, 2006 4:44 pmThanks Steve, was actually doing that now whilst waiting on hold to tell optus it's rooted. Just got a big fat zero for net, the same blank thing I had before. Will try com.