Jump to content

THIS SERVER **** SUCKS


reefnjunkie

Recommended Posts

Here we go again. Slowness and timeing out. What exactly are we supposed to do to try and help? I'm not real computer savvy.

 

If anyone sees slowness today please run these commands and post results in this thread:

 

Windows:

Start menu - Run - 'cmd' enter - 'tracert pnwmas.org' enter (control-c to break out of it if needed)

 

from the same command (cmd) window 'ping -n 50 pnwmas.org' enter

 

Mac:

Terminal app - 'traceroute pnwmas.org' enter (control-c to break out of it)

 

'ping -c 50 pmwmas.org'

Link to comment
Share on other sites

Let's not forget that your ISP could be having an issue at any given time. If you ping our site (pnwmas.org) and see dropped packets that's not always our issue. Try pinging a few other sites (google.com, yahoo.com, ebay.com) and see if those sites are dropping packets also. If they are then it's a very good indication the issue lies with your ISP or your kid is upstairs running a bittorrent client grabbing the last 3 seasons of Glee.

Link to comment
Share on other sites

Okay it's slow again this morning:

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

 

C:\Documents and Settings\kim Vigil>tracert pnwmas.org

 

Tracing route to pnwmas.org [67.23.230.30]

over a maximum of 30 hops:

 

1 3 ms 1 ms 1 ms 10.0.0.1

2 * * * Request timed out.

3 10 ms 9 ms 9 ms ge-7-1-ur01.troutdale.or.bverton.comcast.net [68

.85.242.229]

4 11 ms 8 ms 9 ms 68.87.218.189

5 14 ms 14 ms 13 ms pos-0-7-0-0-cr01.seattle.wa.ibone.comcast.net [6

8.86.95.89]

6 30 ms 29 ms 29 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]

7 38 ms 35 ms 36 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62]

 

8 66 ms 55 ms 55 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]

9 57 ms 55 ms 55 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]

10 * * * Request timed out.

11 * * 91 ms ae-73-78.ebr3.Dallas1.Level3.net [4.69.146.76]

12 * * * Request timed out.

13 * 101 ms 108 ms ae-73-73.csw2.Atlanta2.Level3.net [4.69.148.254]

 

14 * * * Request timed out.

15 * * * Request timed out.

16 115 ms * * HostDime.com-10G-ethernet.core1.level3.net [67.3

0.140.2]

17 * * * Request timed out.

18 112 ms 111 ms * 67-23-230-30.static.dimenoc.com [67.23.230.30]

19 * * * Request timed out.

20 ^C

Link to comment
Share on other sites

Yep SLOW this am...

 

--- pnwmas.org ping statistics ---

50 packets transmitted, 11 packets received, 78.0% packet loss

round-trip min/avg/max/stddev = 110.361/116.554/125.382/5.636 ms

 

and here is google

--- www.l.google.com ping statistics ---

50 packets transmitted, 50 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 45.621/48.629/51.155/1.040 ms

 

and bulkreefsupply

--- bulkreefsupply.com ping statistics ---

50 packets transmitted, 50 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 14.516/16.191/22.156/1.310 ms

Link to comment
Share on other sites

Still slow here's what I get when I do the ping command

 

Pinging pnwmas.org [67.23.230.30] with 32 bytes of data:

 

Request timed out.

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=125ms TTL=45

Reply from 67.23.230.30: bytes=32 time=115ms TTL=45

Request timed out.

Reply from 67.23.230.30: bytes=32 time=115ms TTL=45

Request timed out.

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=167ms TTL=45

Reply from 67.23.230.30: bytes=32 time=121ms TTL=45

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=125ms TTL=45

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=114ms TTL=45

Request timed out.

Reply from 67.23.230.30: bytes=32 time=114ms TTL=45

Request timed out.

Reply from 67.23.230.30: bytes=32 time=114ms TTL=45

Request timed out.

 

Ping statistics for 67.23.230.30:

Packets: Sent = 23, Received = 9, Lost = 14 (60% loss),

Approximate round trip times in milli-seconds:

Minimum = 114ms, Maximum = 167ms, Average = 123ms

Control-C

^C

Link to comment
Share on other sites

Mine again this morning lost 37 packets out of 50...how do I copy and paste the actual code results from the cmd prompt?

 

If you click on the mini command prompt window in the upper left of the command window you will pop down a menu. Look under the Edit menu - you will use the 'Mark' command and then highlight the text you want to copy and then goto the Edit menu again and choose 'Copy'.

Link to comment
Share on other sites

C:\Users\XrayGuy>ping -n 50 pnwmas.org

 

Pinging pnwmas.org [67.23.230.30] with 32 bytes of data:

Request timed out.

Reply from 67.23.230.30: bytes=32 time=106ms TTL=49

Reply from 67.23.230.30: bytes=32 time=101ms TTL=49

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=96ms TTL=49

Request timed out.

Reply from 67.23.230.30: bytes=32 time=103ms TTL=49

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=99ms TTL=49

Request timed out.

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=106ms TTL=49

Request timed out.

Reply from 67.23.230.30: bytes=32 time=165ms TTL=49

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=95ms TTL=49

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=111ms TTL=49

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=95ms TTL=49

Reply from 67.23.230.30: bytes=32 time=109ms TTL=49

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

 

Ping statistics for 67.23.230.30:

Packets: Sent = 50, Received = 11, Lost = 39 (78% loss),

Approximate round trip times in milli-seconds:

Minimum = 95ms, Maximum = 165ms, Average = 107ms

Link to comment
Share on other sites

Don't understand the least bit of this but..... How do I tell if I lost packets?

 

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

 

C:\Documents and Settings\Mike>tracert pnwmas.org

 

Tracing route to pnwmas.org [67.23.230.30]

over a maximum of 30 hops:

 

1 <1 ms <1 ms <1 ms 192.168.1.1

2 6 ms 6 ms 7 ms 73.93.86.1

3 6 ms 7 ms 8 ms ge-4-30-ur01.longview.wa.bverton.comcast.net [68

.87.216.245]

4 9 ms 10 ms 8 ms te-7-1-ar01.troutdale.or.bverton.comcast.net [68

.87.216.77]

5 14 ms 13 ms 17 ms pos-0-7-0-0-cr01.seattle.wa.ibone.comcast.net [6

8.86.95.89]

6 14 ms 14 ms 13 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]

7 15 ms 17 ms 17 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62]

 

8 61 ms 55 ms 55 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]

9 58 ms 57 ms 67 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]

10 73 ms 72 ms 72 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]

11 61 ms 71 ms 72 ms ae-93-98.ebr3.Dallas1.Level3.net [4.69.146.92]

12 80 ms 81 ms 81 ms ae-43-43.ebr3.Atlanta2.Level3.net [4.69.151.186]

 

13 82 ms 81 ms 81 ms ae-73-73.csw2.Atlanta2.Level3.net [4.69.148.254]

 

14 90 ms 89 ms 90 ms ae-71-71.ebr1.Atlanta2.Level3.net [4.69.148.245]

 

15 93 ms 93 ms 93 ms ae-1-8.bar1.Orlando1.Level3.net [4.69.137.149]

16 250 ms 235 ms 238 ms HostDime.com-10G-ethernet.core1.level3.net [67.3

0.140.2]

17 94 ms 93 ms 94 ms 67-23-230-2.static.dimenoc.com [67.23.230.2]

18 95 ms 95 ms 96 ms 67-23-230-30.static.dimenoc.com [67.23.230.30]

 

Trace complete.

 

C:\Documents and Settings\Mike>

Link to comment
Share on other sites

Don't understand the least bit of this but..... How do I tell if I lost packets?

 

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

 

C:\Documents and Settings\Mike>tracert pnwmas.org

 

Tracing route to pnwmas.org [67.23.230.30]

over a maximum of 30 hops:

 

1

2 6 ms 6 ms 7 ms 73.93.86.1

3 6 ms 7 ms 8 ms ge-4-30-ur01.longview.wa.bverton.comcast.net [68

.87.216.245]

4 9 ms 10 ms 8 ms te-7-1-ar01.troutdale.or.bverton.comcast.net [68

.87.216.77]

5 14 ms 13 ms 17 ms pos-0-7-0-0-cr01.seattle.wa.ibone.comcast.net [6

8.86.95.89]

6 14 ms 14 ms 13 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]

7 15 ms 17 ms 17 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62]

 

8 61 ms 55 ms 55 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]

9 58 ms 57 ms 67 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]

10 73 ms 72 ms 72 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]

11 61 ms 71 ms 72 ms ae-93-98.ebr3.Dallas1.Level3.net [4.69.146.92]

12 80 ms 81 ms 81 ms ae-43-43.ebr3.Atlanta2.Level3.net [4.69.151.186]

 

13 82 ms 81 ms 81 ms ae-73-73.csw2.Atlanta2.Level3.net [4.69.148.254]

 

14 90 ms 89 ms 90 ms ae-71-71.ebr1.Atlanta2.Level3.net [4.69.148.245]

 

15 93 ms 93 ms 93 ms ae-1-8.bar1.Orlando1.Level3.net [4.69.137.149]

16 250 ms 235 ms 238 ms HostDime.com-10G-ethernet.core1.level3.net [67.3

0.140.2]

17 94 ms 93 ms 94 ms 67-23-230-2.static.dimenoc.com [67.23.230.2]

18 95 ms 95 ms 96 ms 67-23-230-30.static.dimenoc.com [67.23.230.30]

 

Trace complete.

 

C:\Documents and Settings\Mike>

 

(laugh) It doesn't make any sense to me either Mike but the packets show up with this command" ping -n 50 pnwmas.org" and hit enter

Link to comment
Share on other sites

Another ping pong

 

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

 

C:\Documents and Settings\kim Vigil>ping -n50 pnwmas.org

Bad value for option -n50, valid range is from 1 to 4294967295.

 

C:\Documents and Settings\kim Vigil>ping -n 50 pnwmas.org

 

Pinging pnwmas.org [67.23.230.30] with 32 bytes of data:

 

Request timed out.

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=110ms TTL=45

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=117ms TTL=45

Request timed out.

Reply from 67.23.230.30: bytes=32 time=115ms TTL=45

Request timed out.

Reply from 67.23.230.30: bytes=32 time=115ms TTL=45

Request timed out.

Reply from 67.23.230.30: bytes=32 time=119ms TTL=45

Request timed out.

Reply from 67.23.230.30: bytes=32 time=114ms TTL=45

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=120ms TTL=45

Request timed out.

Reply from 67.23.230.30: bytes=32 time=119ms TTL=45

Request timed out.

Reply from 67.23.230.30: bytes=32 time=117ms TTL=45

Request timed out.

Request timed out.

Reply from 67.23.230.30: bytes=32 time=123ms TTL=45

Reply from 67.23.230.30: bytes=32 time=117ms TTL=45

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

 

Ping statistics for 67.23.230.30:

Packets: Sent = 32, Received = 11, Lost = 21 (65% loss),

Approximate round trip times in milli-seconds:

Minimum = 110ms, Maximum = 123ms, Average = 116ms

Control-C

^C

C:\Documents and Settings\kim Vigil>

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...