'permission denied' trying to mount a directory
 

I have FC3 and had a folder on another computer, also FC3, mounted. I had an etry in /etc/fstab to auto mount it and it worked fine. I have not used this computer for a while and now when I boot into Linux I see that the mounting has failed, reason given was 'permission denied'. If I boot into WinXP I can browse the folder just fine, it is just while in Linux that I have a problem.

I tried to mount the folder after Linux started but I am still denied permission. I am not sure what changed as it used to mount just fine. I'm sure that it is something simple but I am drawing a blank. Thanks.

Todd

try the mount manually - copy and past the command you use and the responce to this thread.

did you remember to start samba first?
is your firewall letting the request through?
is rpc going?

Here is the command and the reply:
Samba and RPC are running and I have turned off the firewall.

When I log in under WinXP (on the same machine) it works fine and I am using the same username/password combo for both Linux and Win.

Thanks

Todd

Try
or

I tried that and I got:
What is interesting (at least to me...) is that I tried to mount the directory from my laptop (identical login and password) and it worked fine. It mounted and I was able to explore the whole thing no problem. It seems to be with this one particular computer.

Todd

I don't know, have you checked it for a DNS issue? Trying to mount it by IP? You are trying to use NFS I presume.
Try several ways to see if you can get to the bottom of it.

mount -t nfs tparks@192.168.1.2:/home /home/tparks/server

You might not be able to mount the whole /home dir, you may have to mount the users dir.

mount -t nfs tparks@192.168.1.2:/home/<user> /home/tparks/server

you may have to use the -o switch
-o username=whatever,password=whatever

Linux is nifty isn't it? Sometimes it makes you fight for every square inch.:study:

When you get it you'll feel accomplishment though.

The only problem is you are using wrong syntax.
try #mount -o username=..... /acsserver//home /home/tparks/server

sorry I also typed wrong one The actual command is
#mount -o username=..... //acsserver/home /home/tparks/server

I tried using all the above suggestions but to no avail, I keep getting various error messages and permission denied results. It is interesting that I am able to mount the server from my laptop but not the desktop. I can even access it through Win XP on the desktop, it in only in Linux that I am denied permission.

I can't imagine that it is a DNS issue, if it was then I doubt that I would get to the point were it would be denying permission. I even did a fresh install of RH4 and it didn't change a thing.

Again, here is the command that I am using and the resulting message:
I appreciate all of the help but so far I am still stuck...

Todd

I just wiped the hard drive and installed Suse Linux 10 (wanted to try it out) and I am having the same problem, this is strange. Seems no matter what I do I cannot mount the folder on my server (which is FC3). It used to mount just fine, I really cannot remember when I began to have a problem, what change I may have made that started this. My laptop mounts it just fine (FC4).

I guess that I am going to have one hell of a sense of accomplishment when I finally get this one figured out...

Todd

Try creating another directory, set it up as a share like normal, and try mounting that.

Record everything you did to set it up and so on and so forth - be pedantic.

Otherwise it sounds like everything is going.

It's a bit of a puzzle to me since my system automatically mounts all the shares it can see. I may have to ressurrect my home network to check this out.

I had a similar problem, "permission denied" and "no such file or directory".
It was in my case SE-Linux that was the cause.( Checking iptables and firewall does not include SE-Linux). Maybe you should check that.

I also have a strange one with Suse 10 before I had a Fedora 2 server and everything workid correct ( Printers NFS share - scanners ) all networked, then the computer started to give problems, and I purchased a new server P4 2.66 - 64Bit 200GB SATA hard disk 1GB ram, and as all my workstations have Suse 10 installed I installed Suse 10 on the server, and the following happens:

1 ) Printers have four instlled all works perfect on all workstations
2 ) Scanners have three all works perfect on all workstations
3 ) NFS export works on all workstations can read and write, but now the strange thing I can not open any documnts from openoffice 2.0 from the server I get " general input/output error " but from Koffice I can open any documents from the server for read/write no problem, firewall is switched OFF. If I copy the document from the server to the local home folder then I can read & write to the document from open office 2.0. I wonder if it is a DNS issue even everything else on the network works correct, and samba works on the only windows machine, but NFS, remember I can read/write to the server folder, but not open documents in open office or Star office 8 direct from the server.

What should I check with SELinux? I see a tab for SELinux under Security Level Configuration but I am not certain what I am looking for that might be causing the problem. Thanks.

Todd

OK, this is interesting...

I shut off SELinux on the server (FC3) and rebooted and I was then able to mount the directory to the workstation (Suse 10); however. I am not able to browse my home folder, tparks, on the server. I am able to browse it when I mount the directory while using another computer or when I use the same computer but booted into windows. My login on this computer is identical to when I login to any other machine.

The user 'tparks' on the server is a member of the group 'tparks' but on the Suse workstation was not. On the workstation I created the 'tparks' group and added 'tparks' as a member and tried again but still did not work. The permissions on the server for the folder are set to 770.

As a side note, I restarted SELinux on the server and I am still able to mount the directory on the Suse workstation. Could SELinux have just been hung up? I am not ever sure what SELinux does (Google here I come...).

Again, thanks for all of the advise, I am getting there; scratching and clawing my way but getting there nonetheless...

Todd