Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Aug 2004 13:33:02 -0700
From:      Paredes =?UNKNOWN?Q?S=E1nchez_Mart=EDn_A=2E?= <mparedes@telmex.com>
To:        "BSD." <FreeBSD-Questions@FreeBSD.org>
Subject:   What is portmapper (I  MUST have portmapper running to use pcnfsd)
Message-ID:   <E3F56D7842656F4484C5668BC4D7F29849D8CD@is~tmxmailhmo1.intranet.telmex.com>

next in thread | raw e-mail | index | archive | help

Hi :

I am trying to replace a sparcstation which has solaris 2.5, we use it
to boot some diskless pc's into MS-DOS 6.22 and mount a file system in
the disk C: of the pc with PC/TCP 4.1.

The boot process I had figured out, but the connection of the drive C:
to the file system is given me problems.

The problem I think is that I don't have running something called
portmapper.

Since I am not subscribed to the list, please send me a copy of your
answer.

Let me explain why I think that, I decide that I have to use tcpdump
to see what is happening.

The diskless is booting with the ip 10.115.44.50

# tcpdump -n ip host 10.115.44.50
tcpdump: listening on xl0
03:44:04.337343 10.115.44.50.603 > 10.115.44.245.111: udp 56
03:44:04.337379 10.115.44.245 > 10.115.44.50: icmp: 10.115.44.245 udp
port 111 unreachable
03:44:04.340453 10.115.44.50.604 > 10.115.44.245.111: udp 56
03:44:04.340465 10.115.44.245 > 10.115.44.50: icmp: 10.115.44.245 udp
port 111 unreachable

So, mi diskless is trying to connect to the port 111/udp, and my
services files says:

sunrpc          111/tcp    rpcbind      #SUN Remote Procedure Call
sunrpc          111/udp    rpcbind      #SUN Remote Procedure Call

And the inetd.conf does not have nothing called sunrpc or rpcbind,
but has the nexts lines:

******************************************************************
#
# RPC based services (you MUST have portmapper running to use these)
#
#rstatd/1-3     dgram rpc/udp wait root /usr/libexec/rpc.rstatd
rpc.rstatd
#rusersd/1-2    dgram rpc/udp wait root /usr/libexec/rpc.rusersd
rpc.rusersd
#walld/1        dgram rpc/udp wait root /usr/libexec/rpc.rwalld
rpc.rwalld
#pcnfsd/1-2     dgram rpc/udp wait root /usr/libexec/rpc.pcnfsd
rpc.pcnfsd
#rquotad/1      dgram rpc/udp wait root /usr/libexec/rpc.rquotad
rpc.rquotad
#sprayd/1       dgram rpc/udp wait root /usr/libexec/rpc.sprayd
rpc.sprayd
******************************************************************

What is the portmapper and how can I run it?, Do I have to uncomment the
pcnfsd line?.

I notice that the program rpc.pcnfsd is the only rpc program that is not
installed

# ll /usr/libexec/rpc.*
-r-xr-xr-x  1 root  wheel  7068 May 25 14:28 /usr/libexec/rpc.rquotad
-r-xr-xr-x  1 root  wheel  9380 May 25 14:28 /usr/libexec/rpc.rstatd
-r-xr-xr-x  1 root  wheel  6808 May 25 14:28 /usr/libexec/rpc.rusersd
-r-xr-xr-x  1 root  wheel  6176 May 25 14:28 /usr/libexec/rpc.rwalld
-r-xr-xr-x  1 root  wheel  4628 May 25 14:28 /usr/libexec/rpc.sprayd

So, I instaled.

# cd /cdrom/packages/All
# pkg_add pcnfsd-93.02.16.tgz
# pkg_info|grep pcnfsd
pcnfsd-93.02.16     Sun PC NFS authentication and printing server

# pkg_info -L pcnfsd-93.02.16
Information for pcnfsd-93.02.16:
/usr/local/libexec/rpc.pcnfsd
/usr/local/man/man8/pcnfsd.8.gz

I notice that pcnfsd has installed in /usr/local/libexec/, which is
diferent
to /usr/libexec/, Do I need to modify inetd.conf?

When I check the man page for inetd.conf I found this about RPC-based
services
that I belive they are TCP-MUX services.

******************************************************************
     To specify an ONC RPC-based service, the entry would contain these
     fields:

           service name/version
           socket type
           rpc/protocol
           user[:group][/login-class]
           server program
           server program arguments

     There are two types of services that inetd can start: standard and
TCP-
     MUX.  A standard service has a well-known port assigned to it; it
may be
     a service that implements an official Internet standard or is a
     BSD-specific service.  As described in RFC 1078, TCPMUX services
are non-
     standard services that do not have a well-known port assigned to
them.
     They are invoked from inetd when a program connects to the
``tcpmux''
     well-known port and specifies the service name.  This feature is
useful
     for adding locally-developed servers.  TCPMUX requests are only
accepted
     when the multiplexor service itself is enabled, above and beyond
and spe-
     cific TCPMUX-based servers; see the discussion of internal services
     below.
******************************************************************

TIA
maps






*************************************************************************=
*************************************************************************=
*********************
Contrata Prodigy Infinitum y navega a Infinitum de velocidad sin ocupar =
tu tel=E9fono. Adem=E1s, ll=E9vate 1 mes de renta Gratis y Prodigy =
M=F3vil,=20
para que navegues en sitios p=FAblicos sin cables. =BFQu=E9 esperas? =
Con=E9ctate  al 01 800 123 2222 o ven a tu Tienda Telmex. Precio m=E1s =
I.V.A.
http://www.hits.telmex.com/app/ad_Mgr/ad_mgrN.jsp?ad=3D166

Prodigy Infinitum la conexi=F3n m=E1s r=E1pida

Asom@te a telmex.com  http://www.telmex.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi? <E3F56D7842656F4484C5668BC4D7F29849D8CD>