Could be a DNS configuration problem.
What does
$ MULT NSLOOKUP LOCALHOST
show? or
$ MULT DIG LOCALHOST

I did a lookup on your posting headers and got the following:
$mult nslookup mac.sture.homeip.net
Server: LOCALHOST
Address: 127.0.0.1

Non-authoritative answer:
Name: STURE.HOMEIP.NET
Address: 80.219.80.21
Aliases: MAC.STURE.HOMEIP.NET

LOCALHOST resolving to 127.0.0.1 is a convention - there is nothing special
in the name server to force that, it works via the same configuration that
all other translations go through.

"Paul Sture" wrote in message
newsaul.sture.nospam-73C62D.04191613092006@mac.sture.homeip.net...
> Hi folks.
>
> I've never used Multinet before, but decided to get a Hobbyist license
> and learn all about it (I previously had TCP/IP Services running).
>
> I'm sure I've made a basic config mistake here, but I can't see it...
>
> I've got it up and running OK, but...
>
> $ telnet localhost
> Trying... [80.219.80.21] %MULTINET-F-ECONNREFUSED, Connection refused
>
> (it does the same if I use the short names to access itself or
> my Mac)
>
> Now, this system is behind a router at 192.168.1.1, so it shouldn't be
> going to the outside world at all.
>
> Config details:
>
> $ mult show/route
> MultiNet IP Routing tables at 13-SEP-2006 03:47:32.79:
> Destination Gateway Flags Refcnt Use Interface
> MTU
> ---------- ---------- ----- ------ ----- ---------
> ----
> DEFAULT-GATEWAY 192.168.1.1 U,G,S 3 5702 se0
> 1500
> LOCALHOST LOCALHOST U,H,Local 3 7629 lo0
> 4168
> 192.168.1/24 DINA.STURE.HOMEI U 3 0 se0
> 1500
>
> $ type hosts.local
>
> ; Local network definitions
> ;
> NET : 0.0.0.0 : DEFAULT-GATEWAY :
> NET : 127.0.0.0 : LOOPBACK-NET :
> ; Local host definitions
> ;
> HOST : 127.0.0.1 : LOCALHOST : : : :
>
> HOST : 192.168.1.22 : DINA.STURE.HOMEIP.NET,DINA : PWS-600AU : VMS : :
> HOST : 192.168.1.41 : MAC.STURE.HOMEIP.NET,MAC : APPLE-IBOOK : OS-X : :
>
> Any pointers gratefully received.
>
> --
> Paul Sture

In article ,
"Richard Whalen" wrote:

> Could be a DNS configuration problem.

It looks like it. I was hoping to just set up the local names and then
tackle DNS later.

> What does
> $ MULT NSLOOKUP LOCALHOST

$ mult nslookup localhost
Server: LOCALHOST
Address: 127.0.0.1

Non-authoritative answer:
Name: sture.homeip.net
Address: 80.219.80.21
Aliases: LOCALHOST.sture.homeip.net

But if I substitute a non-existent node name, it gives the same.

It's as if it's completely ignoring the contents of my HOSTS.LOCAL, (and
yes, I have compiled it and done @ INSTALL_DATABASES).

> show? or
> $ MULT DIG LOCALHOST
>
> I did a lookup on your posting headers and got the following:
> $mult nslookup mac.sture.homeip.net
> Server: LOCALHOST
> Address: 127.0.0.1
>
> Non-authoritative answer:
> Name: STURE.HOMEIP.NET
> Address: 80.219.80.21
> Aliases: MAC.STURE.HOMEIP.NET
>
> LOCALHOST resolving to 127.0.0.1 is a convention - there is nothing special
> in the name server to force that, it works via the same configuration that
> all other translations go through.


Perhaps the use of localhost was a red herring. I am actually trying to
do something like $ telnet mac.

--
Paul Sture