I don't have an SD card in my N900 or my E1820.Ginggs would it be worth a try to disable the SDcard to see if that got anything to do with it?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I don't have an SD card in my N900 or my E1820.Ginggs would it be worth a try to disable the SDcard to see if that got anything to do with it?
Did you ever get an answer from [email protected] ?Same problem. Been stuck with it ever since i got my modem & package.
Is CellC looking into it?
Do they even know this problem exists?
How bout CellC dash with 24hr auto reconnect or some sort of fix.
Hey guys just out of curiosity..... Does this problem occur randomly or after a given amout of time? And knowing the types of people on mybb everyone has checked their cap?
It is random but only after being connected for a few hours.Hey guys just out of curiosity..... Does this problem occur randomly or after a given amout of time? And knowing the types of people on mybb everyone has checked their cap?
It is random but only after being connected for a few hours.
When I tried to go online this morning I could only reach www.cellc.co.za and my router log showed the connection had been established on December 17 at 07:50. So this time it happened after being connected for between 44 and 51 hours.
Cap is still good, disconnected and reconnected and I'm back online.
Have you made sure that there is no power saving options causing this prob (Vista/Win 7)?
My Cell-C E1820 is plugged into a MikroTik RB-411U router, so no possibility of Vista / Windows 7 power saving options being a problem.Have you made sure that there is no power saving options causing this prob (Vista/Win 7)?
In that case your connection would be down and you would not be able to access any sites.
# tcptraceroute -n -q 1 www.cellc.co.za 80
Selected device tun0, address 41.55.132.36, port 18105 for outgoing packets
Tracing the path to www.cellc.co.za (41.72.143.60) on TCP port 80, 30 hops max
1 *
2 41.48.23.13 (41.48.23.13) 70.038 ms
3 10.228.221.45 (10.228.221.45) 59.859 ms
4 41.48.23.13 (41.48.23.13) 69.893 ms
5 41.48.16.1 (41.48.16.1) 69.973 ms
6 *
7 *
8 41.181.47.223 (41.181.47.223) 108.351 ms
9 196.44.0.155 (196.44.0.155) 69.889 ms
10 196.44.31.26 (196.44.31.26) 69.895 ms
11 196.44.31.97 (196.44.31.97) 69.961 ms
12 196.30.1.21 (196.30.1.21) 69.920 ms
13 196.30.156.136 (196.30.156.136) 129.935 ms
14 196.30.213.108 (196.30.213.108) 70.585 ms
15 41.72.136.23 (41.72.136.23) 89.266 ms
16 41.72.143.60 (41.72.143.60) [open] 68.956 ms
# tcptraceroute -n -q 1 www.google.co.za 80
Selected device tun0, address 41.55.132.36, port 18433 for outgoing packets
Tracing the path to www.google.co.za (155.232.240.19) on TCP port 80, 30 hops max
1 *
2 41.48.23.13 (41.48.23.13) 82.175 ms
3 *
4 *
5 41.48.0.3 (41.48.0.3) 189.409 ms
6 41.48.253.36 (41.48.253.36) 77.977 ms
7 *
8 *
9 *
10 196.44.31.95 (196.44.31.95) 87.803 ms
11 196.44.31.254 (196.44.31.254) 89.958 ms
12 196.44.0.72 (196.44.0.72) 69.910 ms
13 198.32.142.33 (198.32.142.33) 69.924 ms
14 155.232.6.38 (155.232.6.38) 99.880 ms
15 155.232.240.19 (155.232.240.19) [open] 99.992 ms
# tcptraceroute -n -q 1 www.google.co.za 80
Selected device tun0, address 41.55.132.36, port 18959 for outgoing packets
Tracing the path to www.google.co.za (155.232.240.19) on TCP port 80, 30 hops max
1 *
2 41.48.23.13 (41.48.23.13) 61.894 ms
3 *
4 *
5 *
6 *
7 *
8 *
9 *
10 *
11 *
12 *
13 *
14 *
15 155.232.240.19 (155.232.240.19) [open] 97.365 ms
# tcptraceroute -n -q 1 www.cellc.co.za 80
Selected device tun0, address 41.49.152.107, port 51035 for outgoing packets
Tracing the path to www.cellc.co.za (41.72.143.60) on TCP port 80, 30 hops max
1 *
2 41.48.23.13 (41.48.23.13) 61.898 ms
3 10.228.221.39 (10.228.221.39) 89.848 ms
4 41.48.23.13 (41.48.23.13) 69.907 ms
5 41.48.16.1 (41.48.16.1) 59.928 ms
6 41.48.0.3 (41.48.0.3) 79.931 ms
7 41.48.253.36 (41.48.253.36) 59.921 ms
8 41.181.47.223 (41.181.47.223) 79.940 ms
9 196.44.0.155 (196.44.0.155) 89.957 ms
10 196.44.31.26 (196.44.31.26) 79.851 ms
11 196.44.31.97 (196.44.31.97) 79.916 ms
12 196.30.1.22 (196.30.1.22) 79.912 ms
13 196.30.156.136 (196.30.156.136) 79.981 ms
14 196.30.213.108 (196.30.213.108) 69.945 ms
15 41.72.136.23 (41.72.136.23) 79.917 ms
16 41.72.143.60 (41.72.143.60) [open] 79.930 ms
# tcptraceroute -n -q 1 www.google.co.za 80
Selected device tun0, address 41.49.152.107, port 19626 for outgoing packets
Tracing the path to www.google.co.za (155.232.240.19) on TCP port 80, 30 hops max
1 *
2 41.48.23.13 (41.48.23.13) 60.704 ms
3 41.48.23.13 (41.48.23.13) 69.545 ms
4 41.48.16.1 (41.48.16.1) 89.594 ms
5 41.48.0.3 (41.48.0.3) 81.769 ms
6 41.48.253.36 (41.48.253.36) 77.506 ms
7 41.181.47.223 (41.181.47.223) 79.649 ms
8 196.44.0.155 (196.44.0.155) 79.615 ms
9 196.44.31.26 (196.44.31.26) 79.637 ms
10 196.44.31.95 (196.44.31.95) 69.618 ms
11 196.44.31.254 (196.44.31.254) 79.626 ms
12 196.44.0.72 (196.44.0.72) 89.641 ms
13 198.32.142.33 (198.32.142.33) 79.671 ms
14 155.232.6.38 (155.232.6.38) 99.567 ms
15 155.232.240.19 (155.232.240.19) [open] 99.642 ms
is this still an issue or have ppl just stopped posting about it?
just to clarify is this a random event? ie does it happen while browsing or after it's been idle for a while (idle= long download and no other traffic or just left connected)? Havn't had this happen to me yet so wanna try recreate to see if there is some kind of pattern