All of the ports are in /etc/services correctly on the server.
Running cmon on the server trying to connect to itself, I get the
following:
tcpdump shows:
tcpdump: listening on lo0
13:03:49.296472 localhost.1210 > localhost.codasrv: udp 292
13:03:49.296504 localhost > localhost: icmp: localhost udp port codasrv
unreachable
Why it would be unreachable is a mystery... netstat -a shows (relevant
lines only):
udp4 0 0 *.rpc2portmap *.*
udp4 0 0 *.codaauth2 *.*
udp4 0 0 Clarke.codasrv-se *.*
udp4 0 0 Clarke.codasrv *.*
Aha. Running cmon from a machine other than the server works. Is there
some restriction against accepting connections from localhost (i.e. in a
bind() call)?
Now on to see if I can get the rest running...
Kenneth
On Fri, Nov 10, 2000 at 12:10:01PM -0500, Jan Harkes wrote:
> On Wed, Nov 08, 2000 at 12:12:56PM -0700, Kenneth Ingham wrote:
> > So, why does cmon imply the server is not running? I can use cmon to
> > connect to testserver.coda.cs.cmu.edu and get data.
> >
> > Kenneth Ingham
> > [EMAIL PROTECTED]
>
> Cmon simply sets up an rpc2 connection with the server and calls
> ViceGetStatistics. I don't know why it fails to connect.
>
> Check whether following ports are correct on the server (in /etc/services),
>
> rpc2portmap 369/udp
> codaauth2 370/udp
> venus 2430/tcp
> venus 2430/udp
> venus-se 2431/udp
> codasrv 2432/udp
> codasrv-se 2433/udp
>
> If they are, use tcpdump (or rpc2tcpdump) on the client to see what
> server it is trying to connect to and whether any responses are
> received.
>
> Jan
>
>
