New equipment installed - report bugs here

[Gary - K7GLD]

Talk about a LOOOoong, circular route - this may be the reason for some of the slowness I've been seeing on this forum...

C:\Documents and Settings\Gary Davidson. GARYSPC. 000>tracert turbodieselregister.

com



Tracing route to turbodieselregister.com [69. 61. 74. 242]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms dslrouter [192. 168. 1. 1]

2 64 ms 61 ms 61 ms aurrorcobr1. aurrorcoro1. centurytel.net [69. 29. 18

5. 6]

3 78 ms 75 ms 73 ms aurrorcoro2. aurrorcoro1. centurytel.net [209. 206.

179. 130]

4 72 ms 64 ms 65 ms ge-6-1. car3. Seattle1. Level3.net [4. 79. 104. 41]

5 78 ms 72 ms 64 ms ae-1-53. mp1. Seattle1. Level3.net [4. 68. 105. 65]

6 85 ms 83 ms 89 ms ae-0-0. bbr1. SanJose1. Level3.net [64. 159. 1. 129]

7 93 ms 84 ms 94 ms ae-14-55. car4. SanJose1. Level3.net [4. 68. 123. 142]



8 89 ms 87 ms 82 ms cpr1-ge-4-1. sanjoseequinix. savvis.net [208. 173. 5

4. 53]

9 89 ms 86 ms 87 ms dcr1-so-3-2-0. SanFranciscosfo. savvis.net [208. 17

3. 54. 66]

10 105 ms 94 ms 105 ms dcr2. lay-so-5-1-0. losangeles. savvis.net [204. 70.

194. 50]

11 149 ms 119 ms 121 ms dcr1-so-2-0-0. dallas. savvis.net [204. 70. 192. 85]



12 176 ms 199 ms 155 ms bar4-serial-4-1-1. losangeles. savvis.net [204. 70.

194. 177]

13 161 ms 158 ms 151 ms bpr1-so-0-0-0. AtlantaPaix. savvis.net [208. 172. 75

. 110]

14 152 ms 152 ms 151 ms 216. 89. 82. 74

15 153 ms 170 ms 163 ms ge-1-atl1-cust1. globalcompass.com [66. 154. 95. 221

]

16 150 ms 155 ms 154 ms 66. 154. 81. 110

17 175 ms 177 ms 154 ms 66. 154. 81. 110

18 152 ms 154 ms 158 ms turbodieselregister.com [69. 61. 74. 242]



Trace complete.

 

[TORQUE THIS]

I have not been getting my emails for subscribed threads, It seems like this started around the same time of the upgrade (maybe by chance)


Michael

Also for me, no e-mails. Was slow on Friday afternoon and is a little slow right now.

 

[Steve St.Laurent]

I'm working on the email issue. It's because we have a firewall in place now and some email providers are rejecting emails from us because they are going through the firewall and it doesn't have a DNS entry. I'll get it fixed as soon as I can. As far as slowness I discovered on friday that the firewall that our security consultant got for us is a 10 mbit firewall when it was supposed to be a 100 mbit firewall. He's working on getting us a replacement as soon as possible. This may cause some minor issues until we can get it replaced.



Keep in mind that if you are look at threads with pictures in them that there can be up to a 5 second delay per picture if the host server the picture is on is slow to send it out or doesn't allow connections.

 

[Steve St.Laurent]

Your emails should be getting through now.

 

[TORQUE THIS]

uh, yeah... just got hit with about 30...


Thanks Steve!

 

[Highfinance97]

Your emails should be getting through now.

i just checked my mail and had 35 from TDR :-laf :-laf





and only 3 subscribed threads :-laf





thanks for the fix



Michael

 

[Steve St.Laurent]

A replacement firewall is being overnighted to us on monday. It should be in place some time on tuesday.

 

[nickleinonen]

never tried that trace thing before, so i did. . mines a little shorter [i don't have any complaints about speed as long as i leave my bittorrent programs offline]

C:\Documents and Settings\Nick Leinonen>tracert turbodieselregister.com



Tracing route to turbodieselregister.com [69. 61. 74. 242]

over a maximum of 30 hops:



1 1 ms <1 ms <1 ms 192. 168. 0. 1

2 17 ms 8 ms 9 ms 10. 238. 210. 1

3 8 ms 7 ms 10 ms gw03. mtmk. phub.net. cable. rogers.com [66. 185. 91. 9]

4 8 ms 7 ms 8 ms gw01. mtmk. phub.net. cable. rogers.com [66. 185. 83. 249]

5 12 ms 11 ms 9 ms 64. 71. 240. 185

6 10 ms 12 ms 9 ms gw02. bloor. phub.net. cable. rogers.com [66. 185. 80. 165]

7 20 ms 19 ms 23 ms igw01. chcrmk. phub.net. cable. rogers.com [66. 185. 80. 201]

8 20 ms 28 ms 19 ms ge2-1. br02. chc01. pccwbtn.net [63. 218. 5. 5]

9 55 ms 54 ms 52 ms globalcompass. ge2-1. br01. atl01. pccwbtn.net [63. 216. 31. 134]

10 56 ms 58 ms 65 ms ge-1-atl1-cust1. globalcompass.com [66. 154. 95. 221]

11 54 ms 57 ms 54 ms turbodieselregister.com [66. 154. 81. 110]

12 54 ms 54 ms 56 ms turbodieselregister.com [69. 61. 74. 242]



Trace complete.

 

[Gary - K7GLD]

Your times and routes sure are cleaner than mine - site is slow again here this morning, even with pretty light traffic...

 

[GHarman]

Steve, Ive been crusing through some earlier threads. Ladder Bars, as an example. Where pictures are called for, they are not available Link Disabled? Thanks for your long hours and hard (SMART) work. GregH

 

[Steve St.Laurent]

They are pictures that were on other peoples servers (or possibly our readers rig section) that have been removed. When someone links to a picture we have no control over how long that picture stays available.

 

[Tomeygun]

I am seeing some thread update emails are being delayed



I mean I see I have PM's - But no emails in my inbox to tell me...

 

[Steve St.Laurent]

Tomeygun - your emails are being returned as undeliverable. Your server is saying "User unknown". Check your email setting in your control panel and make sure that your email address is correct. If it is you might check with your email provider to see what's going on.

 

[Steve St.Laurent]

The new firewall is in place and running. Let me know if you run into any performance problems. Things are flying here. If you see any slowness please do several tracert's first by going to your command prompt (usually start->programs->accessories->command prompt) and then type:



tracert www.turbodieselregister.com



Look for any asterisks in the columns which means you are timing out at that location. If it's anywhere before global compass it means there is a problem on the backbone between you and the servers and that would be out of our control. Do several of them because it may be an intermittent problem.



-Steve

 

[Steve St.Laurent]

BTW, 95% of our traffic is hitting the new (load balanced) servers now. Hopefully the 5% slacker ISP's get their DNS updated before I have to turn off the old IP address in 8 days.

 

[Tomeygun]

Tomeygun - your emails are being returned as undeliverable. Your server is saying "User unknown". Check your email setting in your control panel and make sure that your email address is correct. If it is you might check with your email provider to see what's going on.

Can you ping me again? Maybe from a outlook?

I am getting all other mail, Just not TDR mail



I used the control panel and just confirmed and submited my address again...



BTW - last successful email I rec'd was "Mon 11/20/2006 8:24 AM"

 

[PRout]

Site runs good to Long Beach, Ca...
Here's some quick snippets from some linux boxes & cisco stuff. .

*****

[root@Ely log]# nslookup turbodieselregister.com
Server: 192. 168. 150. 100
Address: 192. 168. 150. 100#53
Non-authoritative answer:
Name: turbodieselregister.com
Address: 69. 61. 74. 242

[root@Ely log]# grep 69. 61. 74. 242 cisco-log
Dec 3 12:03:48 reno. **.net 8046: Dec 3 12:03:47: %SEC-6-IPACCESSLOGP: list 110 permitted tcp 192. 168. 100. 15(49179) -> 69. 61. 74. 242(80), 25 packets

Ping w/ full-size packets:
Carson-City#p
Protocol [ip]:
Target IP address: turbodieselregister.com
Repeat count [5]: 25
Datagram size [100]: 1500
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 24. 176. 210. 94
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]: v
Loose, Strict, Record, Timestamp, Verbose[V]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 25, 1500-byte ICMP Echos to 69. 61. 74. 242, timeout is 2 seconds:
Packet sent with a source address of 24. 176. 210. 94
Reply to request 0 (80 ms)
Reply to request 1 (80 ms)
Reply to request 2 (80 ms)
Reply to request 3 (120 ms)
Reply to request 4 (104 ms)
Reply to request 5 (88 ms)
Reply to request 6 (76 ms)
Reply to request 7 (84 ms)
Reply to request 8 (80 ms)
Reply to request 9 (100 ms)
Reply to request 10 (92 ms)
Reply to request 11 (88 ms)
Reply to request 12 (80 ms)
Reply to request 13 (76 ms)
Reply to request 14 (80 ms)
Reply to request 15 (80 ms)
Reply to request 16 (80 ms)
Reply to request 17 (84 ms)
Reply to request 18 (92 ms)
Reply to request 19 (80 ms)
Reply to request 20 (80 ms)
Reply to request 21 (80 ms)
Reply to request 22 (84 ms)
Reply to request 23 (80 ms)
Reply to request 24 (84 ms)
Success rate is 100 percent (25/25), round-trip min/avg/max = 76/85/120 ms

Ping w/ small packets:
Carson-City#p
Protocol [ip]:
Target IP address: turbodieselregister.com
Repeat count [5]: 25
Datagram size [100]: 36
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 24. 176. 210. 94
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]: v
Loose, Strict, Record, Timestamp, Verbose[V]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 25, 36-byte ICMP Echos to 69. 61. 74. 242, timeout is 2 seconds:
Packet sent with a source address of 24. 176. 210. 94
Reply to request 0 (72 ms)
Reply to request 1 (68 ms)
Reply to request 2 (68 ms)
Reply to request 3 (72 ms)
Reply to request 4 (96 ms)
Reply to request 5 (76 ms)
Reply to request 6 (68 ms)
Reply to request 7 (72 ms)
Reply to request 8 (80 ms)
Reply to request 9 (80 ms)
Reply to request 10 (80 ms)
Reply to request 11 (68 ms)
Reply to request 12 (68 ms)
Reply to request 13 (72 ms)
Reply to request 14 (72 ms)
Reply to request 15 (72 ms)
Reply to request 16 (68 ms)
Reply to request 17 (88 ms)
Reply to request 18 (80 ms)
Reply to request 19 (68 ms)
Reply to request 20 (72 ms)
Reply to request 21 (80 ms)
Reply to request 22 (68 ms)
Reply to request 23 (64 ms)
Reply to request 24 (84 ms)
Success rate is 100 percent (25/25), round-trip min/avg/max = 64/74/96 ms