SOLVED: Basic Kubuntu to Kubuntu home network

[brasslover]

Re: Basic Kubuntu to Kubuntu home network

I had to edit my last post for correctness as I can't currently find any options under System settings to configure NFS client connections. Sorry, I wasn't at my Kubuntu machine when I originally posted..

[sabbathpriest]

Re: Basic Kubuntu to Kubuntu home network

Oh Brother, I feel like my brain expanded by a cubic meter.... But I still am not getting it right. Now, here's my /etc/exports on the Server side:

# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/homes gss/krb5i(rw,sync)
#
/var/lib/samba/printers/ *(async,all_squash)
/var/spool/samba/ *(async,all_squash)
/media/sda1 192.168.2.2(rw)

...and here's the etc/fstab on the Client side

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=40e2b915-4e22-4e6b-9f88-06f121968450 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda5
UUID=ac1175d5-6f26-46e0-ac75-c8dc51135772 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
192.168.2.6:media/sda1 /media/floyd nfs defaults,user 0 0

Now, the shared drive shows on the Client side as

Remote Share 192.168.2.6:media/sda1

but when I click on it or try to mount it it tells me

mount.nfs 192.168.2.6:media/sda1 failed, reason given by server: Premission Denied

In case you are wondering, I did run the following commands after changing etc/exports on the Server side

sudo dpkg-reconfigure portmap

sudo /etc/init.d/portmap restart

And these commands after changing etc/fstab on the Client side

sudo /etc/init.d/portmap restart

sudo /etc/iit.d/nfs-common restart

I am hoping that there is a blatant and obvious mistake in my setup... anything you guys can see?
Once again, THANKS for reading my post, I owe you all a round.

[brasslover]

Re: Basic Kubuntu to Kubuntu home network

Ah, yes, the dreaded permission denied message... >

Try changing the last line in /etc/fstab on the client from this:

192.168.2.6:media/sda1 /media/floyd nfs defaults,user  0  0

to this:

192.168.2.6:/media/sda1 /media/floyd nfs defaults,user  0  0

If that fails, try giving the server a name in /etc/hosts and replace 192.168.2.6 in /etc/fstab with the name you've chosen. You might also run the following on the server immediately after you receive the "permission denied" and see if there is any further explanation listed as to what the issue might be:

tail /var/log/auth.log

[sabbathpriest]

SOLVED

It works now after correcting the typo pointed out by brasslover and a hard reboot of both boxes!
Thank you all for the help!

[metricus]

Re: SOLVED: Basic Kubuntu to Kubuntu home network

My project on this subject was to find a method that would fully use the KDE interface and minimize the need for editing system files. In other words: click only.

I ended up re-formatting and re-installing Gutsy just to see how it works from scratch. The setup was a "server" which had large capacity drives and was also connected to a printer and a "client" which is my laptop. The intent was to share files/directories from the sever as well as the printer.

Sharing Files:

Server Side:
1. Install Package "nfs-kernel-server" with Adept. This also installs all dependencies including portmap
2. K-Menu>System Settings>Sharing. Go to "File Sharing" and click "Administrator mode". Enter your password and then activate "Enable Local Network File Sharing". Choose "Advanced Sharing" and "Use NFS"
3. In the same window under "Shared Folders" choose "Add" and then choose the folder you wish to share. For example /media/sda4/Music (I have a folder named "Music" on my sda4 parition) Then check: "Share with NFS (Linux/Unix)".
4.Make sure that the IP address of your server is fixed and not dhcp. Change it in System Settings>Network Settings
5. I found that it is better to reboot the server after finishing this procedure.

Client Side:
1. Install package "nfs-common"
2. You need to create a directory where fstab will mount the remote share.
To do this you need to start konqueror with root permisions: type in a console: sudo konqueror and after entering the password you will be able to browse with root privileges. BE CAREFUL what you do at this point! Just navigate to the /media folder and right click in it and choose new folder. name your new folder "Music". Once you are done exit the Konqueror before you do some damage
3. You edit your etc/fstab as root (right click>Actions>edit as root) then add the following entry adapted to your specific IP and directories to be shared:
192.168.1.10/media/sda4/Music /media/Music nfs user,noauto,defaults 0 0 (similar also with the posting by sabbathpriest)
4. You will have a new mountable drive under "Storage Media" See snapshot1
NOTES:
*The entry "noauto" is needed if you use a laptop and may not always be at home.
*There seems to be no GUI method to setup the client under KDE.

Sharing Printers

Server Side:
1. It is assumed that our printer is already installed and works on the server side.
2. Kmenu>System Settings>Printers Click "Administrator mode" ...password
3. Click on "Print Server" and enable "Share Printers on Local Network"
4. Reboot Server (not sure if needed but won't hurt)

Client Side
1. KMenu>System Settings>Printers (no need for admin mode here)
2. Click Add>Add Printer/Class choose "Remote CUPS Server" >Next> choose Anonymous >Next > Enter the LAN IP address of your server ex; 192.168.1.10 (should be a fixed one) >Next
3. In the next screen the printer that you shared on the sever should appear available. Choose it and follow the steps to choose the appropriate driver, name etc.
That's all!

Hope this helps

Metricus

[MatthewSchenker]

Re: SOLVED: Basic Kubuntu to Kubuntu home network

Metricus,
Thanks to your instructions, I was finally able to get print sharing working!

However, file sharing still does not work. I did the steps outlined in reply #19. I was able to get the "Remote Share" to show up under "Storage Media" (just like the screenshot attached to your message) which was very exciting. However, when I click on the Remote Share, I get this message:
mount.nfs: unrecognized mount point ...

It seems I am getting closer anyway!

Any suggestions on ho to fix this?

Thanks,
Matthew

[MatthewSchenker]

Re: Basic Kubuntu to Kubuntu home network

Easy Networking and Printer Sharing

Zeroconf and print sharing let you browse the local network for available services. Both are now simple to setup and maintain requiring nothing more than ticking a box to enable the feature.

Network sharing

K Menu | System Settings | Network Settings | Zeroconf Service Discovery

Snowhog,
I definitely appreciate the pointer, but it did not work.

I don't mean to sound harsh, but I think we ought to stop using terms like "easy" and "simple" when referring to wireless networking. I'm sure I'm not alone when I say it's frustrating to keep hearing about another set of instructions that makes wireless setup "easy" and "simple." Each time, I open the instructions all excited about making wireless finally function. At this point, I have spent something like 20 hours on this, and none of the "easy" instructions has worked.

I've gained a lot of confidence in Kubuntu, so I'm sure there is a solution. I just haven't found it yet!

When I do find a solution, I promise to put together instructions for others who are suffering the same frustration!

[MatthewSchenker]

Re: SOLVED: Basic Kubuntu to Kubuntu home network

OK, as I look over the discussion here, it seems I must be close! I tried the suggestions offered in metricus's last post, as well as brasslover's last post.

While I still have some nerves left, making one more attempt to figure out what's wrong with wireless, I'm listing the various lines I have used in the etc/fstab file on the client side, along with the resulting error:

Line attempted: 192.168.1.177:/sda1/home /matthew/Documents nfs defaults,user 0 0
Result: Permissions denied

Line attempted: 192.168.1.177:/sda1 /home/matthew/Documents nfs defaults,user 0 0
Result: mount.nfs: mount point /matthew/Documents does not exist

Line attempted: 192.168.1.177:/home/matthew/Documents nfs defaults,user 0 0
Result: Nothing -- does not show up at all

Line attempted: 192.168.1.177:/sda1/home/matthew/Documents nfs defaults,user 0 0
Result: Nothing -- does not show up at all

Line attempted: 192.168.1.177/sda1/home /matthew/Documents nfs defaults,user 0 0
Result: mount.nfs: mount point /matthew/Documents does not exist

Line attempted: 192.168.1.177/sda1 /home/matthew/Documents nfs defaults,user 0 0
Result: Permissions denied

Line attempted: 192.168.1.177/home/matthew/Documents nfs defaults,user 0 0
Result: Result: Nothing -- does not show up at all

Line attempted: 192.168.1.177/sda1/home/matthew/Documents nfs defaults,user 0 0
Result: Result: Nothing -- does not show up at all

Line attempted: 192.168.1.177:/sda1/home /matthew/Documents nfs user,noauto,defaults 0 0
Result: mount.nfs: mount point /matthew/Documents does not exist

Line attempted: 192.168.1.177:/sda1 /home/matthew/Documents nfs user,noauto,defaults 0 0
Result: Permissions denied

Line attempted: 192.168.1.177:/home/matthew/Documents nfs user,noauto,defaults 0 0
Result: Nothing -- does not show up at all

Line attempted: 192.168.1.177:/sda1/home/matthew/Documents nfs user,noauto,defaults 0 0
Result: Nothing -- does not show up at all

Line attempted: 192.168.1.177/sda1/home /matthew/Documents nfs user,noauto,defaults 0 0
Result: mount.nfs: mount point /matthew/Documents does not exist

Line attempted: 192.168.1.177/sda1 /home/matthew/Documents nfs user,noauto,defaults 0 0
Result: Permissions denied

Line attempted: 192.168.1.177/home/matthew/Documents nfs user,noauto,defaults 0 0
Result: Nothing -- does not show up at all

Line attempted: 192.168.1.177/sda1/home/matthew/Documents nfs user,noauto,defaults 0 0
Result: Nothing -- does not show up at all

After doing each of these, I ran “sudo dpkg-reconfigure portmap” and “sudo /etc/init.d/portmap restart” on the server, and ran “sudo /etc/init.d/portmap restart” on the client. Nothing worked.

Still hoping for a solution.

Thanks,
Matthew

[MatthewSchenker]

Re: SOLVED: Basic Kubuntu to Kubuntu home network

This is just a gues but how about doing something like:

Line attempted: 192.168.1.177://home/matthew/Documents

(notice the double backslash)

None of the other instructions asks for a double slash, but I tried it because I'm getting desperate.

It doesn't work. I get all the same errors as reported above.

Time to give up?

Thanks,
Matthew

[Fintan]

Re: SOLVED: Basic Kubuntu to Kubuntu home network

I am sorry but I deleted that post by mistake, I am not sure it will work either :P

[MatthewSchenker]

Re: SOLVED: Basic Kubuntu to Kubuntu home network

Fintan,
That's OK, and thanks for trying to help.

I really appreciate the great work people have done on Kubuntu, and it is now my full-time operating system.

Of course, the file-sharing issues are frustrating, but I'll deal with it for now. Getting into the Kubuntu community has benefits that far outweigh this relatively small hangup.

I will just hold out hope that the developers working on Kubuntu know how to fix file sharing issues, and I am looking forward to great news in the future.

Matt

[metricus]

Re: SOLVED: Basic Kubuntu to Kubuntu home network

Sorry I did not reply earlier.
Matthew If you are still following this post please reply so I can help . I need more info on your setup.

For the beginning I would like to know if the directory you are attempting to mount your share to is already there. For example if you want to mount the share to /media/share the directory share needs to be there before attempting the mount. It seems this is why you are getting the error message.

Then, which directory have you shared on 192.168.1.177? Also is this a fixed IP? Doesn't sound like it is.

[MatthewSchenker]

Re: SOLVED: Basic Kubuntu to Kubuntu home network

Metricus,
Thanks for trying to help, but this seems far more complicated than I thought it would be.

To answer your questions:

• Yes, the directory I am attempting to mount is already there, and it is set to "share." It has that folder icon with the hand under it. I did this before trying to share it from the laptop.
• I used 192.168.1.177 as a dummy IP for my post. I wasn't sure if it's a security risk to post my actual IP address. But the real one is a fixed IP address.

Honestly, at this point, it's easier for me to just transfer files using a thumb drive. All the configurations and options that have to be checked and re-checked, and all the branches of settings and installations, make it a lot of work. I've spent so many hours trying to get this working over the past few weeks, I'm ready to be patient and wait for the file sharing system to get better in a future release.

In the meantime, I'm very appreciative of all the other great Kubuntu features!

Matthew

[metricus]

Re: SOLVED: Basic Kubuntu to Kubuntu home network

• Yes, the directory I am attempting to mount is already there, and it is set to "share." It has that folder icon with the hand under it. I did this before trying to share it from the laptop.

This is not what I meant. And if you have a little bit more patience this will work.

The reason you were getting the message:"mount.nfs: unrecognized mount point ..."
is most likely that the directory where fstab is attempting to mount the remote TO to did not exist or was not empty. The mount process requires an existing empty directory which will become the directory of the mounted volume.

You had listed the string from your fstab:
192.168.1.177/home/matthew/Documents nfs defaults,user 0 0

this isincomplete because you need a directory to mount it TO which exists and is empty. It is common to create a mount point in /mnt or /media

so attempt a line like:
192.168.1.177/home/matthew/Documents /media/remote nfs defaults,user 0 0

Now VERY IMPORTANT:
1. You need to create the directory /media/remote BEFORE fstab attempts to mount the remote share. Otherwise it will reply that it has no place to mount it to in other words"unrecognized mount point"
To do this you need to start konqueror with root permisions: type in a console: sudo konqueror and after entering the password you will be able to browse with root privileges. BE CAREFUL what you do at this point! Just navigate to the /media folder and right click in it and choose new folder. name your new folder sda1remote. Once you are done exit the Konqueror before you do some damage

Once the directory /media/remote is there fstab will be able to mount the remote to it.

I have to say that I feel your frustration as I find as well that is unacceptable that Kubuntu still does not have an built-in method of sharing files mostly under nfs which is a native linux system mainly since linux has always been tops in file servers and networking.

[metricus]

Re: SOLVED: Basic Kubuntu to Kubuntu home network

I have noticed a mistake in my initial post with the procedure. this may have caused Mathew to be confused about the entry in fstab.
I had:
192.168.1.10/sda4/Music /media/Music nfs user,noauto,defaults 0 0

The correct line is:
192.168.1.10/media/sda4/Music /media/Music nfs user,noauto,defaults 0 0

sda4 is a partition on my server which contains the folders to be shared.

Whatever comes after the IP has to be a directory on the root tree of the server. In my case the directory /media/sda4/Music exists and is shared on the server.


I have edited the initial post and it now has the correct entry. I have also added the step (2) of creating the directory on the client side where the volume will be mounted.