Router problem or not?

HowTo

HowTo

Expert Member
Joined
Aug 7, 2006
Messages
4,372
Reaction score
622
Location
East Rand
Hi All

Have a look at the following tracert log.
HTML: 
C:\Users\Jochen>tracert -d telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

  1    93 ms   217 ms   388 ms  10.0.0.2
  2    34 ms    33 ms    35 ms  196.210.155.1
  3    41 ms    54 ms    61 ms  196.38.72.229
  4   141 ms   144 ms   119 ms  196.38.73.9
  5   117 ms   117 ms   112 ms  168.209.1.140
  6   129 ms   121 ms   127 ms  168.209.1.179
  7   116 ms   116 ms   131 ms  196.25.46.89
  8    92 ms    76 ms    60 ms  196.43.25.137
  9    87 ms    93 ms   109 ms  196.43.39.166
 10     *       91 ms   100 ms  196.43.23.6
 11   129 ms    90 ms    74 ms  196.43.23.34
 12    69 ms    80 ms    84 ms  196.43.22.222

Trace complete.
I did a fresh install from win8.1 back to win7. I noticed this since the install of win7 64bit.
Hop 1 is my concern?
What could be the problem?
 
Do a ping from PC to router i.e. ping 10.0.0.2 and post the results.
If you get 4 returns all under 1ms then its not a local network issue or a PC issue.

try that first and then we'll go further...
 
@ben dover

Do a ping from PC to router i.e. ping 10.0.0.2 and post the results.
If you get 4 returns all under 1ms then its not a local network issue or a PC issue.

try that first and then we'll go further...
Click to expand...

Will do when at home.
 
HowTo said:
Hi All

Have a look at the following tracert log.
HTML: 
C:\Users\Jochen>tracert -d telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

  1    93 ms   217 ms   388 ms  10.0.0.2
  2    34 ms    33 ms    35 ms  196.210.155.1
  3    41 ms    54 ms    61 ms  196.38.72.229
  4   141 ms   144 ms   119 ms  196.38.73.9
  5   117 ms   117 ms   112 ms  168.209.1.140
  6   129 ms   121 ms   127 ms  168.209.1.179
  7   116 ms   116 ms   131 ms  196.25.46.89
  8    92 ms    76 ms    60 ms  196.43.25.137
  9    87 ms    93 ms   109 ms  196.43.39.166
 10     *       91 ms   100 ms  196.43.23.6
 11   129 ms    90 ms    74 ms  196.43.23.34
 12    69 ms    80 ms    84 ms  196.43.22.222

Trace complete.
I did a fresh install from win8.1 back to win7. I noticed this since the install of win7 64bit.
Hop 1 is my concern?
What could be the problem?
Click to expand...

Which Antivirus do you have? Could you run a speedtest on your phone over Wifi and post results here please. Also, try swopping out LAN cable
 
@gregmmc
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jochen>ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Click to expand...

Result as requested.
 
@Zertop
Which Antivirus do you have? Could you run a speedtest on your phone over Wifi and post results here please. Also, try swopping out LAN cable
Click to expand...

Using AVG Antivirus, downloading speed test for my phone.
 
The NSA have intercepted your data stream, re-routed it for logging, and then re-routed it back to you. Have you been downloading naughty movies?

On a more serious note, have you tried different cables? It could be a faulty cable between your PC and router. And have you tried the following good advice:

ben dover said:
Do a ping from PC to router i.e. ping 10.0.0.2 and post the results.
If you get 4 returns all under 1ms then its not a local network issue or a PC issue.

try that first and then we'll go further...
Click to expand...

If the above advice produces 1ms pings, then try pings and tracerts to other local websites. Perhaps there is an issue with traffic going to the Telkom website. It could even be specific to your exchange or DSLAM.
 
Hi All

Busy with fresh install. So far so good.
Only so far lan installed.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jochen Gundlach>Ping 10.0.0.2

Pinging 10.0.0.2 with 32 bytes of data:
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Click to expand...
All the best for the new year to you all.

Back again.
C:\Users\ ping -t 10.0.0.2

Pinging 10.0.0.2 with 32 bytes of data:
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=327ms TTL=64
Reply from 10.0.0.2: bytes=32 time=530ms TTL=64
Reply from 10.0.0.2: bytes=32 time=124ms TTL=64
Reply from 10.0.0.2: bytes=32 time=327ms TTL=64
Reply from 10.0.0.2: bytes=32 time=454ms TTL=64
Reply from 10.0.0.2: bytes=32 time=59ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64
Reply from 10.0.0.2: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.2:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 530ms, Average = 107ms
 
Last edited:
It could be the system talking load on The CPU and not having resources to manage the ping results, check the task manager...
 
Have you got another device on the local LAN you can ping to measure results, again, try it through two or more routers/hubs/switches to eliminate them as suspects!
 
The ping to the router should NOT exceed 1-2ms on a LAN connection, unless someone (or your PC) is sending/receiving at 100Mbps speeds or someone is doing a DoS attack on your modem from the Internet.

If its a Telkom D-Link DSL-2750U, then you should search the forums for the security measures that you should perform on it. You should perhaps ensure that you do it for the other D-Link modems too!
Like do what UltimateNinjaPandaDudeGuy said here:
Ways to fix this:

1.) Set remote access off by default
2.) Set the router not to respond to ICMP packets by default
3.) Set the router with a username and password randomly generated on a sticker on the router for web interface and WiFi network name and password.

Problem SOLVED!
Click to expand...
 
@Pada
1.) Set remote access off by default
2.) Set the router not to respond to ICMP packets by default
3.) Set the router with a username and password randomly generated on a sticker on the router for web interface and WiFi network name and password.
Click to expand...

Have done the above to my Netgear DGN2200 modem.
Problem is still present.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X