Firmware? ProAsm?

Heya, no, not technical like the ROUTER help etc

Just wondering why can't the modem's firmware do a test connect to a tower it finds, then if it gets the infamous remote computer did not respond error, to simply start looking for a different tower and then re-try its connection?

Why do you have to "put your two cents in"... but it's only a "penny for your thoughts"? Where's that extra penny going to?

Well no1 bothers to read the read the technical thread

Save a horney friend........

Durban Mal Park(36) 53% sig 128k

The actual "Remote computer did not respond" is a PPP negotiation problem, typically when the nodeB has gotten isolated from the upstream network controller.

PPP happens on your PC, the modem doesn't even have a clue how to do PPP, so it'd be rather difficult for it to do this kind of test.

If the little PXA255 were running linux though, this would have been doable. One thing is definate though. The firmware needs a method for latching on to a specific tower/frequency. That easily the most crucial feature that IPW has forgotten about.

<center><h6> MyWireless <s>Hacks</s> Tweaks & Tech Info || Have you checked the fawking FAQ? <br /> <font color="red">Tired of bad Service? Want to compare speeds? We at least listen...</font id="red"></h6></center>

I'm not an Expert on this, but as TheRodent stated, the PPP part takes place on your PC.
The "Remote computer did not respond" Error has occurred to me at work, and at home multiple times, and 9/10 it was something to do with my PC/Modem.

I have seen that alot of times, especially through the USB connections (on Adsl and on Mywireless modems), it is the computers internal error. Normally restarting your PC, Resetting the modem, even in severe cases, reinstalling the modem. Fixes the "Remote computer did not respond" problem.

But as I said, im no expert. Just an observation.

35% Signal
[36]Scummyside

The "remote computer did not respond" is a PPP layer error. It means that PPP couldn't authenticate, which means that either the nodeB couldn't talk to the network controller, the authentication service is down, or there is a PPP configuration problem.

In 99% of cases it's the nodeB-&gt;network controller problem i.m.o and 99% of the time this happens during "unscheduled-with-users" scheduled maintenance.

<center><h6> MyWireless <s>Hacks</s> Tweaks & Tech Info || Have you checked the fawking FAQ? <br /> <font color="red">Tired of bad Service? Want to compare speeds? We at least listen...</font id="red"></h6></center>

yes, what he said....

my head hurts.

35% Signal
[36]Scummyside

<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by TheRoDent</i>
<br />The "remote computer did not respond" is a PPP layer error. It means that PPP couldn't authenticate, which means that either the nodeB couldn't talk to the network controller, the authentication service is down, or there is a PPP configuration problem.
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">
Alternatively, also on the PPP layer, the error can simply be that one is too far to handshake with the tower.
modem sends connect request, tower doesn't recieve -&gt; doesn't send ack -&gt; dialler times out with remote computer did not respond.