Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!mit-eddie!uw-beaver!cornell!batcomputer!feigin
From: feigin@batcomputer.tn.cornell.edu (Adam Feigin)
Newsgroups: comp.sys.apollo
Subject: Re: TCP/IP 3.1 hangs on rsh
Message-ID: <5892@batcomputer.tn.cornell.edu>
Date: 11 Aug 88 16:46:09 GMT
References: <5400029@iuvax> <5400031@iuvax>
Reply-To: feigin@tcgould.tn.cornell.edu (Adam Feigin)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 41

In article <5400031@iuvax> jec@iuvax.cs.indiana.edu writes:
>
>	I've noticed that ping also has some problems:  If you ping an
>Apollo the first attempt will usually fail, but after that ping seems
>to work.  
>
>	For instance the first time I try it:
>
>[root@io:33]ping charybdis
>PING charybdis.cs.indiana.edu: 56 data bytes
>Timed out (1 second) waiting for echo reply		<--- fails
>64 bytes from 98.0.0.38: icmp_seq=1. time=154. ms	<--- passes
>  ....
>	The second time, however:
>
>[root@io:36]!ping
>ping charybdis 
>PING charybdis.cs.indiana.edu: 56 data bytes
>64 bytes from 98.0.0.38: icmp_seq=0. time=23. ms	<--- passes

I dont seem to have this problem. Perhaps you need to set some options on your
tcp_server when you start it up. You probably have the timeout option set too
low.

apollo.lap csh[7]: ping gulag.sovcen 56 10
PING gulag.sovcen.upenn.edu: 56 data bytes
64 bytes from 128.91.17.137: icmp_seq=0. time=674. ms
64 bytes from 128.91.17.137: icmp_seq=1. time=11. ms
64 bytes from 128.91.17.137: icmp_seq=5. time=11. ms
.....


						Adam
------------------------------------------------------------------------------
Internet: feigin@tcgould.tn.cornell.edu		Adam Feigin
Bitnet: feigin@crnlthry				Workstation Consultant
UUCP: {backbones}!cornell!batcomputer!feigin	Cornell National Supercomputer
MaBell: (607) 255-3985				Facility, Visualization Group

		"Sometimes a little brain damage can help"
------------------------------------------------------------------------------