heard one the other day that this could be heat related, don't know if I buy
it but.........
"Monkeys" <(E-Mail Removed)> wrote in message
news:bv8nfg$2cg$(E-Mail Removed)...
> Wireless Guru help required:
>
> Have previouly been using a Dlink 900AP+ and PC running ICS with a local
> ADSL modem for shared wireless internet access. Worked fine.
>
> Dropped 900AP+ and now using Dlink DSL-604+ ADSL Router, works fine.
But...
> after about an hour, maybe less maybe more, noticed ping on online gaming
> rises from ~40ms to ~170ms. Nothing fixes this apart from disabling and
> then reenabling the wireless network connection. Ping now back to ~40ms,
> for a while. I get the same results on two different PC's, both using
> D-Link DWL-520+ cards.
>
> I investigated further: Let's call this PC PCBadPing. If I ping PCBadPing
> from another PC on the local wireless network then I get variable results,
> from <10ms to 160ms, so it's a local issue not an internet issue. If I
ping
> any other wireless PC on the local network I get consistent <10ms. So
it's
> peculiar to the workstation, not to the network generally.
>
> Here is an example of pinging PCBadPing from the router:
> Reply from 192.168.0.4, time=160 ms
> Reply from 192.168.0.4, time=10 ms
> Reply from 192.168.0.4, time=160 ms
> Reply from 192.168.0.4, time=90 ms
> Reply from 192.168.0.4, time=130 ms
> Reply from 192.168.0.4, time=60 ms
> Reply from 192.168.0.4, time=100 ms
>
> Here is an example of pinging a different wireless PC from the router:
> Reply from 192.168.0.3, time<10 ms
> Reply from 192.168.0.3, time<10 ms
> Reply from 192.168.0.3, time<10 ms
> Reply from 192.168.0.3, time<10 ms
> Reply from 192.168.0.3, time<10 ms
> Reply from 192.168.0.3, time<10 ms
> Reply from 192.168.0.3, time<10 ms
>
> Here is an example of pinging PCBadPing from another PC on the network
> (using -t)
> Pinging 192.168.0.4 with 32 bytes of data:
>
> Reply from 192.168.0.4: bytes=32 time=96ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=123ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=147ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=171ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=180ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=203ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=7ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=31ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=39ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=63ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=88ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=111ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=135ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=160ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=184ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=207ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=26ms TTL=128
> Reply from 192.168.0.4: bytes=32 time=50ms TTL=128
>
> Ping statistics for 192.168.0.4:
> Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 7ms, Maximum = 207ms, Average = 112ms
>
> Notice the saw-tooth effect; ping steadily increases then drops back. I
get
> the same effect if PCBadPing pings another PC on the wireless network.
>
> The main difficulty in fixing this is that restarting the offending PC, or
> restarting the network connection after changing settings, appears to fix
> the problem for a while.
>
> This only started after removing the 900AP+/ICS comination and replacing
> with the 604+.
>
> HELP!!
>
>
|
Similar Threads
Linear Mode
