Jump to content
Welcome Guest! Please read more information about our club!

Server IP Change

Featured Replies

comment_354692

The new sever seems hyper-slow? Here is a test to verify:

ping zcar.com

Pinging zcar.com [208.43.51.5] with 32 bytes of data:

Ping statistics for 208.43.51.5:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 70ms, Maximum = 155ms, Average = 116ms

ping classiczcars.com

Pinging classiczcars.com [173.164.116.65] with 32 bytes of data:

Ping statistics for 173.164.116.65:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 143ms, Maximum = 375ms, Average = 226ms

C:\Users\Owner>


comment_354693

ping zcar.com

Ping statistics for 208.43.51.5:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 68ms, Maximum = 69ms, Average = 68ms

ping classiczcars.com

Ping statistics for 173.164.116.65:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 135ms, Maximum = 137ms, Average = 135ms

  • Author
comment_354699

Hmm, it shouldn't be slow. The new service plan is 50Mbps download and 10Mbps upload. The upload value is what all users should see on the site. I'll have to check into this. I wonder if there's a speed tester for command line Linux? Do you know of any tools to do this?

m

  • Author
comment_354704

Just checked with the ISP and there's nothing physically causing this link to be slow. Speed tests indicate that we should be seeing speeds in excess of 11Mbps from the server to end users. I'm wondering if there's something on the server causing this such as link speed or firewall issue. Looking into it now.

comment_354709

could be routing. I did a trace route and the path was halifax-nyc-dc-atlanta-dallas-la-oregon.

Here are some linux commands:

http://linux.about.com/od/commands/l/blcmdl8_ping.htm

http://linux.about.com/library/cmd/blcmdl8_traceroute.htm

btw this is my second attempt at replying as my first attempt timed out

  • Author
comment_354937

We found some interesting things today with the IP addresses after the move. I removed some extra IP's associated with the Eth0 card and restarted the server. This may make an improvement on the packet loss.

However, I also noticed that our newest software changes has been showing more CPU use than with our previous software. I've got plans to move the server to a new more powerful machine this month. The new machine has got two processors (dual core) and twice as much memory. The HDD's are in a RAID5 configuration which should also improve performance. These changes alone should make the system much more efficient.

I also did some digging into our new ISP and it looks like we are seeing well above the rates that were purchased. Getting 60Mbps downloads and 15Mbps uploads and we are paying for 50/10. So, the network side looks like it's working just fine.

I'm going to save too much digging on this until we are able to put the new server in place. From what I can see, a hardware improvement will make this place much more efficient. At least until the next upgrade. HA.

m

comment_354951

Thanks for the diligent work and upgrades! Unfortunately I am still getting packet drops. The path seems fine up to Dallas however once it goes into comcast's west coast network it falls apart.

Pinging classiczcars.com [173.164.116.65] with 32 bytes of data:

Reply from 173.164.116.65: bytes=32 time=141ms TTL=46

Reply from 173.164.116.65: bytes=32 time=142ms TTL=46

Reply from 173.164.116.65: bytes=32 time=141ms TTL=46

Request timed out.

Ping statistics for 173.164.116.65:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 141ms, Maximum = 142ms, Average = 141ms

Pinging zcar.com [208.43.51.5] with 32 bytes of data:

Reply from 208.43.51.5: bytes=32 time=69ms TTL=54

Reply from 208.43.51.5: bytes=32 time=69ms TTL=54

Reply from 208.43.51.5: bytes=32 time=70ms TTL=55

Reply from 208.43.51.5: bytes=32 time=69ms TTL=54

Ping statistics for 208.43.51.5:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 69ms, Maximum = 70ms, Average = 69ms

Tracing route to classiczcars.com [173.164.116.65]

over a maximum of 30 hops:

1 5 ms 4 ms 5 ms 192.168.0.1

2 16 ms 15 ms 16 ms loop0.87w.ba15.hlfx.ns.aliant.net [142.176.50.14]

3 15 ms 29 ms 15 ms te-0-0-0-0-83.cr01.hlfx.ns.aliant.net [142.176.53.34]

4 15 ms 15 ms 17 ms xe-8-2-1.cr02.hlfx.ns.aliant.net [142.166.185.66]

5 15 ms 15 ms 16 ms xe-2-0-0.cr02.drmo.ns.aliant.net [142.166.185.74]

6 37 ms 37 ms 38 ms xe-0-0-0.bx01.toro.on.aliant.net [207.231.227.86]

7 38 ms 38 ms 53 ms 67.69.211.21

8 52 ms 74 ms 60 ms BX4-CHICAGODT_POS12-0.net.bell.ca [64.230.186.238]

9 53 ms 73 ms 54 ms be-10-407-pe01.350ecermak.il.ibone.comcast.net [75.149.231.37]

10 55 ms 55 ms 54 ms pos-0-3-0-0-cr01.chicago.il.ibone.comcast.net [68.86.87.249]

11 65 ms 63 ms 63 ms pos-2-14-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.170]

12 85 ms 85 ms 86 ms pos-1-10-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.86.129]

13 * 130 ms 136 ms pos-0-13-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.85.145]

14 124 ms 125 ms * pos-0-15-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.85]

15 136 ms 138 ms 136 ms so-1-0-0-0-ar03.beaverton.or.bverton.comcast.net [68.86.95.110]

16 160 ms * 137 ms po-10-ar01.beaverton.or.bverton.comcast.net [68.87.218.165]

17 * 140 ms 139 ms te-8-2-ur01.eugene.or.bverton.comcast.net [68.87.218.210]

18 * 137 ms 136 ms ge-3-1-0-ten02.eugene.or.bverton.comcast.net [68.85.148.118]

19 150 ms * TOSHIBA [192.168.0.105] reports: Destination host unreachable.

Trace complete.

  • Author
comment_354967

Hi Blue, it looks like you are just farther away (in hops) from our server. Your route seems to jump across the entire USA before it even gets to us. It doesn't appear that changes to our server will improve your speed.

I'll raise the issue with Comcast to see if they have any answers about this.

comment_354977

just for reference I am in south florida

Ping 173.164.116.65

[classiczcars.com]

Round trip time to 173.164.116.65: 69 ms

Round trip time to 173.164.116.65: 69 ms

Round trip time to 173.164.116.65: 69 ms

Round trip time to 173.164.116.65: 69 ms

Round trip time to 173.164.116.65: 70 ms

Round trip time to 173.164.116.65: 67 ms

Round trip time to 173.164.116.65: 69 ms

Round trip time to 173.164.116.65: 67 ms

Round trip time to 173.164.116.65: 67 ms

Round trip time to 173.164.116.65: 68 ms

Average time over 10 pings: 68.4 ms

TraceRoute to 173.164.116.65 [classiczcars.com]

Hop (ms) (ms) (ms) IP Address Host name

1 1 0 0 206.123.64.154 -

2 0 0 0 64.124.196.225 xe-4-2-0.er2.dfw2.us.above.net

3 0 0 0 64.125.26.205 xe-0-0-0.er1.dfw2.us.above.net

4 1 0 0 64.125.13.186 above-comcast.dfw2.us.above.net

5 0 0 0 68.86.86.89 pos-2-0-0-0-cr01.dallas.tx.ibone.comcast.net

6 34 34 34 68.86.86.217 pos-0-10-0-0-cr01.losangeles.ca.ibone.comcast.net

7 44 45 44 68.86.86.1 pos-0-13-0-0-cr01.sacramento.ca.ibone.comcast.net

8 57 57 57 68.86.95.118 so-6-0-0-0-ar03.beaverton.or.bverton.comcast.net

9 57 58 57 68.87.218.165 po-10-ar01.beaverton.or.bverton.comcast.net

10 61 61 61 68.87.218.210 te-8-2-ur01.eugene.or.bverton.comcast.net

11 55 55 55 68.85.148.118 ge-3-1-0-ten02.eugene.or.bverton.comcast.net

12 60 61 61 96.132.221.202 -

13 67 67 67 173.164.116.65 173-164-116-65-oregon.hfc.comcastbusiness.net

Trace complete

Create an account or sign in to comment

Go to topic listing

Recently Browsing 0

  • No registered users viewing this page.

Important Information

By using this site, you agree to our Privacy Policy and Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.