On Sat, Aug 20, 2022 at 06:21:21PM -0700, Wylie wrote:
>
> i am getting this error ... on a fresh install of nfs-kernel-server
>
> mount.nfs: access denied by server while mounting
> 192.168.42.194:/ShareName
>
> i'm not having this issue on other machines installed
i am getting this error ... on a fresh install of nfs-kernel-server
mount.nfs: access denied by server while mounting
192.168.42.194:/ShareName
i'm not having this issue on other machines installed previously
i've tried re-installing Debian and nfs several times
Wylie!
s
Executing /usr/sbin/update-rc.d rpcbind enable
Anything else to try?
>
> > then restart the nfs-kernel-server I can get it to work, but only if I
> > spell out the full ip address of the client. For instance if I put this
> > in /etc/exports it works:
> >
> &g
manually start rpcbind with
>
> $ sudo /etc/init.d/rpcbind start
This starts the service manually, but doesn't mark it for automatic
start. To do that, try:
$ systemctl enable --now rpcbind
> then restart the nfs-kernel-server I can get it to work, but only if I
> spell out t
be missing and I need help troubleshooting it.
> > >
> > > At first the NFS port 2049 was not even being opened. After much
> > > futzing around I discovered that if I manually start rpcbind with
> > >
> > > $ sudo /etc/init.d/rpcbind start
> > >
> &g
t the NFS port 2049 was not even being opened. After much futzing
> > around I discovered that if I manually start rpcbind with
> >
> > $ sudo /etc/init.d/rpcbind start
> >
> > then restart the nfs-kernel-server I can get it to work, but only if I
> > spell ou
discovered that if I manually start rpcbind with
>
> $ sudo /etc/init.d/rpcbind start
>
> then restart the nfs-kernel-server I can get it to work, but only if I
> spell out the full ip address of the client. For instance if I put this
> in /etc/exports it works:
>
&
start
then restart the nfs-kernel-server I can get it to work, but only if I
spell out the full ip address of the client. For instance if I put this
in /etc/exports it works:
/srv/export 192.168.1.1(rw,sync)
but not if I change it to this to allow other machines on the LAN to
mount (I get
or re-installing.
You could try downgrading through http://snapshot.debian.org/ or upgrading if
there are more recent versions of nfs-common and nfs-kernel-server in unstable
or experimental.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe&
On Mon, Mar 14, 2011 at 9:41 AM, Tom H wrote:
> On Sat, Mar 12, 2011 at 5:54 PM, Liam Cassidey
> wrote:
> >
> > ii portmap 6.0.0-2 RPC port
> mapper
>
> Remembered the above when I sent my last post and thought that I might
> have gone down an incorre
On Sat, Mar 12, 2011 at 5:54 PM, Liam Cassidey wrote:
>
> ii portmap 6.0.0-2 RPC port
> mapper
Remembered the above when I sent my last post and thought that I might
have gone down an incorrect path.
I've just tried to install pcbind and it conflicts
On Sat, Mar 12, 2011 at 5:54 PM, Liam Cassidey wrote:
>
> Some more debugging...
>
> I've narrowed down the error to the rpc.nfsd binary:
>
> server:~# rpc.nfsd -d
> rpc.nfsd: knfsd is currently down
> rpc.nfsd: Writing version string to kernel: +4.1 +2 +3 +4
> rpc.nfsd: Setting version failed: er
On Fri, Mar 11, 2011 at 5:49 PM, Liam Cassidey wrote:
> On Fri, Mar 11, 2011 at 11:01 AM, Tom H wrote:
>>
>> If "apt-get -f install" doesn't install and configure it fully,
>> "apt-get install --reinstall nfs-kernel-server" should.
>
> T
On Fri, Mar 11, 2011 at 10:49 PM, Liam Cassidey wrote:
>
>
> On Fri, Mar 11, 2011 at 11:01 AM, Tom H wrote:
>
>> On Thu, Mar 10, 2011 at 7:34 PM, Liam Cassidey
>> wrote:
>> >
>> > server:~# dpkg -l portmap nfs-common nfs-kernel-server
>
On Fri, Mar 11, 2011 at 11:01 AM, Tom H wrote:
> On Thu, Mar 10, 2011 at 7:34 PM, Liam Cassidey
> wrote:
> >
> > server:~# dpkg -l portmap nfs-common nfs-kernel-server
> > Desired=Unknown/Install/Remove/Purge/Hold
> > |
> >
> Status=Not/Inst/Conf-files/
On Thu, Mar 10, 2011 at 7:34 PM, Liam Cassidey wrote:
>
> server:~# dpkg -l portmap nfs-common nfs-kernel-server
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Sta
http://packages.debian.org/search?keywords=nfs-common, that this same
> version is also in stable. So I guess my next question is: has anyone had
> luck running an nfs server on any system since lenny? If so, what versions
> of the 3 (portmap, nfs-common, and nfs-kernel-server) are you runn
version 1:1.2.2-4 installed and it
appears, at least according to
http://packages.debian.org/search?keywords=nfs-common, that this
same version is also in stable. So I guess my next question is: has
anyone had luck running an nfs server on any system since lenny? If
so, what versions of the 3 (p
's been suggested that their may be a bug in the version of nfs-common I'm
using. I have version 1:1.2.2-4 installed and it appears, at least according
to http://packages.debian.org/search?keywords=nfs-common, that this same
version is also in stable. So I guess my next question is: has anyone h
On Wed, Mar 9, 2011 at 2:28 AM, Scott Ferguson
wrote:
> On 09/03/11 17:45, Liam Cassidey wrote:
>>
>> I've removed all entries from /etc/exports, have portmap and nfs-common
>> running, the firewall down, have an empty /etc/hosts.deny and a single
>> entry in hosts.allow (taken from the portmap ma
setting up
> an nfs export from the box. However, I'm unable to install nfs. The
> following happens when I attempt to install nfs-kernel-server.
>
> I've removed all entries from /etc/exports, have portmap and nfs-common
> running, the firewall down,
. The
following happens when I attempt to install nfs-kernel-server.
server:~# apt-get install nfs-kernel-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
nfs-kernel-server
0 upgraded, 1 newly installed,
On 09/03/11 17:45, Liam Cassidey wrote:
>
>
> I'm a bit at a loss here as I've never run into any problems setting up
> nfs mounts on other Unices or Linux distros. There is most likely
> something fundamental I'm missing, but I just can't put my finger on it.
> Any help would be appreciated.
g happens when I attempt to install nfs-kernel-server.
>>
>>
>> server:~# apt-get install nfs-kernel-server
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> The following NEW packages will be installe
On 03/07/2011 06:52 PM, Liam Cassidey wrote:
I'm running Debian unstable, and I'm interested in simply setting up
an nfs export from the box. However, I'm unable to install nfs. The
following happens when I attempt to install nfs-kernel-server.
server:~# apt-get install nf
I'm running Debian unstable, and I'm interested in simply setting up an nfs
export from the box. However, I'm unable to install nfs. The following
happens when I attempt to install nfs-kernel-server.
server:~# apt-get install nfs-kernel-server
Reading package lists... Done
Buil
Good morning.
The last days, i updated the dockstar to Debian Squeeze and nfs-kernel-server
works without any problems.
pgpTJdrliikbr.pgp
Description: PGP signature
Am 03.02.2011 21:37, schrieb Horst Schleicher:
> Hi Sascha,
>
> I got the same trouble installing the nfs-kernel-server on my dockstar
> with debian squeeze install. This already happens at the apt-get install
> stage and subsequent in the config.
>
> Here the output:
>
Hi Sascha,
I got the same trouble installing the nfs-kernel-server on my dockstar
with debian squeeze install. This already happens at the apt-get install
stage and subsequent in the config.
Here the output:
Setting up nfs-kernel-server (1:1.2.2-4) ...
Starting NFS common utilities: statd
Hello everyone.
I have a Seagate-Dockstar (Mini-PC) with 1.2GHz ARM CPU and 128MB RAM
running Debian Squeeze with kernel 2.6.32-5-kirkwood.
I had NFS running on this thing a few months ago, but now, it didnt
start anymore. So i purged it (including nfs-common, nfs-kernel-server,
portmap) and
in mind was to add the option -p PORTNUM to rpc.statd and
rpc.mountd in /etc/init.d/nfs-common and /etc/init.d/nfs-kernel-server.
This way you would have to specify in your firewall rules for the above
ports plus 111 for portmap and 2049 for rpc.nfsd. Unfortunately I have
just realized that it is
Ernest Johanson wrote:
Right. It can go in /etc/init.d or in /etc/network/interfaces. Probably
better in interfaces so the rules are applied as soon as the interfaces
are up.
I got the distinct impression that running firewall scripts using the
/etc/network/if-up.d and /etc/network/if-down.d dire
Right. It can go in /etc/init.d or in /etc/network/interfaces. Probably
better in interfaces so the rules are applied as soon as the interfaces
are up.
On Sat, 3 Jul 2004, Tom Allison wrote:
> Ernest Johanson wrote:
> > Good refinement to tighten things up.
> >
> >
>
> Thanks.
>
> I thought it w
Ernest Johanson wrote:
Good refinement to tighten things up.
Thanks.
I thought it would be necessary to re-run rpcinfo each time I booted
because I can't find anything that says these ports are a certainty.
That, and I only have NFS 3 support that I have to worry about.
# NFS
# First you open
Good refinement to tighten things up.
On Fri, 2 Jul 2004, Tom Allison wrote:
> Ernest Johanson wrote:
> > Been following this thread and understand that the goal is to configure a
> > firewall to control access to the ports used for NFS. If so, then suggest
> > the following:
> >
> > #!/bin/sh
>
Ernest Johanson wrote:
Been following this thread and understand that the goal is to configure a
firewall to control access to the ports used for NFS. If so, then suggest
the following:
#!/bin/sh
NFSPORTS=`rpcinfo -p | awk '/tcp/||/udp/ {print $4}' | sort | uniq`
for PORT_NUM in $NFSPORTS
do
On Fri, 2 Jul 2004, Tom Allison wrote:
> /etc/exports:
> /var/www192.168.1.0/24(rw,no_root_squash)
>
> These are identical on both machines
> /etc/hosts.allow is identical on both machines (empty)
to allow only certain machines to connect and disallow others
on the NFS server:
server
squash)
>
> These are identical on both machines
> /etc/hosts.allow is identical on both machines (empty)
>
> I've opened up port 111 (sunrpc) for both udp and tcp protocols
> and restarted both the port mapper and the nfs-kernel-server.
>
> Now I get iptables blocking on
--- [EMAIL PROTECTED] wrote:
> But I'm wondering what it is that I'm missing.
> Is this the difference between kernel and user nfs servers?
> Are there some args to pass at modprobe time?
Not in terms of options -- NFS configuration is done in the userland level
usually.
-- Thomas Adam
=
"
> On Fri, 02 Jul 2004 05:10:10 +0200, Tom Allison wrote:
>> Portmapper sits on one port, but it's redirecting the nfs connection all
>> over the place. I can't seem to nail it down to one set of ports.
>
> The only way I can think of sorting this out would be to allow any
> packets between the ser
On Fri, 02 Jul 2004 05:10:10 +0200, Tom Allison wrote:
> Portmapper sits on one port, but it's redirecting the nfs connection all
> over the place. I can't seem to nail it down to one set of ports.
The only way I can think of sorting this out would be to allow any
packets between the server and
entical on both machines
/etc/hosts.allow is identical on both machines (empty)
I've opened up port 111 (sunrpc) for both udp and tcp protocols
and restarted both the port mapper and the nfs-kernel-server.
Now I get iptables blocking on port 989/udp->989/udp (ftps-data) which
doesn't mak
er time with all the configuration options, but I don't really know.
I opened up port 111 for the sunrpc protocol, but that's as far as I got
with the firewall.
But I'm not really sure what I am supposed to do with this:
RPCMOUNTDOPTS=
in the /etc/defauls/nfs-kernel-server. I think
On Thu, 1 Jul 2004, Tom Allison wrote:
> Portmapper sits on one port, but it's redirecting the nfs connection all
> over the place. I can't seem to nail it down to one set of ports.
The rpc services called by portmaper can be binded to specific ports, see
man pages for details. To find out wha
Thomas Adam wrote:
--- Tom Allison <[EMAIL PROTECTED]> wrote:
What are my options?
Do I have to hard code the port number into the
/etc/default/nfs-kernel-server and the client fstab files and the
iptables script?
What about changing the port that portmapper listens on?
Portmapper s
--- Tom Allison <[EMAIL PROTECTED]> wrote:
> What are my options?
>
> Do I have to hard code the port number into the
> /etc/default/nfs-kernel-server and the client fstab files and the
> iptables script?
What about changing the port that portmapper listens on?
-- Th
tions?
Do I have to hard code the port number into the
/etc/default/nfs-kernel-server and the client fstab files and the
iptables script?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Emil wrote:
> someone please guide me in setup of NFS server.
apt-get install nfs-kernel-server
cat >> /etc/exports <
pgp0.pgp
Description: PGP signature
=?iso-8859-1?B?RW1pbCBI5Gdlcmx1bmQ= ?= said on Mon, Oct 27, 2003 at 02:00:38PM +0100:
> Thanks,
>
> is 'apt-get install nfs-kernel-server' enough
> or do I need to compile anything?
If you are using a Debian supplied kernel, installing nfs-kernel-server is
enough. If
Thanks,
is 'apt-get install nfs-kernel-server' enough
or do I need to compile anything?
Emil
--
__
Check out the latest SMS services @ http://www.linuxmail.org
This allows you to send and receive SMS through your mailbox.
Powered b
In article <[EMAIL PROTECTED]>,
Emil Hägerlund <[EMAIL PROTECTED]> wrote:
>someone please guide me in setup of NFS server.
>
>What is the difference between packages
>'nfs-kernel-server' and 'nfs-user-server'
>reagarding performance and config?
On Mon, 2003-10-27 at 01:59, =?iso-8859-1?B?RW1pbCBI5Gdlcmx1bmQ= ?=
wrote:
> Hi,
>
> someone please guide me in setup of NFS server.
>
> What is the difference between packages
> 'nfs-kernel-server' and 'nfs-user-server'
> reagarding performance and con
Hi,
someone please guide me in setup of NFS server.
What is the difference between packages
'nfs-kernel-server' and 'nfs-user-server'
reagarding performance and config?
The server is running sarge and 2.4.22-1-k7.
All tips hel
This one time, at band camp, Jean-Michel Besnard said:
> Is there a way I could have tcp as well for nfsd ?
Read the NFS-HOWTO at:
http://www.ibiblio.org/pub/Linux/docs/HOWTO/NFS-HOWTO
It tells you there is a patch for kernel 2.4.17 and later to support
NFS over TCP. Section 2.5 of that documen
Hi,
I am using the package nfs-kernel-server on woody to build a NFS server.
I want to set up an ssh tunnel but unfortunately, nfsd is only listening udp
but not tcp
Because ssh can no deal with udp, I would to find an easy way to get things
running.
Is there a way I could have tcp
On Sun, Nov 19, 2000 at 06:04:11PM +1100, Bek Oberin wrote:
> I can't seem to start the nfsd stuff. Here's my /etc/exports:
>
> /home 196.168.1.20(rw) 192.168.1.21(rw)
>
> And here's what I get when I try to start the daemon:
>
> [EMAIL PROTECTED] /e
I can't seem to start the nfsd stuff. Here's my /etc/exports:
/home 196.168.1.20(rw) 192.168.1.21(rw)
And here's what I get when I try to start the daemon:
[EMAIL PROTECTED] /etc/init.d# ./nfs-kernel-server start
Exporting directories for NFS kernel daemon...192.168.1.21:/hom
After installing the nfs kernel server, syslogd is flodded with
messages like this one:
rpc.mountd: dump request from 192.168.1.1
last message repeated 31 times
last message repeated 61 times
last message repeated 61 times
192.168.1.1 is the host running the nfs kernel server. What does
"
Tapio Lehtonen <[EMAIL PROTECTED]> writes:
> Hello,
>
> Help, please. I'm running kernel 2.2.14 i386, compiled with kernel
> autofs and nfs support. When I try to start nfs-kernel-server, I get
>
> dilbert# /etc/rc2.d/S20nfs-kernel-server start
> Starting NFS k
Hello,
Help, please. I'm running kernel 2.2.14 i386, compiled with kernel
autofs and nfs support. When I try to start nfs-kernel-server, I get
dilbert# /etc/rc2.d/S20nfs-kernel-server start
Starting NFS kernel daemon: export nfsd nfssvc: Function not implemented
mountd done.
dilbert#
Ar
60 matches
Mail list logo
