My host finally got my new server online for us.  It took them a while because the CPU I requested was out of stock.  I really wish they did what they did last time

and upgrade the CPU, I ordered a Dual-Core Xeon last time and they gave me a Quad-Core Xeon for the price of the Dual-Core.

Although the CPU in the new server isn't as strong as the current server there are many additions to the new server that end up way more than making up for that....

First of all the new server has two times the RAM of the current server and is also running dual 146GB SCSI/SAS 10,000RPM drives. These two upgrades over the current

server make a huge difference on a webserver that has as many database queries as testmy.net's does.  The current server is running dual 7200 RPM 250GB SATA drives by

the way... the SCSI/SAS drives on the new server are a nice upgrade.

You may ask... "So why is testmy.net getting a new server again?  I thought you guys just got a new server about a month ago!"
A:  testmy.net DID in fact get a new server a little over a month ago, the reason why I've ordered ANOTHER new server is because my host put the last server in a

datacenter that I HATE.  My host has multipule datacenters, some in Dallas and some in Houston.  The Houston datacenter was one that they bought out from an old

hosting company called "EV1".  The quality of the EV1 datacenter is inferior when compared to the Dallas datacenter that testmy.net usually runs out of.  So once I

noticed that I was in that datacenter I knew right away that I'd be reordering very soon, though I did try to make the best of it.  But despite hard efforts on my end

I just couldn't do anything to improve the quality of the server and I tried everything to make the best of it until I could get another new server.  Put it this way,

although Dallas, TX is only about 240 miles from Houston, TX my personal ping to testmy.net when it's in the crappy datacenter is about 50ms (I just now pinged that

and got an average of 52ms).  I just now pinged the new server, which is now in the correct Dallas, TX datacenter and I got an average ping of 33ms.  Pretty funny how

the Houston datacenter pings 20ms higher when the Houston datacenter is only 100miles further from me than the Dallas datacenter, hahaha.

If you'd like to see what I'm talking about... and actually, if you'd like to see if you've been effected over the past month from the terrible routing to this

datacenter (because not everyone out there get bad routing to this datacenter) you can ping both servers and see the difference that you get... for fun, how about you

guys post your personal pings to both servers... it will prove my point and show you all why i really needed to order ANOTHER server.

The IP for the server in Houston (the current server that's being replaced) is  ::   75.125.181.200 
The IP for the server in Dallas (the server that will be replacing the current one) is  ::   74.54.226.170

Ping both and share with us

Here's mine


You can also see a difference in the trace route


And by the way... that is the cleanest trace route to the Houston server that I've ever had... the trace to that server is usually WAY worse than that.



In conclusion, the new server is now online.  I've already configured most of the custom stuff that I run on my servers and now I'll be starting the transfer of all

the data.  The new server is expected to be 100% functional within the next 24 hours but most likely sooner than that.  This will mean upgraded speed and reliability

for all TMN users.

The new server configuration ::

CPU  ::  Conroe \ Xeon 3060 (Dual Core)
Memory (RAM)  ::  4GB (4096MB) DDR2 800
Memory (HDD0)  ::  146GB SCSI/SAS 10,000RPM
Memory (HDD1)  ::  146GB SCSI/SAS 10,000RPM
Up-link  ::  100Mbps up-link to theplanet's premier Dallas, TX datacenters this means access to over 100Gbps of tier1 bandwidth (

http://www.theplanet.com/tour/default.html )

So I'll let you guys know once you're on the new server, the first clue that you're on the new server will be a message you'll see on the homepage letting you know

that you're on the new server.  So give me a little bit of time to get the data transfered.  Please note that during this process some posts to the forum MAY be lost,

the reason being that the database along with the site data will be transfered and any posts made from that time to the time that it will take for me to change the DNS

over to the new IP may be lost.  In the past this has only resulted in a couple of posts being lost but I would like to let you all know this in advance.  Please also

note that the site may be slow to respond and/or throw errors during this process.  This is because the amount of information being transfered is HUGE nad can sometime

overload one or both of the servers (it's usually mySQL that overloads the server).  Just keep in mind that the problems are temporary and this is why I do these

transfers during off-peak hours in the middle of the night...... just hang in there, thanks for your patience during this process.

Thanks for your patience during this process, I can't wait to see the new server in full action!

-Damon

Traceroute has started ...

traceroute to 74.54.226.170 (74.54.226.170), 64 hops max, 40 byte packets
 1  DD-WRT (192.168.1.1)  9.902 ms  0.928 ms  0.714 ms
 2  cpe-98-28-64-1.columbus.res.rr.com (98.28.64.1)  9.607 ms  10.755 ms  7.926 ms
 3  network-024-029-163-073.woh.rr.com (24.29.163.73)  11.404 ms  14.600 ms  76.826 ms
 4  srp5-0.limaoh1-rtr2.woh.rr.com (24.29.163.141)  14.319 ms  13.838 ms  33.247 ms
 5  son3-0-2.mtgmoh1-rtr0.columbus.rr.com (65.25.128.157)  18.096 ms  18.684 ms  18.476 ms
 6  ae-4-0.cr0.chi30.tbone.rr.com (66.109.6.68)  34.591 ms  27.804 ms  24.701 ms
 7  ae-1-0.pr0.chi10.tbone.rr.com (66.109.6.155)  27.684 ms  28.944 ms  25.838 ms
 8  66.109.9.202 (66.109.9.202)  26.294 ms  28.549 ms  82.113 ms
 9  The-Planet.GigabitEthernet7-3.ar2.DAL2.GBlx.net (64.208.170.198)  51.570 ms  89.577 ms  52.719 ms
10  te7-2.dsr01.dllstx3.theplanet.com (70.87.253.10)  53.536 ms  55.369 ms te7-2.dsr02.dllstx3.theplanet.com (70.87.253.26)  53.775 ms
11  7e.fd.5746.static.theplanet.com (70.87.253.126)  53.845 ms  54.055 ms  65.822 ms
12  po1.car06.dllstx6.theplanet.com (12.96.160.8 )  220.582 ms  106.704 ms  90.085 ms
13  aa.e2.364a.static.theplanet.com (74.54.226.170)  53.240 ms  54.452 ms  70.814 ms

 This ip (red) is consistently excessive comparatively.

He posted the ip to the new server so do a trace to this IP
74.54.226.170

C:\Documents and Settings\Administrator>tracert 74.54.226.170

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    10 ms     9 ms     9 ms  ge-1-37-ur01.peru.in.indiana.Comcast.net [68.86.
186.113]
  3    10 ms     9 ms     9 ms  te-9-4-ur01.huntington.in.indiana.Comcast.net [6
8.86.184.158]
  4    11 ms     9 ms     9 ms  te-9-3-ur03.main.in.indiana.Comcast.net [68.86.1
84.153]
  5    15 ms    13 ms    13 ms  po-10-ur04.mishawaka.in.sbend.Comcast.net [68.86
.187.129]
  6    14 ms    13 ms    14 ms  te-3-1-ur03.mishawaka.in.sbend.Comcast.net [68.8
7.235.21]
  7     *        *       19 ms  te-1-4-ar01.woburn.ma.boston.Comcast.net [68.86.
90.54]
  8    18 ms    17 ms    17 ms  te-0-4-0-5-cr01.boston.ma.ibone.Comcast.net [68.
86.90.53]
  9    19 ms    20 ms    19 ms  TenGigabitEthernet2-2.ar5.CHI1.GBlx.net [64.213.
79.245]
 10    53 ms    53 ms    55 ms  The-Planet.GigabitEthernet7-3.ar2.DAL2.GBlx.net
[64.208.170.198]
 11    52 ms    53 ms    53 ms  te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

 12    51 ms    51 ms    50 ms  7a.fd.5746.static.theplanet.com [70.87.253.122]

 13    65 ms    52 ms    54 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]
 14    51 ms    52 ms    53 ms  aa.e2.364a.static.theplanet.com [74.54.226.170]


Trace complete.

these are from my server

C:\Documents and Settings\Administrator>tracert testmy.net

Tracing route to testmy.net [75.125.181.200]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     9 ms     9 ms    11 ms  ge-1-37-ur01.peru.in.indiana.Comcast.net [68.86.
186.113]
  3     8 ms    10 ms    10 ms  te-9-4-ur01.huntington.in.indiana.Comcast.net [6
8.86.184.158]
  4    10 ms     9 ms     9 ms  te-9-3-ur03.main.in.indiana.Comcast.net [68.86.1
84.153]
  5    14 ms    13 ms    13 ms  po-10-ur04.mishawaka.in.sbend.Comcast.net [68.86
.187.129]
  6    15 ms    13 ms    14 ms  te-3-1-ur03.mishawaka.in.sbend.Comcast.net [68.8
7.235.21]
  7     *       19 ms    19 ms  te-3-1-ar01.chartford.ct.hartford.Comcast.net [6
8.86.90.58]
  8    18 ms    19 ms    20 ms  te-0-4-0-0-cr01.newyork.ny.ibone.Comcast.net [68
.86.90.57]
  9    20 ms    19 ms    20 ms  68.86.88.246
 10    48 ms    48 ms    47 ms  216-54-253-2.ev1.net.demarc [216.54.253.2]
 11    49 ms    48 ms    47 ms  216-54-253-2.ev1.net.demarc [216.54.253.2]
 12    51 ms    53 ms    50 ms  ivhou-207-218-223-126.ev1servers.net [207.218.22
3.126]
 13    52 ms    51 ms    51 ms  75.125.181.200

Trace complete.

C:\Users\Familjen>ping 74.54.226.170

Pinging 74.54.226.170 with 32 bytes of data:

Reply from 74.54.226.170: bytes=32 time=170ms TTL=46
Reply from 74.54.226.170: bytes=32 time=165ms TTL=46
Reply from 74.54.226.170: bytes=32 time=164ms TTL=46
Reply from 74.54.226.170: bytes=32 time=164ms TTL=46

Ping statistics for 74.54.226.170:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 164ms, Maximum = 170ms, Average = 165ms

C:\Users\Familjen>tracert 74.54.226.170

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     5 ms     5 ms     5 ms  gw1-no116.tbcn.telia.com [90.224.86.1]
  3    20 ms    20 ms    20 ms  global-ic-120468-s-b1.c.telia.net [213.248.77.21
4]
  4   167 ms   166 ms   168 ms  The-Planet.GigabitEthernet7-3.ar2.DAL2.GBlx.net
[64.208.170.198]
  5   163 ms   163 ms   161 ms  te9-2.dsr02.dllstx3.theplanet.com [70.87.253.30]

  6   166 ms   164 ms   168 ms  7e.fd.5746.static.theplanet.com [70.87.253.126]

  7   180 ms   208 ms   166 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]
  8   167 ms   165 ms   165 ms  aa.e2.364a.static.theplanet.com [74.54.226.170]


Trace complete.

C:\Users\Familjen>ping 75.125.181.200

Pinging 75.125.181.200 with 32 bytes of data:

Reply from 75.125.181.200: bytes=32 time=182ms TTL=47
Reply from 75.125.181.200: bytes=32 time=188ms TTL=47
Reply from 75.125.181.200: bytes=32 time=182ms TTL=47
Reply from 75.125.181.200: bytes=32 time=190ms TTL=47

Ping statistics for 75.125.181.200:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 182ms, Maximum = 190ms, Average = 185ms

C:\Users\Familjen>tracert 75.125.181.200

Tracing route to 75.125.181.200 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     5 ms     5 ms     5 ms  gw1-no116.tbcn.telia.com [90.224.86.1]
  3    20 ms    19 ms    20 ms  s-bb1-link.telia.net [80.91.254.58]
  4    60 ms    59 ms    98 ms  ffm-bb1-link.telia.net [80.91.248.53]
  5    59 ms    55 ms    55 ms  ffm-b3-link.telia.net [80.91.254.37]
  6    70 ms    70 ms    70 ms  verio-116678-ffm-b3.telia.net [213.248.69.50]
  7    63 ms    63 ms    63 ms  as-0.r23.amstnl02.nl.bb.gin.ntt.net [129.250.5.2
2]
  8   158 ms   155 ms   156 ms  as-0.r20.asbnva01.us.bb.gin.ntt.net [129.250.5.4
6]
  9   148 ms   147 ms   169 ms  ae-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.1
7]
 10   184 ms   189 ms   180 ms  p64-3-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.25
0.5.24]
 11     *        *        *     Request timed out.
 12   190 ms   197 ms   197 ms  xe-4-3.r04.hstntx01.us.bb.gin.ntt.net [129.250.4
.234]
 13   179 ms   188 ms   184 ms  ge-4.ev1.hstntx01.us.bb.gin.ntt.net [129.250.10.
142]
 14   180 ms   184 ms   179 ms  ivhou-207-218-223-126.ev1servers.net [207.218.22
3.126]
 15   179 ms   188 ms   181 ms  75.125.181.200

Trace complete.

dern 8 hops all the way from northern Sweden, that rules

my beautiful pings
Done 5:25pm ct
Dallas:


C:\Users\Justin Lay>ping 74.54.226.170

Pinging 74.54.226.170 with 32 bytes of data:
Reply from 74.54.226.170: bytes=32 time=10ms TTL=51
Reply from 74.54.226.170: bytes=32 time=8ms TTL=51
Reply from 74.54.226.170: bytes=32 time=11ms TTL=51
Reply from 74.54.226.170: bytes=32 time=8ms TTL=51

Ping statistics for 74.54.226.170:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 11ms, Average = 9ms

Houston:


C:\Users\Justin Lay>ping 75.125.181.200

Pinging 75.125.181.200 with 32 bytes of data:
Reply from 75.125.181.200: bytes=32 time=27ms TTL=49
Reply from 75.125.181.200: bytes=32 time=20ms TTL=49
Reply from 75.125.181.200: bytes=32 time=22ms TTL=49
Reply from 75.125.181.200: bytes=32 time=20ms TTL=49

Ping statistics for 75.125.181.200:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 27ms, Average = 22ms


C:\Users\Justin Lay>tracert 74.54.226.170

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  192.168.0.1
  2     5 ms     7 ms     5 ms  10.60.100.1
  3     5 ms     5 ms     4 ms  10.60.1.25
  4    19 ms    15 ms    22 ms  101-246-171-216.belwave.com [216.171.246.101]
  5    15 ms    13 ms     7 ms  145-161-125-64.belwave.net [64.125.161.145]
  6     9 ms    10 ms     8 ms  ge-17-96-195-216.belwave.net [216.195.96.17]
  7     9 ms    13 ms     8 ms  ge-9-96-195-216.belwave.net [216.195.96.9]
  8    28 ms     8 ms    11 ms  396.ge-3-1-0.mpr2.lga3.us.above.net [64.125.129.
11]
  9    10 ms    12 ms    10 ms  xe-1-1-0.er2.dfw2.us.above.net [64.125.26.214]
 10    16 ms    12 ms    22 ms  xe-0-0-0.er1.dfw2.us.above.net [64.125.26.205]
 11    10 ms    11 ms     9 ms  209.66.99.90.available.above.net [209.66.99.90]

 12    13 ms    18 ms    12 ms  te9-1.dsr02.dllstx3.theplanet.com [70.87.253.22]

 13     9 ms    20 ms    10 ms  7e.fd.5746.static.theplanet.com [70.87.253.126]

 14     9 ms     9 ms    10 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]
 15    11 ms    10 ms    10 ms  aa.e2.364a.static.theplanet.com [74.54.226.170]


Trace complete.

Here it is here at work.


And on my DSL line.



Both lines show the new server is much better routeing/ping times from kansas city.

Ugh this is going to blow even harder than the current.... 
Well i hope i can get the speeds back regardless of the incredibly far-routed server.. 


Tracing route to testmy.net [75.125.181.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     7 ms     6 ms     7 ms  72.91.11.1
  3    10 ms     9 ms    10 ms  P9-0.LCR-04.TAMPFL.verizon-gni.net [130.81.59.66]
  4    32 ms    22 ms    21 ms  so-6-0-0-0.PEER-RTR1.ATL81.verizon-gni.net [130.81.17.141]
  5    22 ms    21 ms    23 ms  130.81.14.18
  6    54 ms    54 ms    54 ms  216-54-253-2.ev1.net.demarc [216.54.253.2]
  7    55 ms    54 ms    54 ms  216-54-253-2.ev1.net.demarc [216.54.253.2]
  8    55 ms    54 ms    55 ms  ivhou-207-218-223-126.ev1servers.net [207.218.223.126]
  9    54 ms    52 ms    51 ms  75.125.181.200

Trace complete.



Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     6 ms     7 ms     8 ms  72.91.11.1
  3    10 ms     9 ms    10 ms  P9-0.LCR-04.TAMPFL.verizon-gni.net [130.81.59.66]
  4    42 ms    41 ms    42 ms  so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81.10.94]
  5    41 ms    41 ms    42 ms  130.81.15.42
  6    75 ms    41 ms    41 ms  so-4-0-0.mpr1.iad2.us.above.net [64.125.30.118]
  7    46 ms    44 ms    44 ms  so-6-0-0.mpr1.iad5.us.above.net [64.125.27.74]
  8    67 ms    44 ms    45 ms  so-4-0-0.mpr1.iad1.us.above.net [64.125.29.229]
  9    45 ms    44 ms    45 ms  so-1-0-0.mpr1.dca2.us.above.net [64.125.28.125]
 10    84 ms    85 ms    84 ms  so-1-0-0.mpr3.iah1.us.above.net [64.125.29.37]
 11    85 ms    85 ms    94 ms  so-1-1-0.mpr1.dfw2.us.above.net [64.125.26.129]
 12   109 ms    84 ms    84 ms  xe-1-1-0.er1.dfw2.us.above.net [64.125.26.210]
 13    59 ms    59 ms    59 ms  209.66.99.90.available.above.net [209.66.99.90]
 14    60 ms    59 ms    59 ms  te7-1.dsr02.dllstx3.theplanet.com [70.87.253.18]
 15    60 ms    59 ms    59 ms  7a.fd.5746.static.theplanet.com [70.87.253.122]
 16    62 ms    76 ms    79 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]
 17    58 ms    59 ms    59 ms  aa.e2.364a.static.theplanet.com [74.54.226.170]


Trace complete.