Adrian Partridge wrote:
> #1) Changed the reslvcnf.net.sys file
>
> domain earth.milkyway.space        {this is what is configured under NMMGR}

While this is cute, it's not (yet) a valid DNS domain.  But there are people at
NASA working to make this happen.  ;-)

See http://www.bixby.org/mark/sendmailix.html under "System Requirements"
regarding DNS and hostnames and domain names.  You want "domain" in RESLVCNF to
be the same as the actual DNS domain (note: NOT an NMMGR "domain"!) in which
your 3000 resides.

But I don't think this is your problem, since I can change my own machine to
earth.milkyway.space in RESLVCNF and it still seems to work OK.

...snip...

> #2b) telnet.arpa.sys "tower.netlink.co.uk"
> Telnet Client [A6000000]     (C) Hewlett-Packard Co. 1994
> tower.netlink.co.uk: Host name lookup failure

...snip...

> #6) xeq ftp.arpa.sys tower.netlink.co.uk.
> File Transfer Protocol [A0009001] (C) Hewlett-Packard Co. 1990
> Cannot connect to host: tower.netlink.co.uk.  (FTPERR 9)

At least it's consistent.

What happens if you try the following (ignore the lost packets; my ISP is
having problems this morning)?:

:xeq nettool.net.sys "ping;ping www.gainsborough.com;quit"
NETTOOL Version:      B06000A1

 Enter HELP HELP for an explanation of the help facility.

 Enter HELP OPERATION for guidance on NETTOOL use.

 Commands can be abbreviated, HELP keywords cannot.

 Menu-specific commands for the ROOT:

>>>ping
>>>ping
Name or Address of destination:WWW.GAINSBOROUGH.COM
Sending -----------------------------------------
5 packets of 64 bytes to WWW.GAINSBOROUGH.COM
------------------------------------------

Pinging WWW.GAINSBOROUGH.COM
64 bytes from 194.88.140.9   : icmp_seq=    3 time=  671 ms
64 bytes from 194.88.140.9   : icmp_seq=    4 time=  649 ms
64 bytes from 194.88.140.9   : icmp_seq=    5 time=  594 ms

------------- FINAL STATISTICS -------------
5 packets transmitted, 3 packets received,40 % packet loss
round-trip (ms) min/avg/max = 594/638/671

>>>quit
:

- Mark B.