Test Samba client

[64studio-dev@…]

Hi,

Samba used to work fine in version 1.3.0 but some updates ago it broke.

If I want the create a new share I go through the following menus: Desktop -> Administration -> Shared Folders. Then gksudo asks for the root password. Afterwards I get an error message: "The configuration could not be loadad. You are not allowed to access the system configuration."

But accessing a remote share doesn't work either. I go through: Places -> Connect to Server. In the following dialog box I set all parameters and click on Connect. But then the dialog just hangs. This doesn't happen when I'm trying to access another server, e.g. a ftp server.

Thanks, Dennis

[daniel@…]

I was able to share files from a 64 Studio box to a Windows XP desktop in my own tests - we should test further.

[free@…]

I don't have any windows box at hand, feedback about this issue is welcome!

[qharley@…]

The problem seems to be accessing stuff on other boxes from 64 Studio. I have an old PC running XP that contains quite a lot of my samples and music at the moment. The machine is now in disuse (wonder why) and I use it as a file server, mail client and photo editor (We have CS2...)

From this system I can access all the shared folders on my 64 Studio box, but not vice versa.

I have another PC running CentOS for a internet router and web server + file server, and it can see all the shares, so there should not be a problem with the XP box. btw, 64 also cannot see this CentOS Samba share.

[parkland99@…]

Replying to qharley@wbs.co.za:

The problem seems to be accessing stuff on other boxes from 64 Studio.

After about 3 hours of fiddling around, endless config changes and banging my head off the wall, I have got this working on 1.4.x :)

I'm still have some permissions issues, but I have been able to use 64 studio to copy some files from a windows laptop on the 64Studio box.

I think the root of the problem is a missing package. From Etch repository, I installed "smbfs".

Before installing this, I couldn't get the mount command to work from a terminal. With wild errors like this:

tux@64studio:~$  sudo mount -t cifs -o username=foo,password=bar,workgroup=MSHOME,gid=smb,uid=$USER,fmask=770,dmask=770,rw //thinkpad/c /mnt/samba/
mount: wrong fs type, bad option, bad superblock on //thinkpad/c,
       missing codepage or other error

dmesg message log contains

smbfs: mount_data version 1919251317 is not supported

after installing smbfs, I can see the share called C at the network location thinkpad

tux@64studio:~$  sudo mount -t cifs -o username=foo,password=bar,workgroup=MSHOME //thinkpad/c /mnt/samba/
tux@64studio:~$ ls /mnt/samba/LOGFILE.txt /mnt/samba/LOGFILE.txt
tux@64studio:~$ cp /mnt/samba/LOGFILE.txt /home/tux/Desktop/ tux@64studio:~$ ls /home/tux/Desktop/LOGFILE.txt /home/tux/Desktop/LOGFILE.txt

hope this is of help

best wishes everyone

steve~

[parkland99@…]

Even though I can now mount remote shares from the command line, I'm having trouble getting the samba remote share to mount through the gnome "places/connect to server..." dialog (I think the underlying app is nautilus-connect-server)

I continually get an error message like:

Can't display location "smb://bar;foo@thinkpad/C/"

[free]

(In [183]) * Added smbfs (refs #317)

[parkland99@…]

Replying to free:

(In [183]) * Added smbfs (refs #317)

Thanks Free,

Adding smbfs removes the "supoerblock" error and allows me to mount windows shares.

One thing confuses me: as far as I can tell, this should not be necessary because cifs support should be in the kernel. In fact smbfs will be deprecated soon.

The OP was reporting that mounts were working OK in 1.3.0 but broken in 1.4.0 . Was smbfs dropped because it is now in the kernel? Is there some other problem which is being worked-around by installing smbfs?

By the way, this Ubuntu bug is very similar to what I was seeing, which would suggest a problem in their kernel (2.6.20 for Feisty)

https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/31523

I'm concerned to "hijack" this ticket to solve my immediate problem, but this may not be the same problem for Dennis?

[parkland99@…]

The OP was reporting that mounts were working OK in 1.3.0 but broken in 1.4.0 .

I'm concerned to "hijack" this ticket to solve my immediate problem, but this may not be the same problem for Dennis?

Free,

I think I've solved the GUI part of the problem and hopefully the ticket can be closed.

The second part of the problem was a failure of nautilus-connect-server to connect to a remote samba system. This seems to be the problem reported by Dennis in this ticket, and also seems to be the same as one reported by Mick on the user forum.

The problem, I think, is another missing package (and whatever extra packages it is dependent on).

This missing one is libgnomevfs2-extra + dependencies (I got mine from Etch).

After apt-getting libgnomevfs2-extra, I am able to browse a remote windows share from gnome / places / connect to server ... dialog.

For me, I only enter the IP address, share name and "name to use". After doing this, I get a new network folder on the desktop and can see the remote files.

Also, in the nautilus-connect-server, I can select "browse network", and see all windows / samba boxes on my local network (including the samba share on the host machine!), and I can drill down and see their shares.

For information, I tried adding vfs2-extra yesterday while testing, but it did not make any difference. Looking back, I think this was because smbfs was also missing but I did not realise this at the time, so for me there were two problems to be solved here.

hope this helps Steve~

[parkland99@…]

If I want the create a new share I go through the following menus: Desktop -> Administration -> Shared Folders. Then gksudo asks for the root password. Afterwards I get an error message: "The configuration could not be loadad. You are not allowed to access the system configuration."

Hello Dennis,

The problem with "configuration could not be loaded" may be due to libnet-dbus-perl missing after upgrading.

see http://lists.64studio.com/pipermail/64studio-devel/2007-May/004280.html and http://lists.64studio.com/pipermail/64studio-devel/2007-May/004050.html

Also, please see the other messages on this ticket about two other packages which help to solve some other samba issues.

best wishes Steve~

[free@…]

Steve, thanks a lot for your help. That's great that you sorted this out! I'm going to add libgnomevfs2-extra right now, and I've also upgraded samba to version 3.0.24-6etch4 from the etch security update.

[free]

(In [185]) * Added smbfs and libgnomevfs2-extra (closes #317)