is this a problem [Archive] - SpeedGuide.net Broadband Community

View Full Version : is this a problem


1337Munk
05-28-08, 08:09 AM
i am on my laptop connected wireless to my dsl modem and an xbox360 is also using the modem (wired) ...is there a problem here????

Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=33ms TTL=58
Reply from 82.133.85.65: bytes=32 time=139ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=36ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=30ms TTL=58
Reply from 82.133.85.65: bytes=32 time=31ms TTL=58
Reply from 82.133.85.65: bytes=32 time=34ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=30ms TTL=58
Reply from 82.133.85.65: bytes=32 time=34ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=32ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=31ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=27ms TTL=58
Reply from 82.133.85.65: bytes=32 time=35ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=30ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=33ms TTL=58

Ping statistics for 82.133.85.65:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 139ms, Average = 31ms
why did the ping get big and how can a fix it .

heres some info on my connection
Line State Up
Modulation DMT
Data Path Interleave


Downstream Upstream
Max Allowed Speed (kbps) 3072 384
SN Margin (dB) 20.50 18.00
Line Attenuation (dB) 32.50 16.50
CRC Errors 6 1
.
VPI / VCI 8/35
Protocol PPP over ATM LLC/SNAP

In Octets 415547696
In Errors 0
In Unicast Packets 477208
In Non Unicast Packets 0
In Discard Packets 0

Out Octets 29912373
Out Errors 0
Out Unicast Packets 352546
Out Non Unicast Packets 0
Out Discard Packets 0
.
wireless stat-----
Wireless ID (SSID) hello
Current Channel 1
WEP Encryption Disabled

In Good Frames 323064
In Packets 323064
In Unicast Frames 280591
In Multicast Frames 33142
In Discard Frames 0

Out Good Frames 156038
Out Packets 156038
Out Unicast Frames 154702
Out Multicast Frames 1328
Out Discard Frames 0
.

YeOldeStonecat
05-28-08, 08:33 AM
If you're using wireless....an occasional blip in your pings such as you see would be normal. Even without wireless..if you're using a wired connection..just 1 occasional blip like that can be caused my many things..and considered normal.

1337Munk
05-28-08, 01:37 PM
will that effect online gaming????

YARDofSTUF
05-28-08, 05:00 PM
will that effect online gaming????

Slightly, are you having issues?

1337Munk
05-28-08, 06:02 PM
i just pinged there with my laptop wired.. looks good. so its just jumpy on wireless so? what u think?
Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=27ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=27ms TTL=58
Reply from 82.133.85.65: bytes=32 time=27ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=27ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=29ms TTL=58
Reply from 82.133.85.65: bytes=32 time=27ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=27ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=27ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58
Reply from 82.133.85.65: bytes=32 time=27ms TTL=58
Reply from 82.133.85.65: bytes=32 time=28ms TTL=58

Ping statistics for 82.133.85.65:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 29ms, Average = 27ms

YeOldeStonecat
05-28-08, 09:02 PM
i just pinged there with my laptop wired.. looks good. so its just jumpy on wireless so? what u think?

That looks normal to me...
wired = solid problem free connection.
Wireless = the occasional hiccup, due to nearly infinite reasons.

For online gaming..wireless stinks....I'll take a good copper connection any day of the week without further thought, hands down.

1337Munk
05-29-08, 07:00 AM
alright, cheers for the info :)