• January 20, 2021, 09:36:07 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: DWA 140 Lag Spikes  (Read 10084 times)

bobbydazla

  • Level 1 Member
  • *
  • Posts: 6
DWA 140 Lag Spikes
« on: July 15, 2014, 11:30:04 AM »

Hi there,

Desperately trying to resolve my random lag spikes i'm having with this adapter :(

Makes online gaming an absolute
 nightmare atm, games like WoW / Wildstar will have 30ms ping then shoots to 2000 for a second, this happens every 10-15 seconds.

Been doing some testing using my Nexus 5, My Pc and the router, my nexus 5 pinging the router never breaks 10-15ms. The PC however clearly spikes. Reference below:

Reply from 192.168.1.254: bytes=32 time=2045ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=7ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=5ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=18ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2030ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2044ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=7ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2047ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=5ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=6ms TTL=64
Reply from 192.168.1.254: bytes=32 time=5ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2046ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2034ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=6ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=9ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2043ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2054ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2046ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2050ms TTL=64

Tried a few things, including both the Ralink / D-Link drivers, unticking everything other than IP4 in the wireless settings, enabled multimedia mode in the adapter properties. Can anyone help!?

Thanks!

 
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49461
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: DWA 140 Lag Spikes
« Reply #1 on: July 15, 2014, 11:48:04 AM »

Link>Welcome!


  • What region are you located?

What Mfr and model is the main host router?

Wireless Configurations on the main host router
Links>Wireless Installation Considerations and Managing Signal Congestion and Good Neighbour Policy

  • What wireless modes are you using?
  • 2.4Ghz Routers only: Try single mode G or N or mixed G and N?
  • Channel Width set for Auto 20/40Mhz or try 20Mhz only.
  • Try setting a manual Channel to a open or unused channel. 1, 6 or 11. 11 for single mode N if the channel is clear. 13 for EU regions.
  • What security mode are you using? Preferred security is WPA-Personal. WPA2/AES Only. Some WiFi adapters don't support AES, so you might want to try TPIK only or Auto TPIK and AES.
  • Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by?
  • Any other WiFi routers in the area? Link> Use InSSIDer to find out. How many?
  • If you have any of these options, Try turning OFF or ON Short GI, WLAN Partition, Extra Wireless Protection and WMM Enable

PC 3rd Party Security Software Configurations
  • Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.
  • Turn off all devices accept for one wired LAN PC while testing.
Logged
Cable: 1Gb/50Mb>NetGear CAX80>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

bobbydazla

  • Level 1 Member
  • *
  • Posts: 6
Re: DWA 140 Lag Spikes
« Reply #2 on: July 15, 2014, 11:51:24 AM »

I'm based in England. The router is a BT Home Hub 5, BT infinity Fibre package. I've tried changing the modes to B/G and B/G/N, even messed with the channel.

Thanks for the reply :)
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49461
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: DWA 140 Lag Spikes
« Reply #3 on: July 15, 2014, 11:53:07 AM »

Does the adapter work on a different router? Say at a friends or families place as a test?

Logged
Cable: 1Gb/50Mb>NetGear CAX80>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

bobbydazla

  • Level 1 Member
  • *
  • Posts: 6
Re: DWA 140 Lag Spikes
« Reply #4 on: July 15, 2014, 11:56:05 AM »

Can't say I've tried that, not do i have a spare router. I could however test it connecting to my mobile tethering  over wifi :)
Logged

bobbydazla

  • Level 1 Member
  • *
  • Posts: 6
Re: DWA 140 Lag Spikes
« Reply #5 on: July 15, 2014, 12:00:13 PM »

Reply from 192.168.43.1: bytes=32 time=1600ms TTL=64
Reply from 192.168.43.1: bytes=32 time=2ms TTL=64
Reply from 192.168.43.1: bytes=32 time=6ms TTL=64
Reply from 192.168.43.1: bytes=32 time=7ms TTL=64
Reply from 192.168.43.1: bytes=32 time=8ms TTL=64
Reply from 192.168.43.1: bytes=32 time=15ms TTL=64
Reply from 192.168.43.1: bytes=32 time=9ms TTL=64
Reply from 192.168.43.1: bytes=32 time=8ms TTL=64
Reply from 192.168.43.1: bytes=32 time=7ms TTL=64
Reply from 192.168.43.1: bytes=32 time=8ms TTL=64
Reply from 192.168.43.1: bytes=32 time=11ms TTL=64
Reply from 192.168.43.1: bytes=32 time=1ms TTL=64
Reply from 192.168.43.1: bytes=32 time=2ms TTL=64
Reply from 192.168.43.1: bytes=32 time=14ms TTL=64
Reply from 192.168.43.1: bytes=32 time=14ms TTL=64
Reply from 192.168.43.1: bytes=32 time=2ms TTL=64
Reply from 192.168.43.1: bytes=32 time=2ms TTL=64
Reply from 192.168.43.1: bytes=32 time=9ms TTL=64
Reply from 192.168.43.1: bytes=32 time=7ms TTL=64
Reply from 192.168.43.1: bytes=32 time=8ms TTL=64
Reply from 192.168.43.1: bytes=32 time=16ms TTL=64
Reply from 192.168.43.1: bytes=32 time=2057ms TTL=64
Reply from 192.168.43.1: bytes=32 time=1ms TTL=64
Reply from 192.168.43.1: bytes=32 time=15ms TTL=64
Reply from 192.168.43.1: bytes=32 time=12ms TTL=64
Reply from 192.168.43.1: bytes=32 time=16ms TTL=64
Reply from 192.168.43.1: bytes=32 time=13ms TTL=64
Reply from 192.168.43.1: bytes=32 time=7ms TTL=64
Reply from 192.168.43.1: bytes=32 time=16ms TTL=64
Reply from 192.168.43.1: bytes=32 time=16ms TTL=64
Reply from 192.168.43.1: bytes=32 time=16ms TTL=64
Reply from 192.168.43.1: bytes=32 time=16ms TTL=64
Reply from 192.168.43.1: bytes=32 time=2050ms TTL=64


Still happens :(
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49461
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: DWA 140 Lag Spikes
« Reply #6 on: July 15, 2014, 12:03:57 PM »

No other back ground apps are running on this PC?

Can you test with a different PC by chance?

I would try a different router if you can with a friend or neighbor.

Might try a test and open up the WiFi security on the main host router temporarily and see if you notice the same thing...
Logged
Cable: 1Gb/50Mb>NetGear CAX80>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

bobbydazla

  • Level 1 Member
  • *
  • Posts: 6
Re: DWA 140 Lag Spikes
« Reply #7 on: July 15, 2014, 12:13:25 PM »

I'll open up the security and report back. Might be able to test on another machine too. Give me a few :)
Logged

bobbydazla

  • Level 1 Member
  • *
  • Posts: 6
Re: DWA 140 Lag Spikes
« Reply #8 on: July 15, 2014, 12:23:39 PM »

Security on open and still the same, won't be able to check on a different network or machine for a bit i don't think?
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49461
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: DWA 140 Lag Spikes
« Reply #9 on: July 15, 2014, 12:26:17 PM »

Need to check with Different PC if you can and find someone whom could test the adapter out on a different main host router. Possible problem with the adapter or problem between adapter and this main host router. Only way to find out is to test on different main host router to see if problem follows. If so, then issue maybe with adapter. If issue doesn't follow or seen, then you'll know.
Logged
Cable: 1Gb/50Mb>NetGear CAX80>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.