cancel
Showing results for 
Search instead for 
Did you mean: 

Routers / Wireless

kained
Newbie
Posts: 3
Registered: ‎06-09-2010

Routers / Wireless

Hey Guys,
I am an online gamer(world of warcraft) for which connection is well lets just say important, i have recently moved from orange to plusnet to stop the 200 - 1kms i was getting with orange, but now im not so sure it was them while iam aware that my line will be training with DLM atm things are still problematic with my game connection(although the ping mostly stays at 63 ms it  spikes over 600 to 5.1k and yes i have a screenie!).
I have ran a ping test and outputted to a text file.
Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time=35ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=28ms TTL=64
Reply from 192.168.2.1: bytes=32 time=26ms TTL=64
Reply from 192.168.2.1: bytes=32 time=28ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=5ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=9ms TTL=64
Reply from 192.168.2.1: bytes=32 time=43ms TTL=64
Reply from 192.168.2.1: bytes=32 time=47ms TTL=64
Reply from 192.168.2.1: bytes=32 time=53ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=4ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=4ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=9ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=4ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.2.1:
    Packets: Sent = 201, Received = 201, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 53ms, Average = 2ms
Spikes(just a rescan ? from the wirless?)
I have a belkin wireless N router (300mbps) with a wireless n pci card, i have a decent spec pc:
Core 2 Quad Processor Q6600 (GO Stepping)
6 Gig RAM DDR2

My router is connected to the only telephone socket in the house, and i have removed the front panel and going straight through a brand new filter to the master socket i have even removed the home phone, i have changed router from orange live box (54mbps) to the new router (yet to try the one from plus net).
Im just running out of ideas, any suggestions?
4 REPLIES
Community Veteran
Posts: 14,469
Registered: ‎30-07-2007

Re: Routers / Wireless

Are you saying your PC/Games machine is connected to the router via wireless? If so your speed and pings will be affected by other local wireless networks. What are your pings if you connect via a wired connection?
What is your sync rates and speeds?
Do a ping to www.plus.net and report back
Do you have interleaving on? This can double your normal ping rates to neare 30->40ms, whereas fastpath (no interleaving) can give you pings around 160>20ms

kained
Newbie
Posts: 3
Registered: ‎06-09-2010

Re: Routers / Wireless

Hi,
It did show fastpath a couple of days ago but now seems to be    "Type Interleave Path"
My PC is connected via wireless i have tried multiple channels with no difference in results.
Without running a long cable through my house iam unable to test with wired but if that become my only option i will look at getting one fitted.
Pinging portal.plus.net [212.159.8.2] with 32 bytes of data:
Reply from 212.159.8.2: bytes=32 time=38ms TTL=251
Reply from 212.159.8.2: bytes=32 time=39ms TTL=251
Reply from 212.159.8.2: bytes=32 time=39ms TTL=251
Reply from 212.159.8.2: bytes=32 time=39ms TTL=251
Reply from 212.159.8.2: bytes=32 time=38ms TTL=251
Reply from 212.159.8.2: bytes=32 time=38ms TTL=251
Reply from 212.159.8.2: bytes=32 time=39ms TTL=251
Request timed out.
Request timed out.
Reply from 212.159.8.2: bytes=32 time=68ms TTL=251
Reply from 212.159.8.2: bytes=32 time=56ms TTL=251
Reply from 212.159.8.2: bytes=32 time=42ms TTL=251
Reply from 212.159.8.2: bytes=32 time=119ms TTL=251
Reply from 212.159.8.2: bytes=32 time=44ms TTL=251
Reply from 212.159.8.2: bytes=32 time=38ms TTL=251
Reply from 212.159.8.2: bytes=32 time=59ms TTL=251
Reply from 212.159.8.2: bytes=32 time=40ms TTL=251
Reply from 212.159.8.2: bytes=32 time=48ms TTL=251
Reply from 212.159.8.2: bytes=32 time=39ms TTL=251
Reply from 212.159.8.2: bytes=32 time=38ms TTL=251
Reply from 212.159.8.2: bytes=32 time=40ms TTL=251
Reply from 212.159.8.2: bytes=32 time=80ms TTL=251
Reply from 212.159.8.2: bytes=32 time=38ms TTL=251
Reply from 212.159.8.2: bytes=32 time=1371ms TTL=251
Reply from 212.159.8.2: bytes=32 time=39ms TTL=251
Reply from 212.159.8.2: bytes=32 time=37ms TTL=251
Reply from 212.159.8.2: bytes=32 time=38ms TTL=251
Reply from 212.159.8.2: bytes=32 time=42ms TTL=251
Reply from 212.159.8.2: bytes=32 time=37ms TTL=251
Reply from 212.159.8.2: bytes=32 time=38ms TTL=251
Reply from 212.159.8.2: bytes=32 time=39ms TTL=251
Reply from 212.159.8.2: bytes=32 time=38ms TTL=251
Reply from 212.159.8.2: bytes=32 time=39ms TTL=251
Reply from 212.159.8.2: bytes=32 time=39ms TTL=251
Reply from 212.159.8.2: bytes=32 time=38ms TTL=251
Reply from 212.159.8.2: bytes=32 time=38ms TTL=251
Ping statistics for 212.159.8.2:
   Packets: Sent = 36, Received = 34, Lost = 2 (5% loss),
Approximate round trip times in milli-seconds:
   Minimum = 37ms, Maximum = 1371ms, Average = 83ms
Ping as requested noticed the huge spike and the time outs, any suggestions gonna lower the security on my wireless that may help if there is anything you can suggest or change me to fastpath again that would be appreciated.
EDIT #2
Ok so after the huge spikes modified my wireless security to WEP 128 from WPA2-PSK although iam only connected as 54mbps the connection seems better:
Pinging portal.plus.net [212.159.9.2] with 32 bytes of data:
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Request timed out.
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=35ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=38ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=37ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=35ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=35ms TTL=248
Reply from 212.159.9.2: bytes=32 time=34ms TTL=248
Ping statistics for 212.159.9.2:
    Packets: Sent = 58, Received = 57, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 38ms, Average = 33ms
Only 1% loss and no huge spikes, is the loss something to do with your end or mine ?
jojopillo
Grafter
Posts: 9,786
Registered: ‎16-06-2010

Re: Routers / Wireless

Hi kained,
Your first results show a spike in latency to your router, and since you have changed your security settings seems to have improved it which may suggest a router issue. 1 packet lost would not really be a concern. I would suggest you use pathping for bulk or multiple pings instead of ping.
Jojo Smiley
kained
Newbie
Posts: 3
Registered: ‎06-09-2010

Re: Routers / Wireless

Hey,
Thanks for your response, yeah i guess its a router / adapter issue, not worried is stab le on 54mbps atm, i have requested to be placed on fastpath again so i will see how it goes after that
Kind Regards
Jason