Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Fat|Tony]

Hi thar, I did some searches and wasn't able to find any topics on this, sorry if it's a repeat.

So I've got two computers wireless N cards on both, one linksys wmp400 and one dlink-552 connecting to a DIR-825 version A(1.0 firmware), both are having spikes to the router at around the same time, spikes as high as a thousand or two. Signal is ~80%-90% on both, and I have already moved the router, I mounted it on a wall above all the electronics around it, instead of behind and under them as it was before. Although the previous setup was working fine for some time, and this just recently began. Spikes happen while there's no traffic going across the network. I'm using task manager right now to monitor traffic out from my computer, if there's a better program i can download, I'll do so post haste. I don't know exactly what I need to be checking for here, but I work for a DSL company tshooting customer end equipment, so I'm at least somewhat familiar with all the general principles at work here, just not sure of specifics or what exactly i need to look at for this issue.

Troubleshooting done: netsh int ip reset, netsh winsock reset, reinstalled with latest NIC drivers from DLink site. I've also hard reset the router and reconfigured it, it's got a modem bridged to it with PPPoE set up on the router.

I've never really sat around and pinged at my router for no reason, so I'm not sure what I should realistically be expecting, is it normal for wifi pings to go over 1 when there IS data going through? Or should it pretty much maintain a low ping as long as it's not at maximum throughput. I'm also trying it now with my laptop which is wireless g and that's having the same issues.

This time was a bit better, no 2000 pings, but this is about what it looks like, there's a spike, drops down, is fine for a bit, then another spike, does this somewhat consistently on all machines. When I run a speed test it will also spike a bit (seems reasonable for this to be normal, but is it?) I mean, I know this is going to put a hurting on my internet connection, but if my pings are stopping at the router then coming back, I should have a 300mbps connection, which my 7mbps internet connection is barely denting, even running at full blast.

Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=255ms TTL=64
Reply from 192.168.0.1: bytes=32 time=63ms TTL=64
Reply from 192.168.0.1: bytes=32 time=213ms TTL=64
Reply from 192.168.0.1: bytes=32 time=73ms TTL=64
Reply from 192.168.0.1: bytes=32 time=78ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=94ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=43ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 829, Received = 829, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 823ms, Average = 15ms

Thanks in advance for any help if you need any more info just let me know.

[Fat|Tony]

Also I'm running on the 2.4ghz router, as for some reason my computer will not see the 5.0.  The 5ghz is disabled.

[mac]

Have you tried using a static IP assignment instead of DHCP?

[Fatman]

The DWS-552 is 2.4 GHz only.  I can't find the Linksys WMP400N, but the WMP300N is 2.4 GHz only.  The WMP600N on the other hand is dual band.  That would explain your problems at 5 GHz on at least one of your cards.

As for our latency, wireless interference causes wireless devices to delay a certain period before broadcasting, which could cause such latency.  If it is new, I would check for new 2.4 GHz phones in the area or new competing networks you may be able to channel away from (only use 1, 6, and 11).

[Fat|Tony]

[edit] Also, Mac, I had it set to auto, just hard coded it, and I'm still having the same issue[/edit]


I think it started around the time a wireless printer went on the network, so i'm going to cut that out of it tomorrow. No cordless phones though. I just rearranged my room so my NIC antena have a better line of sight and got the computer off the ground. I was thinking of picking up one of these for even better positioning (my nic has the antenna screwed right into the back, which dont accomodate signal well. At this point though, i've got from 60% signal to 90% per the dlink software, and I'm still having the issue. I can't see why the printer would interfere with it as i'm under the impression it just connects to the router like another nic, and not that it's broadcasting a signal to computers that they connect directly to it (instead of the router).

With omnidirectional antenna, does it matter which way they're angled at? I understand the omni part, but idk if there's just better saturation or what if you point the end AT the recieving device or what. Right now it's about 20 feet away in a straight line, with two walls inbetween no pipes in them, just a lightswitch on one.

Are there any other antenna I can get, maybe a directional, as about 90-120 degree cone would cover all of my devices, but I have no idea where to get one, or if they're just a normal standard that would work with the router or what.

This definitely isn't normal wireless lag, I previously had no issues playing multiplayer games, but now I'm constantly spiking. This literally never happened, then started happening consistantly on 3 computers. Either something changed, or something on the router isn't working right. \=


So first ones were with about 75-80% signal, these are at 90% signal


Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=51ms TTL=64
Reply from 192.168.0.1: bytes=32 time=168ms TTL=64
Reply from 192.168.0.1: bytes=32 time=18ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=68ms TTL=64
Reply from 192.168.0.1: bytes=32 time=101ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=51ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=70ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=226ms TTL=64
Reply from 192.168.0.1: bytes=32 time=16ms TTL=64
Reply from 192.168.0.1: bytes=32 time=153ms TTL=64
Reply from 192.168.0.1: bytes=32 time=20ms TTL=64
Reply from 192.168.0.1: bytes=32 time=70ms TTL=64
Reply from 192.168.0.1: bytes=32 time=121ms TTL=64
Reply from 192.168.0.1: bytes=32 time=104ms TTL=64
Reply from 192.168.0.1: bytes=32 time=154ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=20ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Reply from 192.168.0.1: bytes=32 time=37ms TTL=64
Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=40ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=30ms TTL=64
Reply from 192.168.0.1: bytes=32 time=28ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=15ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=31ms TTL=64
Reply from 192.168.0.1: bytes=32 time=14ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 136, Received = 136, Lost = 0 (0%
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 226ms, Average = 24ms

[Fatman]

The interference may not be your property.  It could be a new wireless network or other source of 2.4 GHz interference in the neighbourhood.

Omnidirectional antennas have a signal area that looks like a doughnut around the antenna.  The higher the gain, the flatter and wider the doughnut.