New wireless connection woes..

[Appledrop]

hi there, yesterday i recieved my new buffalo cable wireless router with a 802.11g card from Texus Instruments. All was easy to set up etc but i have a sligh problem - check out this "ping -t" to my router from this pc upstairs...


Reply from 192.168.11.1: bytes=32 time=907ms TTL=
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=880ms TTL=
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=907ms TTL=
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=2ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=2ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=907ms TTL=
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=907ms TTL=
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=907ms TTL=
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64
Reply from 192.168.11.1: bytes=32 time=1ms TTL=64


There is a clear pattern, and i dont know what is causing it quite frankly! I have tried changing the channel of operation, moving both the wireless router and the antenna on my card, and nothing stops this... I have a utility called Wireless Lan Configuration Utility, oddly , that reports the signal as ''poor'' at '-65/0' - not qutie sure what that -65/0 bit is :l. However, when i do not connect using that utility, but using windows wireless zero thingmibob, it reports signal as ''Very good'' or ''Excellent.'' Odd.

I have TKIP WPA enabled, but it does it even with out that mode... Hmm, also the router has no external antenna; i saw it has a hole on it for connecting one, but i am not sure that my symptoms indicate a signal quality issue, as i thoguht that only bandwidth would suffer, and not latency?? Anyway, if its possible to make a ghetto antenna, i may look into that as well...


Any clues please folks??

 

[Appledrop]

Ok now this is strange.. i went and played CS with ping running, came back a few mins later, and it hadnt done it at ALL.. I suppose thats good, but gah... HMM!!!

yup, definately does never do it in CS.. so my hypothesis is... That it only does it when its idling for some silly reason.