tanktop74 Posted February 18, 2011 Share Posted February 18, 2011 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> Hey Kim, ping google.com to make sure it's not our ISP and post results for that too! Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 18, 2011 Share Posted February 18, 2011 Okay. Here's google I feel like such a computer geek Lol!: Here's the pnwmas: 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 Okay. Here's google I feel like such a computer geek Lol!: ^C C:\Documents and Settings\kim Vigil>ping -n 50 google.com Pinging google.com [74.125.127.104] with 32 bytes of data: Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=38ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=37ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=36ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=36ms TTL=51 Reply from 74.125.127.104: bytes=32 time=36ms TTL=51 Reply from 74.125.127.104: bytes=32 time=36ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=36ms TTL=51 Reply from 74.125.127.104: bytes=32 time=36ms TTL=51 Reply from 74.125.127.104: bytes=32 time=36ms TTL=51 Reply from 74.125.127.104: bytes=32 time=37ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=38ms TTL=51 Reply from 74.125.127.104: bytes=32 time=33ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=36ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=36ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Reply from 74.125.127.104: bytes=32 time=35ms TTL=51 Reply from 74.125.127.104: bytes=32 time=34ms TTL=51 Ping statistics for 74.125.127.104: Packets: Sent = 47, Received = 47, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 33ms, Maximum = 38ms, Average = 35ms Control-C ^C C:\Documents and Settings\kim Vigil> Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 18, 2011 Share Posted February 18, 2011 Pinging without a license! Hey Jackaninny where are you? Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. 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. Reply from 67.23.230.30: bytes=32 time=125ms TTL=45 Request timed out. Request timed out. Request timed out. Reply from 67.23.230.30: bytes=32 time=120ms TTL=45 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=118ms TTL=45 Request timed out. Request timed out. Request timed out. Reply from 67.23.230.30: bytes=32 time=117ms TTL=45 Request timed out. Request timed out. Ping statistics for 67.23.230.30: Packets: Sent = 18, Received = 5, Lost = 13 (72% loss), Approximate round trip times in milli-seconds: Minimum = 111ms, Maximum = 125ms, Average = 118ms Control-C ^C C:\Documents and Settings\kim Vigil> Quote Link to comment Share on other sites More sharing options...
tanktop74 Posted February 18, 2011 Share Posted February 18, 2011 supper freakin slow for me.... PING pnwmas.org (67.23.230.30): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 64 bytes from 67.23.230.30: icmp_seq=3 ttl=45 time=118.842 ms Request timeout for icmp_seq 4 Request timeout for icmp_seq 5 64 bytes from 67.23.230.30: icmp_seq=6 ttl=45 time=113.973 ms Request timeout for icmp_seq 7 Request timeout for icmp_seq 8 Request timeout for icmp_seq 9 Request timeout for icmp_seq 10 Request timeout for icmp_seq 11 Request timeout for icmp_seq 12 Request timeout for icmp_seq 13 Request timeout for icmp_seq 14 Request timeout for icmp_seq 15 Request timeout for icmp_seq 16 Request timeout for icmp_seq 17 64 bytes from 67.23.230.30: icmp_seq=18 ttl=45 time=118.156 ms Request timeout for icmp_seq 19 Request timeout for icmp_seq 20 Request timeout for icmp_seq 21 64 bytes from 67.23.230.30: icmp_seq=22 ttl=45 time=123.406 ms Request timeout for icmp_seq 23 Request timeout for icmp_seq 24 Request timeout for icmp_seq 25 Request timeout for icmp_seq 26 Request timeout for icmp_seq 27 Request timeout for icmp_seq 28 Request timeout for icmp_seq 29 Request timeout for icmp_seq 30 64 bytes from 67.23.230.30: icmp_seq=31 ttl=45 time=112.031 ms Request timeout for icmp_seq 32 64 bytes from 67.23.230.30: icmp_seq=33 ttl=45 time=112.602 ms Request timeout for icmp_seq 34 Request timeout for icmp_seq 35 Request timeout for icmp_seq 36 64 bytes from 67.23.230.30: icmp_seq=37 ttl=45 time=117.250 ms 64 bytes from 67.23.230.30: icmp_seq=38 ttl=45 time=111.628 ms Request timeout for icmp_seq 39 Request timeout for icmp_seq 40 Request timeout for icmp_seq 41 Request timeout for icmp_seq 42 Request timeout for icmp_seq 43 Request timeout for icmp_seq 44 Request timeout for icmp_seq 45 Request timeout for icmp_seq 46 Request timeout for icmp_seq 47 Request timeout for icmp_seq 48 --- pnwmas.org ping statistics --- 50 packets transmitted, 8 packets received, 84.0% packet loss round-trip min/avg/max/stddev = 111.628/115.986/123.406/3.867 ms and just for comparison... --- www.l.google.com ping statistics --- 50 packets transmitted, 50 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 32.479/34.091/43.017/1.460 ms Quote Link to comment Share on other sites More sharing options...
lewisriverfisherman Posted February 18, 2011 Share Posted February 18, 2011 I guess i am not really understanding why one day this site works OK and then the next it is slow, and slow for almost a week. Then some things got tweaked and the site works for almost a full day(clap) and then it is back to being really slow again(scratch). Really Im not trying to complain about the problems but I am just puzzled. My hat goes off the the members that are working on this site to make it fast agian(rock2)(rock2)(rock2). I guess I needed to vent a little. Your Truely Frustrated Reef Keeper Quote Link to comment Share on other sites More sharing options...
AC-k3v Posted February 18, 2011 Share Posted February 18, 2011 Has anybody sent this info to the hosting company? How many modifications have been made to the vBulletin? What version of MySQL is being used? I have issues here from time to time. Mostly slow response. I just chalked it off as a hosting issue. edit: it took about 15 seconds for me to post the above after hitting submit post. Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 18, 2011 Share Posted February 18, 2011 Has anybody sent this info to the hosting company? How many modifications have been made to the vBulletin? What version of MySQL is being used? I have issues here from time to time. Mostly slow response. I just chalked it off as a hosting issue. edit: it took about 15 seconds for me to post the above after hitting submit post. Kevin, you're not even speaking my language. I also do not get why it works well and then doesn't. I only learned what pinging was and I kinda get the whole packet receiving thing. Jackaninny seems to be the most on top of this and I think he did send the info to the hosting company. Quote Link to comment Share on other sites More sharing options...
jackaninny Posted February 18, 2011 Share Posted February 18, 2011 Yes I have had a ticket open with the hosting company since the start of this thread. Just got home and updated the ticket to show the difference between pnwmas.org and google.com and asking to have it escalated to the next level support. Quote Link to comment Share on other sites More sharing options...
AC-k3v Posted February 18, 2011 Share Posted February 18, 2011 Kevin' date=' you're not even speaking my language. I also do not get why it works well and then doesn't. I only learned what pinging was and I kinda get the whole packet receiving thing. Jackaninny seems to be the most on top of this and I think he did send the info to the hosting company.[/quote'] Sorry, The hosting company for this site is HostDime. HostDime's servers could be overloaded. Bandwidth issues? vBulletin is the forum software PNWMAS uses. Mods can be many things. skins, facebook integration, as well as back-end add-ons for the staff. On one of my sites, i get an email every time two members log on with the same IP address. MySQL is just a database management system that is commonly used for vBulletin forums. Kevin Quote Link to comment Share on other sites More sharing options...
jackaninny Posted February 18, 2011 Share Posted February 18, 2011 Sorry, The hosting company for this site is HostDime. HostDime's servers could be overloaded. Bandwidth issues? vBulletin is the forum software PNWMAS uses. Mods can be many things. skins, facebook integration, as well as back-end add-ons for the staff. On one of my sites, i get an email every time two members log on with the same IP address. MySQL is just a database management system that is commonly used for vBulletin forums. Kevin If it was a overloaded bandwidth issue I'd expect to see MORE people experiencing the issue and we are not - in fact I'm currently seeing no packet loss at all and 99% of the time the site looks fine to me. I have noticed that Comcast has Beth/Kim's traffic taking a different path to our host so I'm thinking it's an issue along a particular segment. Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 18, 2011 Share Posted February 18, 2011 Sorry, The hosting company for this site is HostDime. HostDime's servers could be overloaded. Bandwidth issues? vBulletin is the forum software PNWMAS uses. Mods can be many things. skins, facebook integration, as well as back-end add-ons for the staff. On one of my sites, i get an email every time two members log on with the same IP address. MySQL is just a database management system that is commonly used for vBulletin forums. Kevin Thanks! It is all making a little more sense to me. I feel like I have entered a subforum of computer geeks (laugh) Should we call it the Pacific Northwest Marine Aquarium Socieity and Computer Nerd subforum pnwmascns! Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 18, 2011 Share Posted February 18, 2011 Okay here's another trace So Marcus why does it work well for a day and then stop working? Here's another trace. I also have a phone call in to Mark Zuckerberg:D 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 11 ms 13 ms 9 ms ge-7-1-ur01.troutdale.or.bverton.comcast.net [68 .85.242.229] 4 12 ms 11 ms 8 ms 68.87.218.189 5 17 ms 14 ms 15 ms pos-0-7-0-0-cr01.seattle.wa.ibone.comcast.net [6 8.86.95.89] 6 31 ms 30 ms 31 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109] 7 32 ms 34 ms 36 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62] 8 67 ms 71 ms 56 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54] 9 62 ms 69 ms 72 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37] 10 * * * Request timed out. 11 81 ms 88 ms * ae-73-78.ebr3.Dallas1.Level3.net [4.69.146.76] 12 * 109 ms * ae-41-41.ebr3.Atlanta2.Level3.net [4.69.151.178] 13 * 118 ms * ae-73-73.csw2.Atlanta2.Level3.net [4.69.148.254] 14 * * * Request timed out. 15 * * 117 ms ae-1-8.bar1.Orlando1.Level3.net [4.69.137.149] 16 * * * Request timed out. 17 114 ms * * 67-23-230-2.static.dimenoc.com [67.23.230.2] 18 * * * Request timed out. 19 115 ms * * 67-23-230-30.static.dimenoc.com [67.23.230.30] 20 ^C Quote Link to comment Share on other sites More sharing options...
AC-k3v Posted February 18, 2011 Share Posted February 18, 2011 Here are a couple things to look into: http://www.vbulletin.org/forum/showthread.php?t=237025 http://articles.digitalpoint.com/content.php?r=7-Optimize-vBulletin-4 Edit: forums are running fast for me right now. Quote Link to comment Share on other sites More sharing options...
AC-k3v Posted February 18, 2011 Share Posted February 18, 2011 Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Aloha Corals>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 21 ms 12 ms 42 ms cpe-98-155-148-1.hawaii.res.rr.com [98.155.148.1] 3 90 ms 25 ms 11 ms ge-5-1-9-oahuhiqeen-rtr1.hawaii.rr.com [24.25.224.209] 4 14 ms 14 ms 14 ms te0-1-0-7-oahuhimili-rtr2.hawaii.rr.com [24.25.229.241] 5 74 ms 71 ms 72 ms te0-3-0-3-tustca1-rtr3.socal.rr.com [24.25.229.162] 6 72 ms 76 ms 72 ms BE25-tustca1-rtr1.socal.rr.com [66.75.161.50] 7 70 ms 66 ms 67 ms ae-6-0.cr0.lax30.tbone.rr.com [66.109.6.214] 8 97 ms 74 ms 97 ms ae-1-0.pr0.lax00.tbone.rr.com [66.109.6.129] 9 67 ms 69 ms 69 ms xe-8-1-0.edge1.LosAngeles6.Level3.net [4.26.0.17] 10 74 ms 74 ms 75 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190] 11 70 ms 73 ms 74 ms ae-82-82.ebr2.LosAngeles1.Level3.net [4.69.137.25] 12 112 ms 113 ms 106 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78] 13 125 ms 124 ms 142 ms ae-42-42.ebr3.Atlanta2.Level3.net [4.69.151.182] 14 120 ms 119 ms 121 ms ae-63-63.csw1.Atlanta2.Level3.net [4.69.148.242] 15 128 ms 125 ms 125 ms ae-61-61.ebr1.Atlanta2.Level3.net [4.69.148.233] 16 133 ms 132 ms 133 ms ae-1-8.bar1.Orlando1.Level3.net [4.69.137.149] 17 312 ms 223 ms 206 ms HostDime.com-10G-ethernet.core1.level3.net [67.30.140.2] 18 156 ms 140 ms 138 ms 67-23-230-2.static.dimenoc.com [67.23.230.2] 19 140 ms 142 ms 136 ms 67-23-230-30.static.dimenoc.com [67.23.230.30] Trace complete. Quote Link to comment Share on other sites More sharing options...
AC-k3v Posted February 18, 2011 Share Posted February 18, 2011 C:\Users\Aloha Corals>ping pnwmas.org Pinging pnwmas.org [67.23.230.30] with 32 bytes of data: Reply from 67.23.230.30: bytes=32 time=140ms TTL=45 Reply from 67.23.230.30: bytes=32 time=137ms TTL=45 Reply from 67.23.230.30: bytes=32 time=137ms TTL=45 Reply from 67.23.230.30: bytes=32 time=138ms TTL=45 Ping statistics for 67.23.230.30: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 137ms, Maximum = 140ms, Average = 138ms Quote Link to comment Share on other sites More sharing options...
jackaninny Posted February 18, 2011 Share Posted February 18, 2011 Kim/Beth- Please try these two commands and post results: 1) telnet pnwmas.org 25 2) ping 67.23.230.30 The first one you will probably have to let it timeout but post what you first get when/if it connects. Thanks. Quote Link to comment Share on other sites More sharing options...
jackaninny Posted February 18, 2011 Share Posted February 18, 2011 BTW - Is anyone else seeing slowness right now - 11:13pm - I'm humming along and just wanted to make sure the issue didn't go away suddenly. Quote Link to comment Share on other sites More sharing options...
cschwarz Posted February 18, 2011 Share Posted February 18, 2011 its so so slow lol i am falling a sleep lol. took my 10 minuets to lode the page. Quote Link to comment Share on other sites More sharing options...
jackaninny Posted February 18, 2011 Share Posted February 18, 2011 its so so slow lol i am falling a sleep lol. took my 10 minuets to lode the page. ping pnwmas.org? ping google.com? tracert pnwmas.org? Quote Link to comment Share on other sites More sharing options...
XrayGuy Posted February 18, 2011 Share Posted February 18, 2011 Microsoft Windows [Version 6.1.7600] Copyright © 2009 Microsoft Corporation. All rights reserved. C:\Users\XrayGuy>telnet pnwmas.org 25 'telnet' is not recognized as an internal or external command, operable program or batch file. C:\Users\XrayGuy>ping 67.23.230.30 Pinging 67.23.230.30 with 32 bytes of data: Request timed out. Reply from 67.23.230.30: bytes=32 time=96ms TTL=49 Request timed out. Request timed out. Ping statistics for 67.23.230.30: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss), Approximate round trip times in milli-seconds: Minimum = 96ms, Maximum = 96ms, Average = 96ms C:\Users\XrayGuy> Quote Link to comment Share on other sites More sharing options...
XrayGuy Posted February 18, 2011 Share Posted February 18, 2011 C:\Users\XrayGuy>ping -n 50 pnwmas.org Pinging pnwmas.org [67.23.230.30] with 32 bytes of data: Reply from 67.23.230.30: bytes=32 time=104ms TTL=49 Reply from 67.23.230.30: bytes=32 time=97ms TTL=49 Request timed out. Reply from 67.23.230.30: bytes=32 time=101ms TTL=49 Request timed out. Reply from 67.23.230.30: bytes=32 time=105ms TTL=49 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 67.23.230.30: bytes=32 time=108ms TTL=49 Request timed out. Reply from 67.23.230.30: bytes=32 time=97ms TTL=49 Request timed out. Request timed out. 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=96ms 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. Reply from 67.23.230.30: bytes=32 time=107ms TTL=49 Request timed out. Reply from 67.23.230.30: bytes=32 time=94ms TTL=49 Reply from 67.23.230.30: bytes=32 time=94ms TTL=49 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=107ms TTL=49 Request timed out. Request timed out. Request timed out. Reply from 67.23.230.30: bytes=32 time=97ms TTL=49 Ping statistics for 67.23.230.30: Packets: Sent = 50, Received = 13, Lost = 37 (74% loss), Approximate round trip times in milli-seconds: Minimum = 94ms, Maximum = 108ms, Average = 101ms Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 18, 2011 Share Posted February 18, 2011 Kim/Beth- Please try these two commands and post results: 1) telnet pnwmas.org 25 2) ping 67.23.230.30 The first one you will probably have to let it timeout but post what you first get when/if it connects. Thanks. Okay marcus this is what I get and site very slow. 1. 220-server1.pnwmas.org ESMTP Exim 4.69 #1 Fri, 18 Feb 2011 01:44:04 -0800 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail. 2.Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\kim Vigil>ping 67.23.230.30 Pinging 67.23.230.30 with 32 bytes of data: Request timed out. Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=115ms TTL=45 Reply from 67.23.230.30: bytes=32 time=127ms TTL=45 Ping statistics for 67.23.230.30: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 111ms, Maximum = 127ms, Average = 117ms C:\Documents and Settings\kim Vigil> Quote Link to comment Share on other sites More sharing options...
jackaninny Posted February 18, 2011 Share Posted February 18, 2011 Microsoft Windows [Version 6.1.7600] Copyright © 2009 Microsoft Corporation. All rights reserved. C:\Users\XrayGuy>telnet pnwmas.org 25 'telnet' is not recognized as an internal or external command, operable program or batch file. C:\Users\XrayGuy>ping 67.23.230.30 Pinging 67.23.230.30 with 32 bytes of data: Request timed out. Reply from 67.23.230.30: bytes=32 time=96ms TTL=49 Request timed out. Request timed out. Ping statistics for 67.23.230.30: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss), Approximate round trip times in milli-seconds: Minimum = 96ms, Maximum = 96ms, Average = 96ms C:\Users\XrayGuy> XRay- Looks like you are running Windows7 and probably need to enable telnet first: http://www.blogsdna.com/4052/how-to-install-microsoft-telnet-client-on-windows-7.htm Quote Link to comment Share on other sites More sharing options...
cklskypilot Posted February 18, 2011 Share Posted February 18, 2011 LOOKS LIKE IS RUNNING GOOD THIS MORNING. Quote Link to comment Share on other sites More sharing options...
tanktop74 Posted February 18, 2011 Share Posted February 18, 2011 Kim/Beth- Please try these two commands and post results: 1) telnet pnwmas.org 25 2) ping 67.23.230.30 The first one you will probably have to let it timeout but post what you first get when/if it connects. Thanks. telnet pnwmas.org 25 Trying 67.23.230.30... Connected to pnwmas.org. Escape character is '^]'. 220-server1.pnwmas.org ESMTP Exim 4.69 #1 Fri, 18 Feb 2011 06:46:47 -0800 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail. 421 server1.pnwmas.org: SMTP command timeout - closing connection Connection closed by foreign host. --- 67.23.230.30 ping statistics --- 50 packets transmitted, 6 packets received, 88.0% packet loss round-trip min/avg/max/stddev = 113.250/118.735/129.254/6.543 ms BTW, it took like 10 refreshes to get this page to come up, is that due the the packet loss? What I can figure in my head is that if I continue to refresh I will finally "catch" a packet and the page will load, am I kinda understanding? Anything else I can do? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.