World: r3wp

Started, but not able to connect here.

What does your user list show?

it should show 98 users, 0 active.

It does.

ok, good, then there is a firewall or routing problem.

Gregg - not sure it will work on 5402, unless it registers itself 
on altme.com that way?

pekr, when you start the server, you effectively transmit that info 
to the altme world name server.

in worst case, we would have to wait 5-10 days for the timeout. But 
maybe, when starting a server, it will re-register the requested 
port, dunno ...

that is primarily why the world name server exists AFAIK.

It sometimes works and sometimes doesn't. Alt ports that is.

world name exists from the marketing purposes ;-)

I agree with Max, but there are other issues too. Need to check the 
info file.

simply check here,once you transfer and start it - http://www.altme.com/cgi-bin/lookup.cgi

FYI, it takes 10 days for world name passwords to reset when you 
last use it
(last paragraph here: http://www.altme.com/notes/lost-pass.html)

It says none of my worlds are available.

Including this one.

yeah, just got the same reaction.

Not a firewall issue.

And netstat says 5402 is listening.

The world name server still believes that the world ought to be served 
from Henrik's machine.

http://www.altme.com/cgi-bin/lookup.cgi?lookup=rebol4

hmm... that seems a bit silly. if you change your network provider, 
you can't serve anything.

I'm getting invalid user/pass now.

strange the lookup page is screwed up.

Are you running the server again?

I'm not...

This is odd. Now the world name is suddenly case sensitive again.

You should be able to just move and restart a server. 

I still can't connect at all, even on the server itself.

If I try "Rebol4", I get invalid password. If I try "rebol4", I get 
no connection.

Gregg, that's because the WNS did not yet refresh (for whatever reason).

Maybe there is a step missing and it simply can't show that the server 
is not running.

I think the only step missing is that the newly started server needs 
to refresh WNS.

aha... I ctrl-C'ed it, when I quit. maybe that's it?

going to start it and then quit it properly this time

now it responds correctly. you can try again, Gregg.

(lookup responds correctly)

I'm still trying. Don't know how to force a refresh to the WNS though.

I think you may have to start it once via the GUI and enter the password.

I can't start the world manually, because of the private pass issue, 
and the shortcut start doesn't seem to do it.

So we're back where we were.

private pass? are you trying from CLI?

Yes, CLI, since I don't have your pass to start it from the GUI.

so you need the password to switch to a different connection.

Give Henrik remote desktop access to the machine for a minute or 
two. Let him start the server once from the GUI, entering the password. 
WNS should refresh. Shutdown and start from CLI again.

what is WNS ?

This happen when the handshake protocol is not described anywhere, 
sucks big time, to do all the guesses.

The "world name server".

ah ok.

Give me a minute.

Done!