South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Restarted it a few times and suddenly it picks up again. Weird. Its is a Dlink. At least I could change my login details again.
Tried logging into my router this morning but I cannot get access to itI always use 192.168.1.1 but it simply refuses. Tried different browsers etc etc but no luck.
Tried logging into my router this morning but I cannot get access to itI always use 192.168.1.1 but it simply refuses. Tried different browsers etc etc but no luck.
That's the Telkom default. Have rarely seen that IP on any non Telkom routers. That IP is the first thing most of us change when we loginAre you not supposed to use 10.0.0.2 for D-link router ?
Are you not supposed to use 10.0.0.2 for D-link router ?
Seen this before on some DLinks. This the 2750U?
Easiest solution is to power-cycle.*
*And yes, I know we say that a lot, but it is best practice and solves a helluva lot of routing issues.
That's the Telkom default. Have rarely seen that IP on any non Telkom routers. That IP is the first thing most of us change when we login
D3 latency seems to have turned into horse ****. Same with archage...
Tracing route to 8.8.8.8 over a maximum of 30 hops
1 1 ms 1 ms <1 ms 172.25.160.1
2 7 ms 14 ms 10 ms 105.233.54.1
3 15 ms 12 ms 13 ms 196.6.121.38
4 14 ms * 14 ms 196.41.96.132
5 51 ms 51 ms 55 ms 196.6.121.237
6 54 ms 54 ms 56 ms 196.41.96.157
7 54 ms 60 ms 52 ms 72.14.220.38
8 210 ms 192 ms 206 ms 66.249.95.8
9 221 ms 221 ms 230 ms 209.85.244.240
10 203 ms 199 ms * 72.14.232.134
11 194 ms 193 ms 194 ms 216.239.47.87
12 * * * Request timed out.
13 196 ms 197 ms 194 ms 8.8.8.8
Trace complete.
D3 also lagging here. Hope I made the right choice by going to CW...
Are you not supposed to use 10.0.0.2 for D-link router ?
That's the Telkom default. Have rarely seen that IP on any non Telkom routers. That IP is the first thing most of us change when we login
I'm looking into the lag issue now, but because we don't employ full time gamers, it really does help if when this happens you run a pathping to the server in question and send it to support so we can reconcile what you guys are experiencing and know what needs fixing if anything.
Even if it's simply an FYI mail so we can pour over it for you.
If we don't get data forthcoming, it makes it difficult to diagnose the actual problems.