On Wed, Feb 29, 2012 at 5:44 AM, Raffaele Morelli
wrote:
> 2012/2/27 Tom H
>> >> You have to use static ports for statd, mountd, and lockd if you're
>> >> not using nfsv4. (You don't have to use the same static assignments
>> >> used below.)
>> >>
>> >> - Set
>> >> STATDOPTS="--port 4003 --outg
2012/2/27 Tom H
> >> You have to use static ports for statd, mountd, and lockd if you're
> >> not using nfsv4. (You don't have to use the same static assignments
> >> used below.)
> >>
> >> - Set
> >> STATDOPTS="--port 4003 --outgoing-port 4004"
> >> in "/etc/default/nfs-common"
> >>
> >> - Set
>
On Mon, Feb 27, 2012 at 9:29 AM, Raffaele Morelli
wrote:
> 2012/2/27 Tom H
>>
>> On Mon, Feb 27, 2012 at 5:45 AM, Raffaele Morelli
>> wrote:
>> >
>> > I am setting up (tryin at least) a nfs mount on a remote machine,
>> > there's a
>> > firewall in between so I asked the net administrator to ope
2012/2/27 Tom H
> On Mon, Feb 27, 2012 at 5:45 AM, Raffaele Morelli
> wrote:
> >
> > I am setting up (tryin at least) a nfs mount on a remote machine,
> there's a
> > firewall in between so I asked the net administrator to open ports 111
> and
> > 2049 on the server.
> >
> > /etc/exports on the
On Mon, Feb 27, 2012 at 5:45 AM, Raffaele Morelli
wrote:
>
> I am setting up (tryin at least) a nfs mount on a remote machine, there's a
> firewall in between so I asked the net administrator to open ports 111 and
> 2049 on the server.
>
> /etc/exports on the server is
> /home/username/ CLIENT
Hi,
I am setting up (tryin at least) a nfs mount on a remote machine, there's a
firewall in between so I asked the net administrator to open ports 111 and
2049 on the server.
/etc/exports on the server is
/home/username/ CLIENT_IP(ro,sync)
mount command is
mount -v -t nfs REMOTE_IP:/home/use
Hi,
I am setting up (tryin at least) a nfs mount on a remote machine, there's a
firewall in between so I asked the net administrator to open ports 111 and
2049 on the server.
/etc/exports on the server is
/home/username/ CLIENT_IP(ro,sync)
mount command is
mount -v -t nfs REMOTE_IP:/home/use
I have a linux client that is mounting filesystems off of an ibm f50
running aix4.3.2.
The linux client can read from the aix box just fine, but when it
writes anything onto the nfs mounted drives, the writes are painfully
slow (68Kb/sec) on a 100Mb ethernet network.
I have read that this is due
>
>My 2 cents' worth on this one is that my (new) system had full NFS
>capability until I installed the netstd package, at which point I got the
>above message.
>
>Poking around showed that /etc/init.d/netstd__nfs had all 5 of the _start_
>lines commented out. I am a Unix dumbkov but uncommentin
On Wed, 21 Aug 1996, Scott J. Geertgens wrote:
>
> > >> I keep getting the following message when trying to NFS mount any of the
> > >> exported filesystems.
> > >>
> > >> mount clntupd_create: RPC: Program not registered
> > >>
> > >
> > >Check that on the nfs server that mountd is running.
> >> I keep getting the following message when trying to NFS mount any of the
> >> exported filesystems.
> >>
> >>mount clntupd_create: RPC: Program not registered
> >>
> >
> >Check that on the nfs server that mountd is running. This one is usually
> >NOT started from inetd but instead is st
Sherwood,
>> I keep getting the following message when trying to NFS mount any of the
>> exported filesystems.
>>
>> mount clntupd_create: RPC: Program not registered
>>
>
>Check that on the nfs server that mountd is running. This one is usually
>NOT started from inetd but instead is starte
Debian guru's,
Here I am again in need of some assistance with this new release. I've
been using NFS over a SLIP link to my laptop to access resources on the
Debian box (like the CDROM, etc) with the R6 distribution for several
months. Now, with 1.1 my laptop and another machine both using Mini
13 matches
Mail list logo
