Constant disconnects

Status
Not open for further replies.
mine went dead at 1:30am, had to reconnect when i woke up at 6am.
Same old story...
 
Joy, it's happening to me again today (after the first morning of no issues since the 17th).
Why is it that when the connection dies (doesn't 'disconnect', it just stops working), it still shows that uploading is going on, but zero download?

I'm not that clued up (I just stick the thing in a usb and select connect), why would this happen?
 
sitting in Bloem with signal at -83 dbm and every 10 minutes the connection just dies:mad: so far I have wasted 300 odd Mb trying to download something. CellC fix your network , no wonder Vodacom and MTN have not dropped thier prices yet.... :whistle:
 
raoulduke said:
I got the 5 Gig a month 3G card. The first month was superb. No problems and the connection was super fast.

Now, my 3G card constantly disconnects.

I'm starting to understand why we had to pay upfront for the full 12 months. Is it that Cell C has taken on too many clients and now does not have the capacity to handle all this broadband ?

Or is it just me ?
Very disappointed.
Click to expand...

Which area are you in?
 
I am unable to use my whooosh for like 2 weeks now, I can connect but cannot browse...connection keeps on timing out. below is a pit of my experience when pinging 208.67.222.222

really really frustrating! :sick::mad::wtf::confused::cry:

Reply from 208.67.222.222: bytes=32 time=296ms TTL=54
Reply from 208.67.222.222: bytes=32 time=292ms TTL=54
Reply from 208.67.222.222: bytes=32 time=304ms TTL=54
Reply from 208.67.222.222: bytes=32 time=307ms TTL=54
Reply from 208.67.222.222: bytes=32 time=299ms TTL=54
Request timed out.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Request timed out.
General failure.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 208.67.222.222: bytes=32 time=481ms TTL=54
Request timed out.
Reply from 208.67.222.222: bytes=32 time=393ms TTL=54
Reply from 208.67.222.222: bytes=32 time=345ms TTL=54
Reply from 208.67.222.222: bytes=32 time=308ms TTL=54
Reply from 208.67.222.222: bytes=32 time=339ms TTL=54
Reply from 208.67.222.222: bytes=32 time=352ms TTL=54
 
the router was connected definitely. problem is also it looses connection all the time, can hardly keep the connection for 5 minutes. If I enter a website IP i can connect to the site but only for 2 or 3 minutes then I drop connection. If I get a reply from the IP and i try and enter the URL into the browser I cannot browse - site times out :-(
 
Last edited by a moderator:
I currently have a -65dBm 3G signal on an E1820, inductive coupler and external antenna and keep getting disconnected every few minutes.

Update: Seems to have stabilized, it has remained connected for about 40 minutes now.
 
Last edited:
Edwe said:
Cell C is experiencing network problems due to an issue with its Home Location Register (HLR).
Click to expand...

Originally Posted by http://www.hellkom.co.za/newsviewer/local/4351/Cell-C-network-problems
Cell C experienced a technical glitch which affected one of the nodes in certain numbers this afternoon...Our technicians are currently working on the problem and we are hoping to resolve it soon. Cell C wishes to apologise for the inconvenience caused.
Click to expand...

They been working on that one for a little while huh
23 July, 2007
Click to expand...
 
Does ANYONE have a resolution to this.
What a waste of R3k!!!!!!!!!!:mad:
 
Today has been extremely fast for me here in the West Rand. Hope it stays that way!!
 
Axis said:
Today has been extremely fast for me here in the West Rand. Hope it stays that way!!
Click to expand...

Thanks. lmao. you really just making things worse for those of us with this damn disconnecting problems.
 
I stay in Parkview JHB used my cell c stick for the first time in a month last night and my experience was terrible. It connects and switches modes the whole time then all traffic dies. Couldn't get a signal. Today is just as bad and the signal use to always be so good.

SNR: -87, -13

This erratic behavior I cant stand
 
Last edited:
I stay in the South of Johannesburg my wooooosh service was suburb for over 3days non-stop all of a sudden yesterday I try use my woooooosh and was unable to pick up any 3G connection at all, back to my normal house walking ( aka war driving) and discovered all base stations are down(Due to not picking up any 3G MDMA was shown nothing). Only 1 base station in operation same spot as last year TV room.... Perhaps they doing maintenance on sites like firmware updates etc - cause seriously the other day I could do everything with my wooosh even a conversation over 5hours on Skype without getting disconnected or any interruption.

If CELL C wanna live up to their reputation name "4Great service" Please be honest to your customers or have a network page so customers are informed what areas are affected and what is the resolution or ETA and cause of problem...
 
RichardG said:
...I try use my woooooosh and was unable to pick up any 3G connection at all, back to my normal house walking ( aka war driving) and discovered all base stations are down(Due to not picking up any 3G MDMA was shown nothing).
Click to expand...
Was your modem in '3G Preferred' mode or '3G Only' mode?
 
Has anyone tried installing the 'latest' drivers from the cell c website. Im running windows 7 64-bit and I think that play a big part with all the disconnects. But anyway, how do you install the damn drivers. Ive extracted them and opened the app, but nothing happens. So frustrating!

some help on this would be p**s lekker lol.
 
BearCruz said:
Has anyone tried installing the 'latest' drivers from the cell c website. Im running windows 7 64-bit and I think that play a big part with all the disconnects.
Click to expand...
People are also experiencing this problem on their phones and on their routers, so installing new drivers won't help them.
 
I'm getting following:
Loss of connection.
Info on network is blank (when on "3G only").
Weak EDGE signal (when on "3G preferred").

Re-plugging usually helps.
WTH?
 
Last edited:
Pretty much the same issues here in Centurion, device is going crazy *week/2 weeks now*
 
I did use the method "3G ONLY" apply if I switch over to EDGE I am unable to do anything not even connect to IRC, the RSSI -75 on EDGE, also spoke to someone else that stays in the area - she is also experiences the same problem and pretty much she is frustrated 2 blocks away from me

Must remember we are the "Test Subjects" All I ask for is a stable network for a week
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X