New Here

I have had a somewhat similar experience. I get signal from the Forrest Town and Rosebank towers.

Forrest Town: -78db and 0 - 1 load (good signal and good tower)
Rosebank: -80db and 2 - 3 load (good signal and bad tower)

For some reason, Forrest Town's signal will sometimes weaken to -85 which makes me connect to Rosebank. All well and good except that Rosebank is overloaded to the point of standstill during the day.

I only managed to figure out that Rosebank was a problem once I got UTTRace* working. My solution was to focus signal on Forrest Town only.

Now I suspect that, that is what is happening to you. I think that without UTTrace* working it would be impossible to get an idea of where your best signal is. Have you got a friend with IBurst or a reseller that can bring their UTTrace* compatible modem in and help you to setup UTTrace* and find your sweet spot?

I think you said that you get 90% - 100% connection according to the IBurst software. I stand corrected but I think that if you don't get 100% signal from IBurst then you have terrible signal.

Good luck.
 
I think anything above 80% on iBursts monitoring is still acceptable. A bigger problem would be 3 load.

We really have to try figure out if the new modems work for any of these apps, if they dont, then someone needs to lend Seburn one of the new modems and he can hopefully make UTt* compatible.
 
Please can somebody with utTraceStar working download and run this application (port scanner) ...(which btw is quite wicked :) ) http://www.dirfile.com/advanced_port_scanner.htm on the ip 192.168.250.10.

Then can I ask ekkesa to run this to and I can compare results.

I don't have utd available at moment ... I only get it for limited timespans.

I tested the port scan and it seems to be working.
 
IF you are connecting to the randburg tower it would explain the problem you have been have. I know that I connect to it with at least 7/10 sometimes 9/10 rating but can't stay connected or download anything during the day. If I place my modem so that it connects to another tower 5/10 but not as well I get better speed and stay connected, stupid! :rolleyes:
Although it does seemed to have improved today but there is or was definitely something wrong with that tower.
 
The stickied posts on this iBurst forum. They are the posts that say sticky in front of them and stay right at the top of the forum all the time.

The ones you are looking for are UTtracestar, iConnect and eyeBurst.

UTtracestar is generally supposed to be best, but you need th e.Net framework, and eyeBurst is in Java so it works on any OS.
 
Rant

Hey folks,

Just a thought......even though I'm in the expert hands of Seburn and the other gurus here.....should I have to ask your help and take your time to get something I have payed hard-earned cash for to work?...BTW - at exhorbitant costs compared to the rest of this good planet we inhabit together.

In my profession I give the clients/customers what they paid for - to the best of my ability....they don't have to download apps. and tweak what I give them....it's exactly what they commisioned me for.

Example - tonight I'm getting between 1.2 and 3 kBs/sec and getting kicked off every 3 mins or so.....not much better than my old 56k modem....fantastic huh?
 
Wow, some people really have problems with tier iBurst.. 1.2-3kb? And disconnects?

I dont know if ive ever been disconnected while the tower is up...

Are those towers really that bad? I can at least get around 50kb during the day.
 
seburn said:
Please can somebody with utTraceStar working download and run this application (port scanner) ...(which btw is quite wicked :) ) http://www.dirfile.com/advanced_port_scanner.htm on the ip 192.168.250.10.
Click to expand...

When I set IP to 192.168.250.10 (Iburst Modem) I get no open ports.
On 192.168.250.1 (my PC's NIC connected to the Iburst Modem) I get 3 open ports and 64 closed ports from the default port list.

utTraceSTar working fine.
 
Ja, I was under the impression that it should be port 192.168.250.1 as well...
but I thought id rather trust Seburn...
Okay and here are my results too: I get 9 ports open, 58 closed.

the open ports are very interesting.. The only open ports are 80, 25 ,110 which is web surfing and mail. Then 8080 for a proxy, and 3128 for their squid proxy. Then 135, 139 and 445 for DNS and netbios. And 1080 for socks.
 
Last edited:
iBurst modem command port listens on 192.168.250.10 port 1234, the modem does not respond to anything else (e.g. ping). The easiest way to test communication is to telnet 192.168.250.10 1234 from a directly connected PC (Ethernet easiest - no drivers) with an IP address of 192.168.250.x (but NOT 10) and a mask of 255.255.255.0. If this succeeds (some funky text on screen), the signal monitoring tools should work.

One way of checking that your PC and modem are on the same physical network is to ping 192.168.250.10 (it will fail) then do an 'arp -a' and you should see a dynamic MAC address in your arp table for 192.168.250.10.
 
How did Gres find out the port number then?

I was told Ekkese could Ping modem on 192.168.250.10 - get good replies from it?

Ekhaatvensters ... on 192.168.250.10 ??? 9 open ports (and no 1234) very strange and GC none.

Seems like this is not the solution to test the new modems, Maybe try roman4604's method. But this will not tell us if they changed the port.
 
seburn said:
I was told Ekkese could Ping modem on 192.168.250.10 - get good replies from it?
Click to expand...

Hi,

I get very good ping replies from the modem, but cant connect to it. Will run the port scan and send my results.
 
You should find TCP port 1234 active/listeneing on the iBurst modem if you do a port scan on it. If you didn't, you couldnt telnet it.

Either the scanning sw is junk or ppl are getting confused with instructions and setting either PC or router (WAN inf) to 192.168.250.10, thereby duplicating the iBurst modem's IP. If the duplicated device's arp response is faster than the modem's, the PC will assume .10 resides on that device instead of the modem.

BTW Seburn the one thing that still limits the usefullness of the likes of uttracestar is that it doesnt report FER%. It's gotta be there somewhere if the iBurst client can retrieve it. Any progress on that front?
 
Last edited:
I searched very far into the commands and found nothing. It might be possible they are using an unrelated method to find this value based on tcp traffic.
 
seburn said:
It might be possible they are using an unrelated method to find this value based on tcp traffic.
Click to expand...
I'm convinced it has to be somewhere on the air interface level.

If one start a continous ping (IP level) and are running some % of FER, the IP stack never reports that packets are lost/corrupt. All that happens is the latencies increase as the air interface retransmitts the corrupt packets in the backround without IP's knowledge.

I think the only way to get to the bottom of this is with a USB protocol decoder to see how the iBurst client does it. Might give it a try one day if I get the urge.
 
robhk again

I must be fair to iBurst.......loading this forum's home page - 31.8 secs.

This page - 28.9 secs - so I checked my bandwidth monitor.......

Two nights ago 500+ meg.....tonight - zero, nada, zilch....and I haven't downloaded anything at the speeds I'm getting.

Looks like a screw-up with my account....will check on Monday. Explains the snail speeds and being kicked off every couple of minutes.

Keep the faith folks !!!!
 
Actually it doesn't explain that... your capped speeds of 64kb is fine for browsing, especially a low-image local site, it should open almost as fast as uncapped.

But it would explain your terrible speed when downloading.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X