Discussion:
Connection refused, lost or timed out
(too old to reply)
Robin Edwards
2007-02-12 20:44:32 UTC
Permalink
Hello again,

Now a couple of hours since I tried to connect. Same problem, though.

Voyager's log now starts with "Can't resolve smtp.orpheusnet.co.uk"
then "Can't resolve fleece.argonet.co.uk"
then "...same again.... "
then "Can't resolve pop.orpheusnnet.co.uk"

each with "Closing down" after them.

Suppose it must be a substantial problem somewhere :-((

Looking forward to getting on line again!

Cheers, Robin
--
Robin Edwards

- still supplying "1st" - the only real statistical software
for RISC OS
Paul Vigay
2007-02-13 21:37:21 UTC
Permalink
Post by Robin Edwards
Voyager's log now starts with "Can't resolve smtp.orpheusnet.co.uk"
then "Can't resolve fleece.argonet.co.uk"
then "...same again.... "
then "Can't resolve pop.orpheusnnet.co.uk"
each with "Closing down" after them.
Suppose it must be a substantial problem somewhere :-((
Unfortunately that problem lies with your machine somewhere. :-(

When this occurs, try pressing f12 and typing *show inet* and press return.

What output do you get? Specifically, what's the inet$resolvers value?

it should be 213.130.128.32 213.130.128.33

If not, Voyager has become corrupted, or you've got a clash in the main
RISC OS !Boot networking side of things.

See the first issue discussed at
http://www.orpheusinternet.co.uk/support/riscos/voyager/problems.html for
more information, and a solution.

Paul
Robin Edwards
2007-02-14 21:23:58 UTC
Permalink
Post by Paul Vigay
Post by Robin Edwards
Voyager's log now starts with "Can't resolve smtp.orpheusnet.co.uk"
then "Can't resolve fleece.argonet.co.uk"
then "...same again.... "
then "Can't resolve pop.orpheusnnet.co.uk"
each with "Closing down" after them.
Suppose it must be a substantial problem somewhere :-((
Unfortunately that problem lies with your machine somewhere. :-(
Added later:- though I got through to the "Connecting..." message,
which I thought meant that I'd reached the remote machine. Maybe I'm
suffering from delusions ;-)
Post by Paul Vigay
When this occurs, try pressing f12 and typing *show inet* and press return.
What output do you get? Specifically, what's the inet$resolvers value?
it should be 213.130.128.32 213.130.128.33
Hi, Paul! I get exactly this, but as you will have realised the system
is working again! It remains a profound mystery to me. I've done
nothing to the machine or software except to switch it off for the
night. This morning (or was it yesterday morning?) everything worked
perfectly, as normal. My telephone line has been perfect too, as far as
I can tell.
Post by Paul Vigay
If not, Voyager has become corrupted, or you've got a clash in the
main RISC OS !Boot networking side of things.
See the first issue discussed at
http://www.orpheusinternet.co.uk/support/riscos/voyager/problems.html
for more information, and a solution.
Haven't been there yet - out all day today and busy with other things
when I got back. Will no doubt see you at The Webbington shortly :-)

Cheers,

Robin
--
Robin Edwards

- still supplying "1st" - the only real statistical software
for RISC OS
Loading...