Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Router Problems
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Fibre Broadband
- :
- Router Problems
Router Problems
25-10-2014 1:44 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Hi
I have the Technicolor TG582n router provided by plusnet. I used to get ping problems before (like 1-2 second interruptions every minute), now the stuff has gone worse. I tried changing the settings, changing channels, setting game mode and other stuff like that, but it only got EVEN worse. I tried resetting the settings via the special button in the extremely laggy interface, however it did not help. Have a look at this:
Any suggestions or recipes (other then buying a different router)?
Oh yeah, and the event log is empty.
UPDATE
This looks more like the pattern I used to get. Everything alright, then suddenly a drop.
I have the Technicolor TG582n router provided by plusnet. I used to get ping problems before (like 1-2 second interruptions every minute), now the stuff has gone worse. I tried changing the settings, changing channels, setting game mode and other stuff like that, but it only got EVEN worse. I tried resetting the settings via the special button in the extremely laggy interface, however it did not help. Have a look at this:
ping google.com -n 100
Pinging google.com [74.125.230.102] with 32 bytes of data:
Reply from 74.125.230.102: bytes=32 time=389ms TTL=57
Reply from 74.125.230.102: bytes=32 time=25ms TTL=57
Reply from 74.125.230.102: bytes=32 time=248ms TTL=57
Reply from 74.125.230.102: bytes=32 time=429ms TTL=57
Reply from 74.125.230.102: bytes=32 time=24ms TTL=57
Reply from 74.125.230.102: bytes=32 time=253ms TTL=57
Reply from 74.125.230.102: bytes=32 time=474ms TTL=57
Reply from 74.125.230.102: bytes=32 time=26ms TTL=57
Reply from 74.125.230.102: bytes=32 time=293ms TTL=57
Reply from 74.125.230.102: bytes=32 time=508ms TTL=57
Reply from 74.125.230.102: bytes=32 time=23ms TTL=57
Reply from 74.125.230.102: bytes=32 time=332ms TTL=57
Reply from 74.125.230.102: bytes=32 time=24ms TTL=57
Reply from 74.125.230.102: bytes=32 time=23ms TTL=57
Reply from 74.125.230.102: bytes=32 time=370ms TTL=57
Reply from 74.125.230.102: bytes=32 time=24ms TTL=57
Reply from 74.125.230.102: bytes=32 time=55ms TTL=57
Reply from 74.125.230.102: bytes=32 time=413ms TTL=57
Reply from 74.125.230.102: bytes=32 time=24ms TTL=57
Ping statistics for 74.125.230.102:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 508ms, Average = 208ms
Control-C
^C
Any suggestions or recipes (other then buying a different router)?
Oh yeah, and the event log is empty.
UPDATE
ping google.com -n 100
Pinging google.com [74.125.230.100] with 32 bytes of data:
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=14ms TTL=57
Reply from 74.125.230.100: bytes=32 time=17ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=16ms TTL=57
Reply from 74.125.230.100: bytes=32 time=506ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=601ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=17ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=16ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=16ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=22ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=18ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Request timed out.
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Reply from 74.125.230.100: bytes=32 time=15ms TTL=57
Ping statistics for 74.125.230.100:
Packets: Sent = 35, Received = 34, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 601ms, Average = 47ms
Control-C
^C
This looks more like the pattern I used to get. Everything alright, then suddenly a drop.
Message 1 of 2
(741 Views)
1 REPLY 1
Re: Router Problems
28-10-2014 9:24 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Have you tried updating the router to the latest firmware?
Wireless can be a bit hit and miss - particularly if there is some kind of interference.
Wireless can be a bit hit and miss - particularly if there is some kind of interference.
Message 2 of 2
(273 Views)
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page