Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Getting lagspikes in online games suddenly


  • Please log in to reply
12 replies to this topic

#1 Pajajn

Pajajn

  • Members
  • 368 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:127.0.0.1
  • Local time:01:06 PM

Posted 20 January 2013 - 01:25 PM

I noticed that i recently began to get strange lagspikes on my wireless gaming PC. I play League of Legends and Counter-Strike 1.6 which are very stable dependant to get the good hit registration..

Router ASUS N56u
Modem Zyxel Tripleplay D331 or someting similiar, gray box
Adapter/NIC: Cisco AE1000 ralink driver
Link: 2.4Ghz
speed: 144Mbps full strength

Problem
: Whenever i play i get a small lagspike which varies from around 20ms and goes up to 120ms for 1-3 seconds and then back to normal. nothing more than that and in FPS based games the network stability are really important to get secured accuracy <_<


MiniToolBox by Farbar  Version:10-01-2013
Ran by MSI (administrator) on 20-01-2013 at 19:20:08
Running from "C:\Documents and Settings\MSI\My Documents\Hämtade filer"
Microsoft Windows XP Service Pack 3 (X86)
Boot Mode: Normal
***************************************************************************

========================= IE Proxy Settings: ============================== 

Proxy is not enabled.
No Proxy Server is set.
========================= Hosts content: =================================


127.0.0.1       localhost

========================= IP Configuration: ================================


WARNING: Could not obtain host information from machine: [HOME-40BC64AB84]. Some commands may not be available.
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.



# ---------------------------------- 
# Interface IP Configuration         
# ---------------------------------- 
pushd interface ip


# Interface IP Configuration for "Wireless Network Connection 2"

set address name="Wireless Network Connection 2" source=dhcp 
set dns name="Wireless Network Connection 2" source=dhcp register=PRIMARY
set wins name="Wireless Network Connection 2" source=dhcp


popd
# End of interface IP configuration




Windows IP Configuration



        Host Name . . . . . . . . . . . . : home-40bc64ab84

        Primary Dns Suffix  . . . . . . . : 

        Node Type . . . . . . . . . . . . : Unknown

        IP Routing Enabled. . . . . . . . : No

        WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Wireless Network Connection 2:



        Connection-specific DNS Suffix  . : 

        Description . . . . . . . . . . . : Linksys AE1000 #3

        Physical Address. . . . . . . . . : 98-FC-11-C5-F0-B8

        Dhcp Enabled. . . . . . . . . . . : Yes

        Autoconfiguration Enabled . . . . : Yes

        IP Address. . . . . . . . . . . . : 192.168.1.123

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . : 192.168.1.1

        DHCP Server . . . . . . . . . . . : 192.168.1.1

        DNS Servers . . . . . . . . . . . : 192.168.1.1

        Lease Obtained. . . . . . . . . . : den 20 januari 2013 19:11:47

        Lease Expires . . . . . . . . . . : den 21 januari 2013 19:11:47

Server:  my.router
Address:  192.168.1.1

Name:    google.com
Addresses:  173.194.32.35, 173.194.32.36, 173.194.32.37, 173.194.32.38
	  173.194.32.39, 173.194.32.40, 173.194.32.41, 173.194.32.46, 173.194.32.32
	  173.194.32.33, 173.194.32.34



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



Reply from 173.194.32.35: bytes=32 time=20ms TTL=51

Reply from 173.194.32.35: bytes=32 time=19ms TTL=51



Ping statistics for 173.194.32.35:

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

Approximate round trip times in milli-seconds:

    Minimum = 19ms, Maximum = 20ms, Average = 19ms

Server:  my.router
Address:  192.168.1.1

Name:    yahoo.com
Addresses:  98.139.183.24, 206.190.36.45, 98.138.253.109



Pinging yahoo.com [98.139.183.24] with 32 bytes of data:



Reply from 98.139.183.24: bytes=32 time=563ms TTL=46

Reply from 98.139.183.24: bytes=32 time=587ms TTL=46



Ping statistics for 98.139.183.24:

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

Approximate round trip times in milli-seconds:

    Minimum = 563ms, Maximum = 587ms, Average = 575ms



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=64

Reply from 127.0.0.1: bytes=32 time<1ms TTL=64



Ping statistics for 127.0.0.1:

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

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x40003 ...98 fc 11 c5 f0 b8 ...... Linksys AE1000 #3
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1   192.168.1.123	  20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1	  1
      192.168.1.0    255.255.255.0    192.168.1.123   192.168.1.123	  20
    192.168.1.123  255.255.255.255        127.0.0.1       127.0.0.1	  20
    192.168.1.255  255.255.255.255    192.168.1.123   192.168.1.123	  20
        224.0.0.0        240.0.0.0    192.168.1.123   192.168.1.123	  20
  255.255.255.255  255.255.255.255    192.168.1.123   192.168.1.123	  1
Default Gateway:       192.168.1.1
===========================================================================
Persistent Routes:
  None

========================= Event log errors: ===============================

Application errors:
==================
Error: (01/17/2013 02:28:43 PM) (Source: Application Error) (User: )
Description: Faulting application controlcenteri.exe, version 1.0.229.0, faulting module controlcenteri.exe, version 1.0.229.0, fault address 0x00442ee9.
Processing media-specific event for [controlcenteri.exe!ws!]

Error: (01/13/2013 02:00:30 AM) (Source: Application Error) (User: )
Description: Faulting application rads_user_kernel.exe, version 0.0.0.0, faulting module rads_user_kernel.exe, version 0.0.0.0, fault address 0x000b8554.
Processing media-specific event for [rads_user_kernel.exe!ws!]

Error: (01/11/2013 03:20:45 PM) (Source: Application Error) (User: )
Description: Faulting application rads_user_kernel.exe, version 0.0.0.0, faulting module rads_user_kernel.exe, version 0.0.0.0, fault address 0x000b8554.
Processing media-specific event for [rads_user_kernel.exe!ws!]

Error: (01/03/2013 06:41:15 PM) (Source: Application Error) (User: )
Description: Faulting application rads_user_kernel.exe, version 0.0.0.0, faulting module rads_user_kernel.exe, version 0.0.0.0, fault address 0x000b8554.
Processing media-specific event for [rads_user_kernel.exe!ws!]

Error: (12/30/2012 06:22:01 PM) (Source: Application Error) (User: )
Description: Faulting application rads_user_kernel.exe, version 0.0.0.0, faulting module rads_user_kernel.exe, version 0.0.0.0, fault address 0x000b8554.
Processing media-specific event for [rads_user_kernel.exe!ws!]

Error: (12/27/2012 00:59:02 PM) (Source: Application Error) (User: )
Description: Faulting application rads_user_kernel.exe, version 0.0.0.0, faulting module rads_user_kernel.exe, version 0.0.0.0, fault address 0x000b8554.
Processing media-specific event for [rads_user_kernel.exe!ws!]

Error: (12/25/2012 02:30:02 PM) (Source: Application Error) (User: )
Description: Faulting application rads_user_kernel.exe, version 0.0.0.0, faulting module rads_user_kernel.exe, version 0.0.0.0, fault address 0x000b8554.
Processing media-specific event for [rads_user_kernel.exe!ws!]

Error: (12/22/2012 03:19:38 PM) (Source: crypt32) (User: )
Description: Failed auto update retrieval of third-party root list sequence number from: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt> with error: This network connection does not exist.

Error: (12/22/2012 03:19:38 PM) (Source: crypt32) (User: )
Description: Failed auto update retrieval of third-party root list sequence number from: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt> with error: This network connection does not exist.

Error: (12/22/2012 03:19:38 PM) (Source: crypt32) (User: )
Description: Failed auto update retrieval of third-party root list sequence number from: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt> with error: This network connection does not exist.


System errors:
=============
Error: (01/20/2013 07:20:09 PM) (Source: DCOM) (User: HOME-40BC64AB84)
Description: DCOM got error "%%1058" attempting to start the service winmgmt with arguments ""
in order to run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}

Error: (01/20/2013 07:20:08 PM) (Source: DCOM) (User: HOME-40BC64AB84)
Description: DCOM got error "%%1058" attempting to start the service winmgmt with arguments ""
in order to run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}

Error: (01/20/2013 07:11:39 PM) (Source: DCOM) (User: NT AUTHORITY)
Description: DCOM got error "%%1058" attempting to start the service winmgmt with arguments ""
in order to run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}

Error: (01/20/2013 07:11:39 PM) (Source: DCOM) (User: NT AUTHORITY)
Description: DCOM got error "%%1058" attempting to start the service winmgmt with arguments ""
in order to run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}

Error: (01/20/2013 07:11:39 PM) (Source: DCOM) (User: NT AUTHORITY)
Description: DCOM got error "%%1058" attempting to start the service winmgmt with arguments ""
in order to run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}

Error: (01/20/2013 07:11:39 PM) (Source: DCOM) (User: NT AUTHORITY)
Description: DCOM got error "%%1058" attempting to start the service winmgmt with arguments ""
in order to run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}

Error: (01/20/2013 07:11:24 PM) (Source: DCOM) (User: NT AUTHORITY)
Description: DCOM got error "%%1058" attempting to start the service winmgmt with arguments ""
in order to run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}

Error: (01/20/2013 07:11:24 PM) (Source: DCOM) (User: NT AUTHORITY)
Description: DCOM got error "%%1058" attempting to start the service winmgmt with arguments ""
in order to run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}

Error: (01/20/2013 07:11:24 PM) (Source: DCOM) (User: NT AUTHORITY)
Description: DCOM got error "%%1058" attempting to start the service winmgmt with arguments ""
in order to run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}

Error: (01/20/2013 07:11:24 PM) (Source: DCOM) (User: NT AUTHORITY)
Description: DCOM got error "%%1058" attempting to start the service winmgmt with arguments ""
in order to run the server:
{8BC3F05E-D86B-11D0-A075-00C04FB68820}


Microsoft Office Sessions:
=========================
Error: (01/17/2013 02:28:43 PM) (Source: Application Error)(User: )
Description: controlcenteri.exe1.0.229.0controlcenteri.exe1.0.229.000442ee9

Error: (01/13/2013 02:00:30 AM) (Source: Application Error)(User: )
Description: rads_user_kernel.exe0.0.0.0rads_user_kernel.exe0.0.0.0000b8554

Error: (01/11/2013 03:20:45 PM) (Source: Application Error)(User: )
Description: rads_user_kernel.exe0.0.0.0rads_user_kernel.exe0.0.0.0000b8554

Error: (01/03/2013 06:41:15 PM) (Source: Application Error)(User: )
Description: rads_user_kernel.exe0.0.0.0rads_user_kernel.exe0.0.0.0000b8554

Error: (12/30/2012 06:22:01 PM) (Source: Application Error)(User: )
Description: rads_user_kernel.exe0.0.0.0rads_user_kernel.exe0.0.0.0000b8554

Error: (12/27/2012 00:59:02 PM) (Source: Application Error)(User: )
Description: rads_user_kernel.exe0.0.0.0rads_user_kernel.exe0.0.0.0000b8554

Error: (12/25/2012 02:30:02 PM) (Source: Application Error)(User: )
Description: rads_user_kernel.exe0.0.0.0rads_user_kernel.exe0.0.0.0000b8554

Error: (12/22/2012 03:19:38 PM) (Source: crypt32)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txtThis network connection does not exist.

Error: (12/22/2012 03:19:38 PM) (Source: crypt32)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txtThis network connection does not exist.

Error: (12/22/2012 03:19:38 PM) (Source: crypt32)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txtThis network connection does not exist.


========================= Memory info: ===================================

Percentage of memory in use: 21%
Total physical RAM: 3327.1 MB
Available physical RAM: 2602.27 MB
Total Pagefile: 5211.17 MB
Available Pagefile: 4372.49 MB
Total Virtual: 2047.88 MB
Available Virtual: 1970.31 MB

========================= Partitions: =====================================

1 Drive c: () (Fixed) (Total:931.5 GB) (Free:902.82 GB) NTFS

========================= Users: ========================================

User accounts for \\

Administrator            Guest                    HelpAssistant            
MSI                      SUPPORT_388945a0         


**** End of log ****

Edited by Pajajn, 20 January 2013 - 01:25 PM.


BC AdBot (Login to Remove)

 


#2 Baltboy

Baltboy

    Bleepin' Flame Head


  • Members
  • 1,432 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Pennsylvania
  • Local time:02:06 PM

Posted 20 January 2013 - 07:19 PM

Usually lag spikes are on your ISP's end of the connection. It could be many things depending on what type of service you have. I would suspect hey have a bad cable or splice in the line. Call your ISP and tell them you have been having issues with the connection. If they don't do it ask them to run a test on your connection for troubles and max speed.
Get your facts first, then you can distort them as you please.
Mark Twain

#3 The Pugilist

The Pugilist

  • Members
  • 826 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:02:06 PM

Posted 21 January 2013 - 10:23 AM

I was having trouble finding your modem on google so I'm unsure what type of internet service you have. Slower broadband connections (like DSL) could explain the poor latency but also other traffic on your network could too (like someone streaming youtube/pandora/netflix/etc). I would be interested to know the quality of your internet connection, this can be ascertained by running a speed test. Once you do that, let me know what your ping, download speed, and upload speed are and we can diagnose it further from there.

Another thing that does catch my eye in your log file is this:

Reply from 98.139.183.24: bytes=32 time=563ms TTL=46

Reply from 98.139.183.24: bytes=32 time=587ms TTL=46


The latency we are seeing in these pings seems very high to me, but sadly this could be caused by a number of factors so it does not tell me where the problem is exactly.

Ultimately, other factors in this problem could include:
  • Problems with the servers to which you are connecting.
  • problems with your ISP (as Baltboy suggested)
  • Problems with your networking hardware
  • Interference on your wireless network

//Dave

#4 Pajajn

Pajajn
  • Topic Starter

  • Members
  • 368 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:127.0.0.1
  • Local time:01:06 PM

Posted 21 January 2013 - 04:45 PM

Right now speedtest had to server near me so i had awful ms up to 73. I therefore made a flashbased speed test with www.bredbandskollen.se and got

11,93 Mbit/s send files: 1,94 Mbit/s
Responsetime: 0-5MS


When i download with Bit/utorrent i get
Down: 1,5MB/sec
Up: ~400Kb/sec (if i remembe right)

I also upgraded the router firmware to opensourced russian code-project version and net is already more stable. But not as perfect as i would have it. Is there anyway that WPA2 security has any differences in using TKIP or AES encryption signal wise?

#5 The Pugilist

The Pugilist

  • Members
  • 826 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:02:06 PM

Posted 22 January 2013 - 05:09 PM

Well your bandwidth looks sufficient to play the games that you are talking about unless there are other people on your connection using the bandwidth.

Responsetime: 0-5MS


I am suspicious of the accuracy of that result but if the firmware change in your router has made a difference, then it would seem as though that was at least part of the problem. As far as the question about TKIP and AES, no that does not have any affect on signal quality. If there are many other wireless networks nearby it could be that yours and several others are all on the same channel, which can be problematic. Some routers have the ability to determine the best channel to use, others have tools to show you neighboring networks and the channels that they occupy. Given that you are using non-standard firmware though I cant really help.
//Dave

#6 Pajajn

Pajajn
  • Topic Starter

  • Members
  • 368 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:127.0.0.1
  • Local time:01:06 PM

Posted 23 January 2013 - 04:18 PM

Im right now pretty sure the problem isn't within the firmware itself

Rather be in general network settings/registry *
Channel settings or something

I just wanna point out that i used TCP optimizer but i read around and think that maybe the TTL=64 is too low? maybe 128 is better for my wireless and that Max duplicate ACKS could be changed from 2 to 3?

Im not 100 % sure about all this and since i really enjoyed their tweak tool on automatic before all these years i see no point in why it schould abandon me now :angry: Anyone experienced and welknown in these terms that could help please

Edited by Pajajn, 23 January 2013 - 07:39 PM.


#7 The Pugilist

The Pugilist

  • Members
  • 826 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:02:06 PM

Posted 24 January 2013 - 10:58 PM

Well, to be honest with you, there are many programs out there which claim to automatically make your computer faster or decrease your network latency, etc. Most of these however are scams and offer no real benefit. Truth is, if you are having problems with your latency, there is probably bigger problems than the specific TCP/IP settings your computer is using (like TTL and Max duplicate Acks). Furthermore, logic dictates that since these default settings work perfectly for many other people, they are not the cause of your latency fluctuations.

If it was me, I would continue to look into your networking equipment and your ISP. Back in post 4 you said:

Right now speedtest had to server near me so i had awful ms up to 73. I therefore made a flashbased speed test with www.bredbandskollen.se and got


I would encourage you not to disregard a result just because it does not tell you what you want to hear. You have seen repeatedly that your latency is high to remote hosts, like 75 to the speedtest.net servers and the almost half a second to yahoo (as seen in the original post). This, I believe is the area which you should direct your research.

As a wise person once said: "If you hear hoofbeats, look for horses not zebras"
//Dave

#8 Pajajn

Pajajn
  • Topic Starter

  • Members
  • 368 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:127.0.0.1
  • Local time:01:06 PM

Posted 25 January 2013 - 09:59 AM

The Pugilist yes ofcourse :) i also tried pinging the servers i usually play on which are hosted here in Sweden... look on every server i suddenly get a markable lag :wacko:
Speedtest here by the way! Posted Image

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48

Reply from 79.138.109.41: bytes=32 time=18ms TTL=48

Reply from 79.138.109.41: bytes=32 time=18ms TTL=48

Reply from 79.138.109.41: bytes=32 time=18ms TTL=48

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48

Reply from 79.138.109.41: bytes=32 time=59ms TTL=48

Reply from 79.138.109.41: bytes=32 time=3906ms TTL=48

Reply from 79.138.109.41: bytes=32 time=40ms TTL=48

Reply from 79.138.109.41: bytes=32 time=18ms TTL=48

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48

Reply from 79.138.109.41: bytes=32 time=18ms TTL=48

Reply from 79.138.109.41: bytes=32 time=18ms TTL=48

Reply from 79.138.109.41: bytes=32 time=18ms TTL=48

Reply from 79.138.109.41: bytes=32 time=18ms TTL=48

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48

Reply from 79.138.109.41: bytes=32 time=18ms TTL=48

Reply from 79.138.109.41: bytes=32 time=19ms TTL=48



Ping statistics for 79.138.109.41:

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

Approximate round trip times in milli-seconds:

Minimum = 18ms, Maximum = 3906ms, Average = 42ms

Edited by Pajajn, 25 January 2013 - 10:00 AM.


#9 Pajajn

Pajajn
  • Topic Starter

  • Members
  • 368 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:127.0.0.1
  • Local time:01:06 PM

Posted 25 January 2013 - 12:53 PM




Pinging 192.168.1.1 with 32 bytes of data:







Request timed out.



Request timed out.



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Destination host unreachable.



Destination host unreachable.



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Request timed out.



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=71ms TTL=64



Reply from 192.168.1.1: bytes=32 time=634ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time=4ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

[b]Signal strength: Very good

[/b]  <img src='http://www.bleepingcomputer.com/forums/public/style_emoticons/<#EMO_DIR#>/wacko.gif' class='bbc_emoticon' alt=':wacko:' /> <img src='http://www.bleepingcomputer.com/forums/public/style_emoticons/<#EMO_DIR#>/wacko.gif' class='bbc_emoticon' alt=':wacko:' />  

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64



Reply from 192.168.1.1: bytes=32 time<1ms TTL=64







Ping statistics for 192.168.1.1:



    Packets: Sent = 239, Received = 234, Lost = 5 (2% loss),



Approximate round trip times in milli-seconds:



    Minimum = 0ms, Maximum = 634ms, Average = 3ms




Edited by Pajajn, 25 January 2013 - 01:03 PM.


#10 Baltboy

Baltboy

    Bleepin' Flame Head


  • Members
  • 1,432 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Pennsylvania
  • Local time:02:06 PM

Posted 30 January 2013 - 01:24 PM

I am assuming the 192.168.1.1 ping is to your router? That should never be unreachable or exceed the <1ms time. That means either your router or the wireless adapter is not working properly. First question is why are you not using the Cisco supplied driver for your wireless adapter?

The first thing I would do would be to connect via ethernet cable directly to the modem and run the ping tests and speed tests to see if the spikes continue. If so then it is more than likely and issue with your ISP. A smaller possiblity would be that your router is a faulty but I would start with the ISP.

If the spikes go away with the use of a cable then the issue exists with the adapter. First look for interference anything new in between you and the router. Wireless phones, compact flouresent lighting, microwaves, or any other type of probable interference. If none of them exist I would install the Cisco supplied driver for your OS. If that doesn't work then I would think that the adapter itself is failing. If you can try a different adapter to see if the spikes continue.
Get your facts first, then you can distort them as you please.
Mark Twain

#11 Pajajn

Pajajn
  • Topic Starter

  • Members
  • 368 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:127.0.0.1
  • Local time:01:06 PM

Posted 30 January 2013 - 01:28 PM

I recently upgraded with a reformat to Windows 7 64bit and everything working smooth so far actually :D i haven't ran a ping yet but the spikes are as much as gone.

REcently though i had Device malfunctioning so i removed the extra lenthh cable from the Cisco adapter and plugged into front panel and much more stable right now actually. Also on point why im not using the Cisco driver is because there isnt any program it's only using windows built in wireless feature...

#12 Baltboy

Baltboy

    Bleepin' Flame Head


  • Members
  • 1,432 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Pennsylvania
  • Local time:02:06 PM

Posted 30 January 2013 - 01:30 PM

If the driver provided by cisco is newer, which it probably is since it was revised 4/2012, I would download and install it. It may address lots of other little issues that are not covered by the built in windows driver.
Get your facts first, then you can distort them as you please.
Mark Twain

#13 Pajajn

Pajajn
  • Topic Starter

  • Members
  • 368 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:127.0.0.1
  • Local time:01:06 PM

Posted 30 January 2013 - 02:52 PM

No you misunderstood my comment Baltboy ^^ there is a driver for the device itself but it still uses windows wireless manager :thumbup2:. Also using the newer ralink driver always been worse in my case and i tried several times and at several partitions and ended up with crashes and unstable usb port disconnecting etc. You could read about it in Cisco AE1000 support forum if you google :/

Right now everything working though, i tried pinging 192.168.1.1 recently and got almost 99 percent <1ms sometimes 1-3 and one time i had 19 but never above this so very stable when device connected in front panel without extra length cable :blink:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users