Is this normal (for Neotel)

[ebendl]

I am online, 23:14. I have a continuous ping running to Neotel's DNS server 41.160.0.36. My RSSI is 66. I am using a Windows 2003 server, connected to the Prime device and then shared via NAT across the network. The ping is running on the server.

The ping goes like this:

Reply from 41.160.0.36: bytes=32 time=263ms TTL=250
Reply from 41.160.0.36: bytes=32 time=212ms TTL=250
Request timed out.
General failure.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Reply from 41.160.0.36: bytes=32 time=288ms TTL=250
Reply from 41.160.0.36: bytes=32 time=267ms TTL=250
General failure.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Reply from 41.160.0.36: bytes=32 time=616ms TTL=250
Reply from 41.160.0.36: bytes=32 time=435ms TTL=250
General failure.
Destination host unreachable.
Destination host unreachable.

Sometimes longer, sometimes shorter between successful pings. Sometimes longer continuous pings. Ping times down to 100 ms at the shortest.

Is this "normal" - do you guys get a similar result? Could it be a faulty device, incompatibility with Windows Server 2003, bad signal? I am sick to the bone of this Neotel connection - only waiting for the REP to check out the towers, then I am canceling. Every time it "phases out", my downloads stop, my wife's ABSA internet banking logs out, my Exchange mail drops. While the connection is active, I get fairly good results: multiple processes running (i.e. browsing, downloading, IM etc.) and downloads are above 50 KB/s.

 

[medicnick83]

Yes, this is normal.

 

[ebendl]

Yes, this is normal.

Great, at least we're all being treated (like crap) equally.

 

[medicnick83]

My pings are sometimes really bad, late into the night (we talking early hours of the morning) it gets much much better.

 

[Next Thing]

The infamous disconnection problem lol

 

[LabAnimal]

yep, about right! But I managed to fix my problem! Its actually so simple to resolve, why I didn't do this earlier is beyond me!.........


.... I canceled and joined SAOL uncapped!

 

[Next Thing]

LOL

 

[Quest10n]

yep, about right! But I managed to fix my problem! Its actually so simple to resolve, why I didn't do this earlier is beyond me!.........


.... I canceled and joined SAOL uncapped!

:wtf: is it that simple, i must do the same

 

[pierreSimons]

I'm about to start a 3GB download using neoflex , is that a good idea?

 

[Next Thing]

Not without a Very Very good download manager

 

[frobbertze]

yep, about right! But I managed to fix my problem! Its actually so simple to resolve, why I didn't do this earlier is beyond me!.........


.... I canceled and joined SAOL uncapped!

This seems to be the general solution to all neotel related problems these days.

 

[ebendl]

So this morning I decided to give my Windows 2003 server a skip and give a Windows XP machine a go. Turns out that
a) either Neotel has healed itself overnight
b) the wet weather is forming a special "conductive pipe" to my window and thus my Prime device
c) My Windows 2003 server caused endless disconnects and stalemates with no data coming through...
d) I like pickles.

I get a full download speed, constant connection now. It seems as if something went wrong with the Windows 2003 system. This leads me to believe that Neotel doesn't cater for Vista nor Server - only windows XP, as the most problems I had was on these two systems.

Will continue monitoring.

 

[medicnick83]

Will continue monitoring.

What a waste of your time...

I wouldn't bother, not anymore at least.

 

[ebendl]

What a waste of your time...

I wouldn't bother, not anymore at least.

I agree, but I am already stuck in it, don't want to pay for the device now and can't get ADSL since I am moving in a month or 2's time.

I just want this bloody connection to work, so anything that helps, well, helps.