It's allover red rover.
:fingerscrossed:
Printable View
It's allover red rover.
:fingerscrossed:
Thanks Neil, and please say thanks to Steven too.
:brava:fingerscrossed:
Back up to proper speed for me. Thanks for getting it sorted :2tsup:
So far so good.:2tsup:
Best it has worked for me in months, thank you.
pker:U
Looks like the Squirrels have been fed.
This problem over the last week or so certainly kept Steven the 'puta guru and Neil a tad busy.
Thanks guys for all the extra work.
Alan...
Both me and Neil were very busy at times working on this, but since it was outside of our control the rest was mostly a waiting game. Its looking good so far though.
Everyones patience and feedback over the last week (and several months) is also very appreciated. :2tsup:
Solved :2tsup: or at least it is at the moment - great work by those involved.
All happening on Star Wars Day,
"May the fourth be with you."
yep blindingly (almost) faster than the last few days
great work guys
A ping of woodworkforims.com currently shows a consistent speed of 195ms which is the fastest the forums have ever run since coming on line 25 years ago.
I think it's time to break this one out again. http://ubeaut.biz/woohoo.gif
I don't think I'm being premature this time.
As Steven said thanks to everyone for being so patient over the last week and for the feedback. Without that feedback it can take a lot more time to get to the root of some problems.
Cheers - Neil :2tsup:
Hi,
Looking good now, but went to bed half an hour after the time others were getting in last night as I was still being timed out.
Good on you all
:):D:U:U:D:)
(all grins)
Fantastic job guys. As someone said earlier, it's the fastest I have ever seen it run:yippee:
I notice you haven't put that big tempting red button on again Neil:roll:
Thanks for the fix guys, it is now officially awesome!
Your efforts running and keeping the forum going is much appreciated.:2tsup::2tsup:
Cheers, Ian
Totally agree guys - fantastic job - Well Done :clap:
Sorry to throw a spanner in the works, but I have noticed a weird side effect of the new server.
Since the latest migration (last night), Outlook is sending all new post/PM notification emails to my junk folder. I've told it 4 times now that [email protected] is safe, but they're still getting filtered :?
Is anyone else getting this problem? Any ideas why it's happening?
EDIT: Adding WWF to my contacts seems to have fixed it.
Starting late last week I've been unable to get the Forum to connect. I use Firefox most of the time but I also tried Chrome. Refreshing my browser didn't help. Another computer in the house was unable to connect too. Today I had the idea to use the TOR browser on Firefox and I can now get to the site. Could the NSA now be monitoring subversive woodworkers?
Hey this speed is like years ago :p :2tsup:
Ah can someone rest the time limit on PM's 145 sec's between is a wee bit much don't ya thunk. Thanks in advance
Quote:
Originally Posted by wheelinround
If you are using a bookmarked login, stop. Delete the login and type in or copy this url https://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.Quote:
Originally Posted by rob streeper
Hope this is of some help.
Cheers - Neil :U
Rob's issue sounds like mine (DNS points to 209.95.48.51 for me, which seems to be the new address?). It seems like the server is just plain not responding to me, I can't ping the server unless I use a different Internet link.
I'm a network engineer in my day job, happy to help if I can be of any assistance!
Change your dns to 8.8.8.8 and 8.8.4.4
These are googles public DNS. It's fast, free and soon to be secure.
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
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 :U
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
Me too - I am connected again from the connection that wasn't working before - thanks team!
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