This is a multi-part message in MIME format. ------=_NextPart_000_0009_01C0A7DF.DC70CEE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Greetings; Seems I'm having a slight problem with ping, i've never seen it before. = When I'm pinging anything, I get these wrong data byte errors (see = below) 64 octets from 66.1.27.160: icmp_seq=3D171 ttl=3D126 time=3D797.3 ms 64 octets from 66.1.27.160: icmp_seq=3D172 ttl=3D126 time=3D1132.2 ms wrong data byte #0 should be 0x9f but was 0x9e9e 9c a7 3a 36 2e 4 0=20 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f = 20 21 22 23 24 25 26 27=20 28 29 2a 2b 2c 2d 2e 2f=20 64 octets from 66.1.27.160: icmp_seq=3D174 ttl=3D126 time=3D1910.4 ms wrong data byte #0 should be 0xa1 but was 0xa0a0 9c a7 3a 30 2e 4 0=20 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f = 20 21 22 23 24 25 26 27=20 28 29 2a 2b 2c 2d 2e 2f=20 64 octets from 66.1.27.160: icmp_seq=3D176 ttl=3D126 time=3D471.4 ms 64 octets from 66.1.27.160: icmp_seq=3D177 ttl=3D126 time=3D192.2 ms 64 octets from 66.1.27.160: icmp_seq=3D178 ttl=3D126 time=3D526.7 ms 64 octets from 66.1.27.160: icmp_seq=3D179 ttl=3D126 time=3D1164.6 ms wrong data byte #0 should be 0xa6 but was 0xa5a5 9c a7 3a 29 2e 4 0=20 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f = 20 21 22 23 24 25 26 27=20 28 29 2a 2b 2c 2d 2e 2f=20 64 octets from 66.1.27.160: icmp_seq=3D180 ttl=3D126 time=3D174.3 ms Any advice on fixing this, or letting me know what it is, would be = greatly appreaited. Thanks.. Tyler Hall EVTI Inc. (480) 503-3228 ------=_NextPart_000_0009_01C0A7DF.DC70CEE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Greetings;

Seems I'm having a slight problem with = ping, i've=20 never seen it before. When I'm pinging anything, I get = these=20 wrong data byte errors (see below)

64 octets from 66.1.27.160: = icmp_seq=3D171 ttl=3D126=20 time=3D797.3 ms
64 octets from 66.1.27.160: icmp_seq=3D172 ttl=3D126 = time=3D1132.2=20 ms
wrong data byte #0 should be 0x9f but was 0x9e9e 9c a7 3a 36 2e 4 = 0=20
        8 9 a b c d e f 10 11 12 = 13 14 15=20 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27=20
        28 29 2a 2b 2c 2d 2e 2f =
64=20 octets from 66.1.27.160: icmp_seq=3D174 ttl=3D126 time=3D1910.4 = ms
wrong data byte=20 #0 should be 0xa1 but was 0xa0a0 9c a7 3a 30 2e 4 0=20
        8 9 a b c d e f 10 11 12 = 13 14 15=20 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27=20
        28 29 2a 2b 2c 2d 2e 2f =
64=20 octets from 66.1.27.160: icmp_seq=3D176 ttl=3D126 time=3D471.4 ms
64 = octets from=20 66.1.27.160: icmp_seq=3D177 ttl=3D126 time=3D192.2 ms
64 octets from = 66.1.27.160:=20 icmp_seq=3D178 ttl=3D126 time=3D526.7 ms
64 octets from 66.1.27.160: = icmp_seq=3D179=20 ttl=3D126 time=3D1164.6 ms
wrong data byte #0 should be 0xa6 but was = 0xa5a5 9c a7=20 3a 29 2e 4 0
        8 9 a b c d = e f 10=20 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27=20
        28 29 2a 2b 2c 2d 2e 2f =
64=20 octets from 66.1.27.160: icmp_seq=3D180 ttl=3D126 time=3D174.3 = ms

Any advice on fixing this, or letting = me know what=20 it is, would be greatly appreaited. Thanks..

Tyler Hall
EVTI Inc.
(480)=20 503-3228

------=_NextPart_000_0009_01C0A7DF.DC70CEE0--