Thread: Squirrels on strike???

Steven looking into it.

However for anyone who is still having a problem please try doing traceroute for the forums from the command prompt using the below command:
tracert woodworkforums.com

This will show if there are any dropped routes along the path to the destination server.

Click here for info on using traceroute if you're not sure how it works.

If you find any dropouts please copy and past the full result from the traceroute into this thread.

Hope this helps.

Cheers - Neil

Sure - I can't even ping the server. Traceroute from an optus cable connection (122.108.189.x) which can't connect:

ceres danny$ traceroute www.woodworkforums.com
traceroute to www.woodworkforums.com (209.95.48.51), 64 hops max, 52 byte packets
1 192.168.198.254 (192.168.198.254) 0.895 ms 0.619 ms 0.599 ms
2 10.66.0.1 (10.66.0.1) 11.280 ms 10.846 ms 19.984 ms
3 rdl1-ge1-2.gw.optusnet.com.au (198.142.160.201) 10.820 ms 10.632 ms 10.967 ms
4 * * *
5 * * *
6 198.142.250.221 (198.142.250.221) 23.738 ms
198.142.250.229 (198.142.250.229) 22.087 ms *
7 * 198.142.139.116 (198.142.139.116) 21.192 ms 32.246 ms
8 198.142.139.132 (198.142.139.132) 25.524 ms 36.858 ms 24.782 ms
9 203.208.192.205 (203.208.192.205) 178.758 ms
198.142.139.116 (198.142.139.116) 36.220 ms 27.035 ms
10 203.208.171.118 (203.208.171.118) 169.393 ms
203.208.158.122 (203.208.158.122) 199.109 ms
198.142.139.132 (198.142.139.132) 37.522 ms
11 203.208.174.189 (203.208.174.189) 182.592 ms
203.208.192.205 (203.208.192.205) 182.485 ms 181.483 ms
12 ae0.cr2.lax112.us.zip.zayo.com (64.125.32.78) 178.079 ms 177.298 ms
203.208.172.146 (203.208.172.146) 181.754 ms
13 203.208.151.101 (203.208.151.101) 179.402 ms
ae12.mpr1.slc1.us.zip.zayo.com (64.125.21.222) 193.179 ms 203.188 ms
14 208.184.34.150.ipyx-068416-003-zyo.above.net (208.184.34.150) 208.697 ms 195.821 ms 201.707 ms
15 206.130.126.30.west-datacenter.net (206.130.126.30) 191.951 ms
ae12.mpr1.slc1.us.zip.zayo.com (64.125.21.222) 200.840 ms 202.458 ms
16 * * *
17 * 206.130.126.26.west-datacenter.net (206.130.126.26) 196.258 ms
206.130.126.30.west-datacenter.net (206.130.126.30) 211.842 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 *^C

Originally Posted by crowie

Sorry Neil & Steven.
I have no access to WWF at all at home on either Internet Explorer, Google Chrome, Safari neither my usual Firefox since 3:30pm yesterday... Running Windows 7.. I was still out this morning.
It works from daughters home in Penrith on Safari so who knows!
Cheers crowie

I got home from my daughters this afternoon and looked again for the WWF; WOW; I'm on the air again THANK YOU!!

Me too - I am connected again from the connection that wasn't working before - thanks team!

Originally Posted by ubeaut

If you are using a bookmarked login, stop. Delete the login and type in or copy this url http://www.woodworkforums.com and that should fix the problem. We moved to a new section of the server and now have a different IP address. Also the DNS needed to be updated from your service provider(s) which can take from a few minutes to a few days depending on how on the ball they are with their updates.

Hope this is of some help.

Cheers - Neil

Thanks Neil I have never come across 145sec wait time after just replying to 3 pm's 60sec maybe never in 10 yrs 145.

Normally use a notification to bring the forum up these days not in my tabs set up at all. Will however try it.

Originally Posted by Acco

Talking as an ex Admin, we definitely don't want this relaxed, if you're sending that many messages, I suggest you either get email addresses or use an instant message like Skype etc for those that you're in regular contact with

As just replied to Neil never in 10 yrs have I had 145sec show before using PM's after just sorry I said 3 it was the the wait time for the third one to be sent. Funny I seem to get replies faster than 14sec between

Now it works for me without using TOR. Nonetheless here is the routing with TOR on and then with TOR off.

TOR routing


Tracing route to woodworkforums.com [209.95.48.51]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 24 ms 24 ms 23 ms 172-9-4-2.lightspeed.snantx.sbcglobal.net [172.9
.4.2]
3 24 ms 24 ms 24 ms 75.28.192.122
4 28 ms 28 ms 28 ms 12.83.39.17
5 34 ms 35 ms 31 ms ggr3.dlstx.ip.att.net [12.122.138.17]
6 * * * Request timed out.
7 53 ms 52 ms 87 ms ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
8 68 ms 68 ms 69 ms ae6.mpr2.den1.us.zip.zayo.com [64.125.31.58]
9 68 ms 68 ms 68 ms ae10.mpr1.slc1.us.zip.zayo.com [64.125.21.65]
10 76 ms 75 ms 76 ms 208.184.34.150.IPYX-068416-003-ZYO.above.net [20
8.184.34.150]
11 75 ms 75 ms 76 ms 206.130.126.26.west-datacenter.net [206.130.126.
26]
12 76 ms 76 ms 76 ms 209.95.48.51.static.midphase.com [209.95.48.51]


Trace complete.



Firefox routing

Tracing route to woodworkforums.com [209.95.48.51]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 24 ms 24 ms 23 ms 172-9-4-2.lightspeed.snantx.sbcglobal.net [172.9
.4.2]
3 24 ms 24 ms 24 ms 75.28.192.122
4 28 ms 28 ms 28 ms 12.83.39.17
5 34 ms 35 ms 31 ms ggr3.dlstx.ip.att.net [12.122.138.17]
6 * * * Request timed out.
7 53 ms 52 ms 87 ms ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
8 68 ms 68 ms 69 ms ae6.mpr2.den1.us.zip.zayo.com [64.125.31.58]
9 68 ms 68 ms 68 ms ae10.mpr1.slc1.us.zip.zayo.com [64.125.21.65]
10 76 ms 75 ms 76 ms 208.184.34.150.IPYX-068416-003-ZYO.above.net [20
8.184.34.150]
11 75 ms 75 ms 76 ms 206.130.126.26.west-datacenter.net [206.130.126.
26]

My regular access is blocked again. Here's the trace.

Tracing route to woodworkforums.com [209.95.48.51]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 24 ms 24 ms 23 ms 172-9-4-2.lightspeed.snantx.sbcglobal.net [172.9
.4.2]
3 24 ms 24 ms 24 ms 75.28.192.122
4 28 ms 28 ms 28 ms 12.83.39.17
5 34 ms 35 ms 31 ms ggr3.dlstx.ip.att.net [12.122.138.17]
6 * * * Request timed out.
7 53 ms 52 ms 87 ms ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
8 68 ms 68 ms 69 ms ae6.mpr2.den1.us.zip.zayo.com [64.125.31.58]
9 68 ms 68 ms 68 ms ae10.mpr1.slc1.us.zip.zayo.com [64.125.21.65]
10 76 ms 75 ms 76 ms 208.184.34.150.IPYX-068416-003-ZYO.above.net [20
8.184.34.150]
11 75 ms 75 ms 76 ms 206.130.126.26.west-datacenter.net [206.130.126.
26]

Timeouts from this point to #30

If you are on a PC, you could try flushing your DNS by using: ipconfig /flushdns on the cmd line.
For other OSs see here: https://www.whatsmydns.net/flush-dns.html

Originally Posted by hiroller

If you are on a PC, you could try flushing your DNS by using: ipconfig /flushdns on the cmd line.
For other OSs see here: https://www.whatsmydns.net/flush-dns.html

Did it, no improvement. I still have to use TOR to get around the server that is timing me out.

I guess the longer time limit also prevents PM's being sent and received to buyers and sellers in quick time.

Originally Posted by rob streeper

My regular access is blocked again. Here's the trace.

Tracing route to woodworkforums.com [209.95.48.51]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 24 ms 24 ms 23 ms 172-9-4-2.lightspeed.snantx.sbcglobal.net [172.9
.4.2]
3 24 ms 24 ms 24 ms 75.28.192.122
4 28 ms 28 ms 28 ms 12.83.39.17
5 34 ms 35 ms 31 ms ggr3.dlstx.ip.att.net [12.122.138.17]
6 * * * Request timed out.
7 53 ms 52 ms 87 ms ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
8 68 ms 68 ms 69 ms ae6.mpr2.den1.us.zip.zayo.com [64.125.31.58]
9 68 ms 68 ms 68 ms ae10.mpr1.slc1.us.zip.zayo.com [64.125.21.65]
10 76 ms 75 ms 76 ms 208.184.34.150.IPYX-068416-003-ZYO.above.net [20
8.184.34.150]
11 75 ms 75 ms 76 ms 206.130.126.26.west-datacenter.net [206.130.126.
26]

Timeouts from this point to #30

I ran a tracert on my system, and it gets to the forum on the hop after west-datacentre.net (your hop 11). So I'm not at all sure how this can be a problem with your system, as you were only 1 hop away.

Agreed, more likely an issue with your DNS provider.
Have your tried updating your DNS settings to different provider.
You could try the Google settings mentioned previously by Evanism.

Also make sure you don't have an entry for woodworkforums.com in your computers hosts file.

PS - we're working through a few fixes along with looking into this.

Originally Posted by hiroller

Agreed, more likely an issue with your DNS provider.
Have your tried updating your DNS settings to different provider.
You could try the Google settings mentioned previously by Evanism.

Did it, no improvement.