Jump to content

THIS SERVER **** SUCKS


reefnjunkie

Recommended Posts

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?

 

Yes that packet loss is exactly what's causing your 'slowness'.

 

Refreshing actually might make the issue worse because it puts a heavier load on the site to respond to multiple requests from a single user.

Link to comment
Share on other sites

220-server1.pnwmas.org ESMTP Exim 4.69 #1 Fri, 18 Feb 2011 08:40:01 -0800

220-We do not authorize the use of this system to transport unsolicited,

220 and/or bulk e-mail.

 

Microsoft Windows [Version 6.1.7600]

Copyright © 2009 Microsoft Corporation. All rights reserved.

 

C:\Users\XrayGuy>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.

Request timed out.

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.

Request timed out.

Request timed out.

Request timed out.

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

Request timed out.

Request timed out.

Request timed out.

Request timed out.

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

Request timed out.

Request timed out.

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

Request timed out.

Request timed out.

Request timed out.

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

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

Request timed out.

Request timed out.

Request timed out.

Request timed out.

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

Request timed out.

Request timed out.

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

Request timed out.

Request timed out.

Request timed out.

Request timed out.

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

Request timed out.

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

Request timed out.

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

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 = 94ms, Maximum = 106ms, Average = 97ms

Link to comment
Share on other sites

C:\Users\XrayGuy>ping -n 50 google.com

 

Pinging google.com [74.125.53.99] with 32 bytes of data:

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=34ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=35ms TTL=51

Reply from 74.125.53.99: bytes=32 time=34ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=34ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=238ms TTL=51

Reply from 74.125.53.99: bytes=32 time=72ms TTL=51

Reply from 74.125.53.99: bytes=32 time=63ms TTL=51

Reply from 74.125.53.99: bytes=32 time=233ms TTL=51

Reply from 74.125.53.99: bytes=32 time=128ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=34ms TTL=51

Reply from 74.125.53.99: bytes=32 time=35ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=31ms TTL=51

Reply from 74.125.53.99: bytes=32 time=38ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=34ms TTL=51

Reply from 74.125.53.99: bytes=32 time=34ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=35ms TTL=51

Reply from 74.125.53.99: bytes=32 time=44ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=33ms TTL=51

Reply from 74.125.53.99: bytes=32 time=34ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=32ms TTL=51

Reply from 74.125.53.99: bytes=32 time=34ms TTL=51

 

Ping statistics for 74.125.53.99:

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

Approximate round trip times in milli-seconds:

Minimum = 31ms, Maximum = 238ms, Average = 44ms

Link to comment
Share on other sites

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

 

Pinging craigslist.org [208.82.236.129] with 32 bytes of data:

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=196ms TTL=241

Reply from 208.82.236.129: bytes=32 time=76ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=265ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=49ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=50ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=49ms TTL=241

Reply from 208.82.236.129: bytes=32 time=49ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=57ms TTL=241

Reply from 208.82.236.129: bytes=32 time=49ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=49ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=49ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=49ms TTL=241

Reply from 208.82.236.129: bytes=32 time=49ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=49ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=47ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

Reply from 208.82.236.129: bytes=32 time=48ms TTL=241

 

Ping statistics for 208.82.236.129:

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

Approximate round trip times in milli-seconds:

Minimum = 47ms, Maximum = 265ms, Average = 55ms

Link to comment
Share on other sites

I don't know what you all are going on about....I have not had a single issue with the website. It seems to run just fine and dandy anytime of the day or night. Never slow, never misses a beat. Of course I'm running a new iMac with Safari so that could be the answer right there.

 

I'm not too hip on the new vbulletin software and new look of the site however, but that's another thread.

Link to comment
Share on other sites

I don't know what you all are going on about....I have not had a single issue with the website. It seems to run just fine and dandy anytime of the day or night. Never slow, never misses a beat. Of course I'm running a new iMac with Safari so that could be the answer right there.

 

I'm not too hip on the new vbulletin software and new look of the site however, but that's another thread.

 

Way to rub it in Scott! LOL!

Link to comment
Share on other sites

I don't know what you all are going on about....I have not had a single issue with the website. It seems to run just fine and dandy anytime of the day or night. Never slow, never misses a beat. Of course I'm running a new iMac with Safari so that could be the answer right there.

 

I'm not too hip on the new vbulletin software and new look of the site however, but that's another thread.

 

I am running a new Mac too, I think it has something to with the firewall and how our ISP routes us to the server. I have been slow, fast and had tomes I cant get on at all. iPhone slow on forum runner from time to time too!

Link to comment
Share on other sites

can't do a darn thing, waited 5 min for this page to come up... better on my phone right now.

 

 

--- 67.23.230.30 ping statistics ---

50 packets transmitted, 9 packets received, 82.0% packet loss

round-trip min/avg/max/stddev = 112.328/122.145/131.763/6.521 ms

 

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

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

round-trip min/avg/max/stddev = 34.776/38.722/51.658/3.529 ms

 

--- any-fp.wa1.b.yahoo.com ping statistics ---

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

round-trip min/avg/max/stddev = 38.775/50.224/119.374/16.378 ms

Link to comment
Share on other sites

I am running a new Mac too' date=' I think it has something to with the firewall and how our ISP routes us to the server. I have been slow, fast and had tomes I cant get on at all. iPhone slow on forum runner from time to time too![/quote']

 

How to turn off the OSX firewall - http://kb.iu.edu/data/aozg.html

 

Also what make and model of cable modem do you have and what make and model of wireless router do you have (all those funny model #'s please)?

Link to comment
Share on other sites

The crux of the matter is this.....cruising and participating in this forum used to be fun...it's now an aggravation. Just like now...I wanted to read this thread. After spending 3 times as long loading the website amd logging in(aggravation) I had to look at the unfamiliar background template (aggravation)...attempt to read the "GREEN" font color(big aggravation)...I attempted to follow this thread. Every other page loaded in microseconds....every other page took forever.

I dislike aggravations...the hobby itself gives me plenty.....as a result I've only accessed this site 3 times since the changeover....before the changeover it was 3-4 times a day.

Any like minded folks out there?????????????????

Link to comment
Share on other sites

How to turn off the OSX firewall - http://kb.iu.edu/data/aozg.html

 

Also what make and model of cable modem do you have and what make and model of wireless router do you have (all those funny model #'s please)?

 

Now why would I want to turn off my firewall? And that wont help kim, she is in the same boat on a pc.

 

I have a leased cable modem.... Arris Model TM602G/CT

 

wireless modem is a Lynksys wireless g 2.4 GHz with speed booster (ya right!)

Link to comment
Share on other sites

I still zip thru this website like I'm on a T100 line. Back and forth, page to page, anytime day or night, no issues whatsoever. The pages load almost instantly.

I have Comcast broadband, using a Comcast supplied modem and wireless router.

Although I never do on my windoze work peecees, maybe you IE users could empty the history and cache files and see if this helps any.

Link to comment
Share on other sites

Now why would I want to turn off my firewall? And that wont help kim, she is in the same boat on a pc.

 

I have a leased cable modem.... Arris Model TM602G/CT

 

wireless modem is a Lynksys wireless g 2.4 GHz with speed booster (ya right!)

 

I wanted to make sure you were not using a cable modem that had a firewall built-in (doesn't look like it) and then using a wireless router with a firewall (pretty sure yours does - on the bottom does the label say WRT54G?) which can cause issues. If your wireless router has a firewall built-in then your firewall on your laptop is not needed - double firewalls does not double your protection it only doubles the number of points were you need a correct configuration. I don't run any firewall on my home computers except for my main router connected to my cable modem. If you are connecting to a public WiFi spot then, yes, turning on the firewall is a good idea.

Link to comment
Share on other sites

I wanted to make sure you were not using a cable modem that had a firewall built-in (doesn't look like it) and then using a wireless router with a firewall (pretty sure yours does - on the bottom does the label say WRT54G?) which can cause issues. If your wireless router has a firewall built-in then your firewall on your laptop is not needed - double firewalls does not double your protection it only doubles the number of points were you need a correct configuration. I don't run any firewall on my home computers except for my main router connected to my cable modem. If you are connecting to a public WiFi spot then' date=' yes, turning on the firewall is a good idea.[/quote']

 

it has a WRT54GS on it...

Link to comment
Share on other sites

Here are my results after turning my Windows firewall off to test to see if that was the issue...

 

Ping statistics for 67.23.230.30:

Packets: Sent = 50, Received = 14, Lost = 36 (72% loss),

Approximate round trip times in milli-seconds:

Minimum = 95ms, Maximum = 259ms, Average = 110ms

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...