[Simh] Unable to telnet to other hosts

[priya chincholikar]

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 <
Mark at infocomm.com> 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:* simh-bounces at trailing-edge.com [mailto:
> simh-bounces at trailing-edge.com] *On Behalf Of *Christopher Myers
> *Sent:* Tuesday, November 05, 2013 7:55 AM
> *To:* priya chincholikar
> *Cc:* simh at trailing-edge.com
>
> *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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20131107/e6420816/attachment-0002.html>