Remote host did not Respond Error

[stoke]

Remote host did not Respond Error [On Connect]

A friend of mine had been using a new ibust modem - all woz fine.

He uses the modem at work and at home.

On Monday (At work) - when connecting - it started with "Remote host did not Respond Error."

After calling WBS and playing and begging and kicking, nothing.

When he got home, it woz the same error despite having worked fine on sunday night.

So - he reinstalled the drivers - USB - and it immediately worked 100%.'
At work this morning, everything still 100%.

Wierd.
My guess is something to do with Over-The-Air firmware updates?

 

[slimothy]

those over the air updates are long over and its got nothin to do with drivers.
Which host was he trying to contact because it could be that the host is down or a node between your friend and the host (or many hosts) may be down and theres no way round. Of course it could be WBS's shaping policies, I have sometimes noticed packets get dropped when requesting certain dynamic files, although it has become pretty rare since 2 weeks back.

Can you try ping the host and paste the results, because that will let you know whats happening on a network level, if it says no route to host then a node is down or he isn't connected, if it says something like 84.75.54.155 != blah.hostname.com
then it is a DNS error, either they are having problems with thier DNS server (they being the host) or they are waiting for the main internic database to update with new IPs, which can take anywhere from 1 - 48 hours depending on where it is in the world.

The other options is that the host may be down, you can establish this by pinging it and getting a Request Timed Out message, of cours ehtis doesn't always mean the host is down, it could be that your friends connection is down, but he can test that by pinging some server you know is never down like google.com, if you get responses from google and request timed out from the other server the other server is down.

If you get responses from the host but still can't access thje service it could be that the service you are trying to use is blocked by a firewall or router or the software that runs it is skitzing.

Also what software is he using, has he tried alternatives and is he running windows XP SP2?

 

[stoke]

Slim - you've gone too far - couldn't even get a connection up and running. The error occirs on the CONNECT. Sorry - wazn't clear.

And WBS said that there were no problems with the towers.

And - cos the modem was new, I don't think that the firmware updates can be excluded as an option, I doubt the new modems provided by WBS already have the firmware installed.

Win XP SP2.

 

[gigtech]

haha, good time to format