Help - Search - Members - Calendar
Full Version: 36% Packet Loss
Hostony Board > General Support > General Support
steve_d555
Mar 19 2005, 03:28 AM
Hi,
My domain is silentlink.com and I have been getting pretty shoddy connections. Could it be because its a 70.* server? Should I switch? My friends are asking why my site doesnt work sometimes, and I have no idea.

Thanks,
--Steve

CODE
PING 70.84.130.28 (70.84.130.28) 56(84) bytes of data.
64 bytes from 70.84.130.28: icmp_seq=1 ttl=48 time=66.8 ms
64 bytes from 70.84.130.28: icmp_seq=4 ttl=48 time=65.8 ms
64 bytes from 70.84.130.28: icmp_seq=6 ttl=48 time=65.4 ms
64 bytes from 70.84.130.28: icmp_seq=7 ttl=48 time=66.6 ms
64 bytes from 70.84.130.28: icmp_seq=8 ttl=48 time=66.9 ms
64 bytes from 70.84.130.28: icmp_seq=9 ttl=48 time=67.5 ms
64 bytes from 70.84.130.28: icmp_seq=10 ttl=47 time=67.2 ms
64 bytes from 70.84.130.28: icmp_seq=11 ttl=48 time=68.8 ms
64 bytes from 70.84.130.28: icmp_seq=15 ttl=48 time=63.8 ms
64 bytes from 70.84.130.28: icmp_seq=17 ttl=47 time=65.2 ms
64 bytes from 70.84.130.28: icmp_seq=18 ttl=48 time=66.7 ms
64 bytes from 70.84.130.28: icmp_seq=21 ttl=48 time=71.8 ms
64 bytes from 70.84.130.28: icmp_seq=22 ttl=47 time=67.4 ms
64 bytes from 70.84.130.28: icmp_seq=24 ttl=48 time=66.3 ms
64 bytes from 70.84.130.28: icmp_seq=26 ttl=48 time=68.7 ms
64 bytes from 70.84.130.28: icmp_seq=27 ttl=48 time=65.6 ms
64 bytes from 70.84.130.28: icmp_seq=30 ttl=47 time=66.3 ms
64 bytes from 70.84.130.28: icmp_seq=31 ttl=48 time=64.6 ms
64 bytes from 70.84.130.28: icmp_seq=32 ttl=47 time=65.8 ms
64 bytes from 70.84.130.28: icmp_seq=33 ttl=48 time=67.9 ms
64 bytes from 70.84.130.28: icmp_seq=34 ttl=47 time=68.6 ms
64 bytes from 70.84.130.28: icmp_seq=35 ttl=47 time=65.1 ms
64 bytes from 70.84.130.28: icmp_seq=36 ttl=47 time=67.4 ms
64 bytes from 70.84.130.28: icmp_seq=37 ttl=47 time=66.1 ms
64 bytes from 70.84.130.28: icmp_seq=38 ttl=48 time=65.6 ms
64 bytes from 70.84.130.28: icmp_seq=39 ttl=48 time=67.7 ms
64 bytes from 70.84.130.28: icmp_seq=42 ttl=48 time=64.0 ms
64 bytes from 70.84.130.28: icmp_seq=45 ttl=48 time=68.0 ms
64 bytes from 70.84.130.28: icmp_seq=47 ttl=48 time=64.7 ms
64 bytes from 70.84.130.28: icmp_seq=50 ttl=48 time=72.3 ms
64 bytes from 70.84.130.28: icmp_seq=51 ttl=48 time=67.6 ms
64 bytes from 70.84.130.28: icmp_seq=52 ttl=48 time=64.1 ms
64 bytes from 70.84.130.28: icmp_seq=54 ttl=47 time=65.9 ms
64 bytes from 70.84.130.28: icmp_seq=55 ttl=48 time=67.2 ms
64 bytes from 70.84.130.28: icmp_seq=56 ttl=48 time=68.4 ms
64 bytes from 70.84.130.28: icmp_seq=58 ttl=48 time=66.8 ms
64 bytes from 70.84.130.28: icmp_seq=59 ttl=47 time=65.4 ms
64 bytes from 70.84.130.28: icmp_seq=60 ttl=48 time=66.3 ms
64 bytes from 70.84.130.28: icmp_seq=62 ttl=47 time=64.7 ms
64 bytes from 70.84.130.28: icmp_seq=64 ttl=48 time=65.8 ms
64 bytes from 70.84.130.28: icmp_seq=65 ttl=47 time=66.9 ms
64 bytes from 70.84.130.28: icmp_seq=66 ttl=47 time=67.3 ms

--- 70.84.130.28 ping statistics ---
66 packets transmitted, 42 received, 36% packet loss, time 65146ms
rtt min/avg/max/mdev = 63.851/66.737/72.330/1.748 ms
ryanmills
Mar 19 2005, 03:35 AM
welcome to my world... I get the same thing... I was told to change my email password... rolleyes.gif funny it did not work... unsure.gif
steve_d555
Mar 19 2005, 04:39 AM
QUOTE(ryanmills @ Mar 18 2005, 11:35 PM)
welcome to my world... I get the same thing... I was told to change my email password... rolleyes.gif funny it did not work... unsure.gif
*


How would that work, lol. When my month im probably taking my backups and going.
Lehrer
Mar 19 2005, 04:50 AM
Dear Ladies and Gentlemen, hereby I attach the latest update of server 30:

Pinging 70.84.130.28 with 32 bytes of data:

Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time=1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62
Reply from 70.84.130.28: bytes=32 time=1ms TTL=62
Reply from 70.84.130.28: bytes=32 time<1ms TTL=62

Ping statistics for 70.84.130.28:
Packets: Sent = 37, Received = 37, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms


I hope you liked it.
ryanmills
Mar 19 2005, 04:57 AM
I am on the same server and I get 40-50 packet loss


QUOTE
Microsoft Windows XP [Version 5.1.2600]© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\admin>ping 70.84.130.28 -n 20

Pinging 70.84.130.28 with 32 bytes of data:

Reply from 70.84.130.28: bytes=32 time=111ms TTL=47
Reply from 70.84.130.28: bytes=32 time=96ms TTL=48
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=107ms TTL=47
Reply from 70.84.130.28: bytes=32 time=96ms TTL=46
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=104ms TTL=47
Reply from 70.84.130.28: bytes=32 time=99ms TTL=47
Reply from 70.84.130.28: bytes=32 time=96ms TTL=46
Reply from 70.84.130.28: bytes=32 time=95ms TTL=47
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=104ms TTL=46
Reply from 70.84.130.28: bytes=32 time=96ms TTL=48
Request timed out.
Request timed out.

Ping statistics for 70.84.130.28:
    Packets: Sent = 20, Received = 10, Lost = 10 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 95ms, Maximum = 111ms, Average = 100ms



Just for kicks lets try it one more time... (i dont wanna here that "it was rebooting" line) I have been seeing this for 2 days now. Thou I will say the rest of the stats on the server looks really good. I just wish I could access it.



wow moving on up to 53% loss
QUOTE
Microsoft Windows XP [Version 5.1.2600]© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\admin>ping 70.84.130.28 -n 20

Pinging 70.84.130.28 with 32 bytes of data:

Reply from 70.84.130.28: bytes=32 time=111ms TTL=47
Reply from 70.84.130.28: bytes=32 time=96ms TTL=48
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=107ms TTL=47
Reply from 70.84.130.28: bytes=32 time=96ms TTL=46
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=104ms TTL=47
Reply from 70.84.130.28: bytes=32 time=99ms TTL=47
Reply from 70.84.130.28: bytes=32 time=96ms TTL=46
Reply from 70.84.130.28: bytes=32 time=95ms TTL=47
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=104ms TTL=46
Reply from 70.84.130.28: bytes=32 time=96ms TTL=48
Request timed out.
Request timed out.

Ping statistics for 70.84.130.28:
    Packets: Sent = 20, Received = 10, Lost = 10 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 95ms, Maximum = 111ms, Average = 100ms

C:\Documents and Settings\admin>




steve_d555 did you just have your site moved from a diffrent server? I had mine moved two days ago and I have been seeing this since. I can barly check my email it takes 10 try to get all 8 accounts. FTP is pointless since it times out after almost every file


Just as so not to be un-fair I will ping my old Hostony server plus both Hostony DNS servers

QUOTE
Microsoft Windows XP [Version 5.1.2600]© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\admin>ping 70.84.105.196 -n 40

Pinging 70.84.105.196 with 32 bytes of data:

Reply from 70.84.105.196: bytes=32 time=105ms TTL=47
Reply from 70.84.105.196: bytes=32 time=97ms TTL=48
Reply from 70.84.105.196: bytes=32 time=94ms TTL=46
Reply from 70.84.105.196: bytes=32 time=96ms TTL=48
Reply from 70.84.105.196: bytes=32 time=98ms TTL=46
Reply from 70.84.105.196: bytes=32 time=95ms TTL=48
Reply from 70.84.105.196: bytes=32 time=96ms TTL=47
Reply from 70.84.105.196: bytes=32 time=95ms TTL=46
Reply from 70.84.105.196: bytes=32 time=96ms TTL=48
Reply from 70.84.105.196: bytes=32 time=98ms TTL=47
Reply from 70.84.105.196: bytes=32 time=96ms TTL=47
Reply from 70.84.105.196: bytes=32 time=94ms TTL=47
Reply from 70.84.105.196: bytes=32 time=96ms TTL=46
Reply from 70.84.105.196: bytes=32 time=95ms TTL=47
Reply from 70.84.105.196: bytes=32 time=95ms TTL=46
Reply from 70.84.105.196: bytes=32 time=94ms TTL=47
Reply from 70.84.105.196: bytes=32 time=98ms TTL=46
Reply from 70.84.105.196: bytes=32 time=95ms TTL=48
Reply from 70.84.105.196: bytes=32 time=97ms TTL=48
Reply from 70.84.105.196: bytes=32 time=98ms TTL=46
Reply from 70.84.105.196: bytes=32 time=97ms TTL=47
Reply from 70.84.105.196: bytes=32 time=95ms TTL=47
Reply from 70.84.105.196: bytes=32 time=100ms TTL=47
Reply from 70.84.105.196: bytes=32 time=97ms TTL=48
Reply from 70.84.105.196: bytes=32 time=96ms TTL=48
Reply from 70.84.105.196: bytes=32 time=99ms TTL=46
Reply from 70.84.105.196: bytes=32 time=95ms TTL=48
Reply from 70.84.105.196: bytes=32 time=98ms TTL=47
Reply from 70.84.105.196: bytes=32 time=96ms TTL=48
Reply from 70.84.105.196: bytes=32 time=97ms TTL=46
Reply from 70.84.105.196: bytes=32 time=95ms TTL=48
Reply from 70.84.105.196: bytes=32 time=97ms TTL=46
Reply from 70.84.105.196: bytes=32 time=97ms TTL=47
Reply from 70.84.105.196: bytes=32 time=99ms TTL=48
Reply from 70.84.105.196: bytes=32 time=96ms TTL=46
Reply from 70.84.105.196: bytes=32 time=96ms TTL=48
Reply from 70.84.105.196: bytes=32 time=97ms TTL=46
Reply from 70.84.105.196: bytes=32 time=97ms TTL=48
Reply from 70.84.105.196: bytes=32 time=99ms TTL=47
Reply from 70.84.105.196: bytes=32 time=96ms TTL=46

Ping statistics for 70.84.105.196:
    Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 94ms, Maximum = 105ms, Average = 96ms

C:\Documents and Settings\admin>ping DNS.HOSTONY.COM -n 40

Pinging DNS.HOSTONY.COM [67.15.111.43] with 32 bytes of data:

Reply from 67.15.111.43: bytes=32 time=87ms TTL=49
Reply from 67.15.111.43: bytes=32 time=90ms TTL=49
Reply from 67.15.111.43: bytes=32 time=91ms TTL=49
Reply from 67.15.111.43: bytes=32 time=88ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=91ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=90ms TTL=49
Reply from 67.15.111.43: bytes=32 time=90ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=88ms TTL=49
Reply from 67.15.111.43: bytes=32 time=91ms TTL=49
Reply from 67.15.111.43: bytes=32 time=91ms TTL=49
Reply from 67.15.111.43: bytes=32 time=91ms TTL=49
Reply from 67.15.111.43: bytes=32 time=90ms TTL=49
Reply from 67.15.111.43: bytes=32 time=90ms TTL=49
Reply from 67.15.111.43: bytes=32 time=90ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=88ms TTL=49
Reply from 67.15.111.43: bytes=32 time=91ms TTL=49
Reply from 67.15.111.43: bytes=32 time=90ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=91ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=90ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=88ms TTL=49
Reply from 67.15.111.43: bytes=32 time=94ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=90ms TTL=49
Reply from 67.15.111.43: bytes=32 time=88ms TTL=49
Reply from 67.15.111.43: bytes=32 time=88ms TTL=49
Reply from 67.15.111.43: bytes=32 time=89ms TTL=49
Reply from 67.15.111.43: bytes=32 time=90ms TTL=49

Ping statistics for 67.15.111.43:
    Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 87ms, Maximum = 94ms, Average = 89ms

C:\Documents and Settings\admin>ping DNS.HOSTONY.ORG -n 40

Pinging DNS.HOSTONY.ORG [67.19.102.93] with 32 bytes of data:

Reply from 67.19.102.93: bytes=32 time=95ms TTL=46
Reply from 67.19.102.93: bytes=32 time=105ms TTL=47
Reply from 67.19.102.93: bytes=32 time=95ms TTL=46
Reply from 67.19.102.93: bytes=32 time=96ms TTL=47
Reply from 67.19.102.93: bytes=32 time=94ms TTL=47
Reply from 67.19.102.93: bytes=32 time=97ms TTL=48
Reply from 67.19.102.93: bytes=32 time=95ms TTL=47
Reply from 67.19.102.93: bytes=32 time=96ms TTL=47
Reply from 67.19.102.93: bytes=32 time=112ms TTL=46
Reply from 67.19.102.93: bytes=32 time=94ms TTL=47
Reply from 67.19.102.93: bytes=32 time=97ms TTL=47
Reply from 67.19.102.93: bytes=32 time=95ms TTL=46
Reply from 67.19.102.93: bytes=32 time=97ms TTL=48
Reply from 67.19.102.93: bytes=32 time=97ms TTL=48
Reply from 67.19.102.93: bytes=32 time=97ms TTL=46
Reply from 67.19.102.93: bytes=32 time=95ms TTL=48
Reply from 67.19.102.93: bytes=32 time=99ms TTL=46
Reply from 67.19.102.93: bytes=32 time=99ms TTL=48
Reply from 67.19.102.93: bytes=32 time=95ms TTL=47
Reply from 67.19.102.93: bytes=32 time=96ms TTL=46
Reply from 67.19.102.93: bytes=32 time=99ms TTL=47
Reply from 67.19.102.93: bytes=32 time=95ms TTL=48
Reply from 67.19.102.93: bytes=32 time=97ms TTL=48
Reply from 67.19.102.93: bytes=32 time=97ms TTL=47
Reply from 67.19.102.93: bytes=32 time=97ms TTL=48
Reply from 67.19.102.93: bytes=32 time=96ms TTL=46
Reply from 67.19.102.93: bytes=32 time=94ms TTL=47
Reply from 67.19.102.93: bytes=32 time=95ms TTL=46
Reply from 67.19.102.93: bytes=32 time=96ms TTL=48
Reply from 67.19.102.93: bytes=32 time=96ms TTL=46
Reply from 67.19.102.93: bytes=32 time=97ms TTL=48
Reply from 67.19.102.93: bytes=32 time=98ms TTL=46
Reply from 67.19.102.93: bytes=32 time=95ms TTL=46
Reply from 67.19.102.93: bytes=32 time=97ms TTL=47
Reply from 67.19.102.93: bytes=32 time=95ms TTL=46
Reply from 67.19.102.93: bytes=32 time=98ms TTL=48
Reply from 67.19.102.93: bytes=32 time=99ms TTL=47
Reply from 67.19.102.93: bytes=32 time=98ms TTL=48
Reply from 67.19.102.93: bytes=32 time=95ms TTL=48
Reply from 67.19.102.93: bytes=32 time=98ms TTL=47

Ping statistics for 67.19.102.93:
    Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 94ms, Maximum = 112ms, Average = 96ms

Umm thous seem fine...



Whats even better is that not everyone has this issue. I had a few friends and my ISP do the same thing. My ISP (who is on a OC line) got the same thing plus a friend who uses comcast in cali but someone in canada and north dakota both got zero... so im at a loss as to wtf is going on. All I know is at this point its costing me to much money... I gave them 48 hours to figure it out after getting the run-around. I opened a new account with a diffrent host. I'm going to test a few sites there and if this is not fixed (maybe it cant be) and the other testing goes well I'm gone.
ryanmills
Mar 19 2005, 05:04 AM
Lehrer from my stand point as a user your post more or less called us wrong. I would do your home work a bit before you post again. You may not be seeing the issue for what ever reason. But some of us are...


So Ladies and Gentlemen, hereby I attach the latest update of server 30:

from dnsstuff.com since I can only run four at a time I will post a few trys of it...

CODE
Pinging 70.84.130.28 [70.84.130.28]:

Ping #1: * [No response]
Ping #2: * [No response]
Ping #3: Got reply from 70.84.130.28 in 56ms [TTL=49]
Ping #4: Got reply from 70.84.130.28 in 55ms [TTL=49]

Done pinging 70.84.130.28!




Pinging 70.84.130.28 [70.84.130.28]:

Ping #1: Got reply from 70.84.130.28 in 55ms [TTL=49]
Ping #2: * [No response]
Ping #3: * [No response]
Ping #4: Got reply from 70.84.130.28 in 71ms [TTL=49]

Done pinging 70.84.130.28!

(to do an IPv6 ping for a domain name, add a ':' before the domain name)




Pinging 70.84.130.28 [70.84.130.28]:

Ping #1: * [No response]
Ping #2: * [No response]
Ping #3: * [No response]
Ping #4: * [No response]

Done pinging 70.84.130.28!

(to do an IPv6 ping for a domain name, add a ':' before the domain name)




Pinging 70.84.130.28 [70.84.130.28]:

Ping #1: * [No response]
Ping #2: * [No response]
Ping #3: Got reply from 70.84.130.28 in 57ms [TTL=49]
Ping #4: Got reply from 70.84.130.28 in 55ms [TTL=49]

Done pinging 70.84.130.28!

(to do an IPv6 ping for a domain name, add a ':' before the domain name)





Pinging 70.84.130.28 [70.84.130.28]:

Ping #1: Got reply from 70.84.130.28 in 55ms [TTL=49]
Ping #2: Got reply from 70.84.130.28 in 54ms [TTL=49]
Ping #3: Got reply from 70.84.130.28 in 55ms [TTL=49]
Ping #4: Got reply from 70.84.130.28 in 55ms [TTL=49]

Done pinging 70.84.130.28!

(to do an IPv6 ping for a domain name, add a ':' before the domain name)




Pinging 70.84.130.28 [70.84.130.28]:

Ping #1: Got reply from 70.84.130.28 in 56ms [TTL=49]
Ping #2: Got reply from 70.84.130.28 in 58ms [TTL=49]
Ping #3: * [No response]
Ping #4: Got reply from 70.84.130.28 in 55ms [TTL=49]

Done pinging 70.84.130.28!

(to do an IPv6 ping for a domain name, add a ':' before the domain name)




Pinging 70.84.130.28 [70.84.130.28]:

Ping #1: * [No response]
Ping #2: * [No response]
Ping #3: * [No response]
Ping #4: * [No response]

Done pinging 70.84.130.28!

(to do an IPv6 ping for a domain name, add a ':' before the domain name)



seems like a issue to me.... and yes I already have a trouble ticket open... its been open for 48 hours and its still not fixed. I'm posting here in hopes that someone else might have a clue...
steve_d555
Mar 19 2005, 05:48 AM
Same here, it just seems to randomly drop packets. It could be our ISPs or shoddy networking. Either way, do you think I could switch my server to a different, maybe better one?
ryanmills
Mar 19 2005, 05:50 AM
I would open a trouble ticket and ask them for a move. Thou I wonder how many people on server30 even know about the issue. I know for sure comcast users will see the same thing...
steve_d555
Mar 19 2005, 06:02 AM
Same with Verizon...
ryanmills
Mar 19 2005, 06:33 AM
at least they are not big ISP's or anything... *rolls eyes*
ryanmills
Mar 19 2005, 06:46 AM
you can also add "sympatico" to the list...
steve_d555
Mar 19 2005, 07:04 AM
And your positive this happened when you switched to Server 30 from the other one?
Alexandre
Mar 19 2005, 07:51 AM
Hi steve_d55,
smile.gif
Give me please your remote IP address.
ryanmills
Mar 19 2005, 08:47 AM
QUOTE(steve_d555 @ Mar 19 2005, 07:04 AM)
And your positive this happened when you switched to Server 30 from the other one?
*



Yea its only server 30 as far as I can tell I can ping my old server 70.84.105.196 with out a issue no packet loss at all. I had them move me becuse the server was just overloaded... figures the sats look good on 30. They are going to move my account again. Im hoping no more issues pop up...
BobcatASL
Mar 19 2005, 01:39 PM
You can add Mediacom to that list as well.

Although I'm convinced its nothing to do with the ISP
ser_pros
Mar 19 2005, 08:09 PM
Daer customers
We are working on the problems with this server.
It works properly from some ISPs.
If somebody can't connect to the server at once we can transfer their accouts to another server.
Just open the trouble ticket in this case.
steve_d555
Mar 20 2005, 03:41 AM
You guys have switched my servers, but have neglected to import my mySQL database and now I cannot import it because it is saying it is the wrong charset (latin1).
steve_d555
Mar 20 2005, 05:44 AM
Just switched and things seem fine. Thanks.
ryanmills
Mar 20 2005, 08:41 PM
yea they did the same thing to me... I asked about it 15 hours ago hoping it would be fixed before the sunday peak times... The imported some of the tables, others are a mess and I have some sites that are down becuse of it... 10 hours ago I asked them to look into that and the fact that my DNS is jacked... it keeps adding my main domian (that no longer points here for good reason) into the name making my addon domains a subdomain when it should just use the domain name... plus this server is running older software than the one I was one before adding confits and for some reason this server does not add a trailing forward slash "/" to the end of folder name. Now if you the domain whatever.com/wtf it gives you a 404 unless you add the "/" I guess one of my users gallerys wont work becuse of this... what a joke...
ryanmills
Mar 20 2005, 08:47 PM
QUOTE(ser_pros @ Mar 19 2005, 08:09 PM)
Daer customers
We are working on the problems with this server.
It works properly from some ISPs.
If somebody can't  connect to the server at once we can transfer their accouts to another server.
Just open the trouble ticket in this case.
*


Just so anyone who is in the same boat as me. This is NOT true It took few trouble tickets and it was three days before it was even moved (and the first move was botched. None of my domains got moved and then after they were move the DNS was not updated...). I was told somthing was wrong on my end. Its been a week now since I have had to start dealing with this and I am still having problams... its been 10 hours now and no one has replyed to my trouble ticket. Now its peak hours again and I am getting emails saying site links wont work... outstanding... dry.gif
steve_d555
Mar 20 2005, 09:58 PM
Mine went well all in all (cept for a slight problem with the mysql database), and im not having any problems on this new server, and there arent dropped packets anymore.

Just one question though, maybe you guys should think about lowering the TTL on the nameservers from 14400 to 3600 or maybe 7200, because then DNS changes will take less time to show up.

Just a suggestion,
Steve
wh0r3
Mar 21 2005, 02:00 AM
just for grins, after reading this thread, i also ran a ping to that server, and here are the results:

QUOTE
C:\Documents and Settings\NBK Wh0r3>ping 70.84.130.28 -n 40

Pinging 70.84.130.28 with 32 bytes of data:

Reply from 70.84.130.28: bytes=32 time=48ms TTL=51
Reply from 70.84.130.28: bytes=32 time=47ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=47ms TTL=52
Reply from 70.84.130.28: bytes=32 time=48ms TTL=51
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=49ms TTL=52
Reply from 70.84.130.28: bytes=32 time=48ms TTL=52
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=47ms TTL=51
Reply from 70.84.130.28: bytes=32 time=48ms TTL=52
Reply from 70.84.130.28: bytes=32 time=47ms TTL=52
Reply from 70.84.130.28: bytes=32 time=49ms TTL=52
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=48ms TTL=52
Reply from 70.84.130.28: bytes=32 time=48ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=48ms TTL=52
Reply from 70.84.130.28: bytes=32 time=48ms TTL=51
Reply from 70.84.130.28: bytes=32 time=48ms TTL=52
Reply from 70.84.130.28: bytes=32 time=48ms TTL=51
Request timed out.
Request timed out.
Reply from 70.84.130.28: bytes=32 time=47ms TTL=51
Reply from 70.84.130.28: bytes=32 time=47ms TTL=52
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 70.84.130.28:
    Packets: Sent = 37, Received = 18, Lost = 19 (51% loss),
Approximate round trip times in milli-seconds:
    Minimum = 47ms, Maximum = 49ms, Average = 47ms
Control-C
^C
C:\Documents and Settings\NBK Wh0r3>


i am in memphis, on bellsouth's extreme dsl.

ph34r.gif
steve_d555
Mar 21 2005, 03:13 AM
http://www.ripe.net/ripe/maillists/archive...4/msg00119.html

It seems that it is a faily new block, so most ISPs filter it, and thats causing packets to be dropped (or something along those lines).

After switching to a 67.x.x.x server everything is working fine.
ryanmills
Mar 21 2005, 04:43 AM
Yea thats what I have come to understand. What I dont understand is why someone had to blow smoke up my ass about it for three days. Whats even worse to me is that most people cant view anything on that server. If it had worked for me, most new vistors it would have timed out on and they would have thought I had screwed somthing up. I would not have even had a clue... That is bullshit right there...
Slavik
Mar 21 2005, 04:54 AM
Dear Ryanmills!
Be polite please.
ryanmills
Mar 21 2005, 07:38 PM
QUOTE(Slavik @ Mar 21 2005, 04:54 AM)
Dear Ryanmills!
Be polite please.
*


Please view my most resent ticket... I would have been polite but its been over a week. All I want is for my sites to work... I have have around 25 subdomains that are gone and 5 or so add-on domains... its been 16 hours since I added it to my trouble ticket... I have been told over and over. Its must work now... But there is always somthing large that is missed. My last point was just to show some truth. I am sorry for my use of lanuage.

Lets face it... would you be happy if someone lied to you?
Slavik
Mar 22 2005, 06:22 AM
Dear Ryanmills,
we are working on your problem at the moment.

Best regards,
Slavik koshelev
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2024 Invision Power Services, Inc.
IPS Driver Error

IPS Driver Error

There appears to be an error with the database.
You can try to refresh the page by clicking here