According to his first post he's already configured TCPIP, but it wouldn't hurt to ask.
Priya, have you run "@SYS$MANAGER:TCPIP$CONFIG" to configure TCPIP? I'm assuming also, that you already tried to input a host using the "SET HOST" command and you entered "SHOW HOST" and got the error. Try what David suggested. On Thu, Nov 7, 2013 at 8:26 AM, David Holland <[email protected]>wrote: > The error implies he doesn't have a local hosts database file. > > This is what's on one of my systems: > > $ show log TCPIP$HOST > "TCPIP$HOST" = "SYS$COMMON:[SYSEXE]TCPIP$HOST.DAT;1" (LNM$SYSTEM_TABLE) > $ type TCPIP$HOST > 127.0.0.1 LOCALHOST > <etc> > > I *think* running @SYS$MANAGER:TCPIP$CONFIG and configuring the > primary interface should have added a hostname/IP address alias to the > local hosts database file. Its been a long time since I had to do > reconfigure it. I'd say run it again, and poke around in the core > environment menu. > > I think you can also create a hosts database with the TCPIP command, > and the "CREATE HOST" sub-command. > > See: > http://h71000.www7.hp.com/doc/83final/6524/6524pro_002.html > > David > > > On Thu, Nov 7, 2013 at 8:01 AM, Mark Pizzolato - Info Comm > <[email protected]> wrote: > > Hi Priya, > > > > > > > > I suggest you look at the details Christopher Myers provided. > > > > > > > > I have almost no experience with VMS TCP/IP Services. I have always > been a > > MultiNet user. > > > > > > > > Good Luck. > > > > > > > > - Mark > > > > > > > > From: priya chincholikar [mailto:[email protected]] > > Sent: Thursday, November 07, 2013 4:48 AM > > To: Mark Pizzolato - Info Comm > > Cc: Christopher Myers; [email protected] > > > > > > Subject: Re: [Simh] Unable to telnet to other hosts > > > > > > > > Hi, > > > > How do I make this work ? > > > > > > > > $ tcpip > > > > TCPIP> sh host > > > > %TCPIP-E-HOSTERROR, cannot process host request > > > > -TCPIP-E-NOFILE, cannot access TCPIP$HOST database file > > > > -RMS-E-FNF, file not found > > > > %TCPIP-E-HOSTERROR, cannot process host request > > > > -TCPIP-E-NOFILE, cannot access !AS database file > > > > > > > > -Priya > > > > > > > > > > > > On Thu, Nov 7, 2013 at 5:35 PM, priya chincholikar <[email protected] > > > > wrote: > > > > Hi, > > > > > > > > I'm having a weird problem now. > > > > I'm able to ping but cannot use telnet. I have a feeling I did something > > wrong during tcpip configuration. > > > > > > > > $ telnet 192.168.0.37 > > > > %TELNET-E-IVHOST, Invalid or unknown host 192.168.0.37 > > > > -TCPIP-E-NO_RECOVERY, unexpected name server failure > > > > ford/system$ tcpip > > > > TCPIP> ping 192.168.0.37 > > > > PING 192.168.0.37 (192.168.0.37): 56 data bytes > > > > 64 bytes from 192.168.0.37: icmp_seq=0 ttl=64 time=0 ms > > > > 64 bytes from 192.168.0.37: icmp_seq=1 ttl=64 time=0 ms > > > > 64 bytes from 192.168.0.37: icmp_seq=2 ttl=64 time=0 ms > > > > 64 bytes from 192.168.0.37: icmp_seq=3 ttl=64 time=0 ms > > > > > > > > > > > > ----192.168.0.37 PING Statistics---- > > > > 4 packets transmitted, 4 packets received, 0% packet loss > > > > round-trip (ms) min/avg/max = 0/0/0 ms > > > > TCPIP> > > > > TCPIP> exit > > > > > > > > - Priya > > > > > > > > On Tue, Nov 5, 2013 at 10:20 PM, Mark Pizzolato - Info Comm > > <[email protected]> wrote: > > > > Hi Chris, > > > > > > > > On Priya’s system either eth0 or em1 would produce the same results. The > > simh Ethernet generic naming paradigm makes this true. > > > > > > > > Priya’s first problem is that he can’t ping. I’ll step back once packets > > are moving on the wire. Once he can ping, your ideas may be relevant. > > > > > > > > - Mark > > > > > > > > From: [email protected] [mailto: > [email protected]] > > On Behalf Of Christopher Myers > > Sent: Tuesday, November 05, 2013 7:55 AM > > To: priya chincholikar > > Cc: [email protected] > > > > > > Subject: Re: [Simh] Unable to telnet to other hosts > > > > > > > > Hey, > > > > > > > > I think you're attaching the wrong Ethernet interface. > > > > > > > > You've got it set to 'em1' when > > http://www.wherry.com/gadgets/retrocomputing/vax-simh.html has it set to > > 'eth0.' Not sure if this is what the problem is, just something I > noticed. > > > > > > > > > > > > Also, just a heads up. I've had a somewhat similar problem on VAXStation > > 3100 running OpenVMS 7.3. > > > > > > > > I couldn't TELNET to hosts, but could ping them and the error I would > get is > > the same. > > > > > > > > -TCPIP-E-NO_RECOVERY, unexpected name server failure > > > > > > > > When I was trying to figure this out, I discovered that OpenVMS > apparently > > wants a name attached to that host. So you need to give 192.168.0.37 a > text > > name like "MYHOST" and then you'll be able to telnet with that name and > > (oddly) the IP address. > > > > > > > > What you need to do is go into the tcpip configuration program. > > > > > > > > $ TCPIP > > > > > > > > TCPIP> SET HOST MYHOST /ADDRESS=192.168.0.37 > > > > > > > > TCPIP> SHOW HOST > > > > > > > > This is how I fixed my little problem on real equipment. I had a working > > ping to a host, but no ability to TELNET. > > > > > > > > > > > > > > _______________________________________________ > > Simh mailing list > > [email protected] > > http://mailman.trailing-edge.com/mailman/listinfo/simh >
_______________________________________________ Simh mailing list [email protected] http://mailman.trailing-edge.com/mailman/listinfo/simh
