** Changed in: samba (Ubuntu)
Importance: Undecided = Low
** Changed in: samba (Ubuntu)
Status: Incomplete = Confirmed
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this bug notification because you are a member
** Changed in: samba (Ubuntu)
Importance: Undecided = Low
** Changed in: samba (Ubuntu)
Status: Incomplete = Confirmed
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this bug notification because you are a member
If the servers where people are seeing this problem are all openwrt
running Samba 2.0, then it appears this is a known incompatibility
dating back to 2004. I could open a bug report upstream asking for
Linux CIFS compatibility with Samba 2.0, but if it hasn't been fixed so
far, it's unlikely that
This appears to be a duplicate of at bug at
https://dev.openwrt.org/ticket/2865
Try mounting in fstab using this
For a non-password protected share with read/write permission use
//netbiosname/sharename/media/sharenamecifs
guest,rw,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
This appears to be a duplicate of at bug at
https://dev.openwrt.org/ticket/2865
Try mounting in fstab using this
For a non-password protected share with read/write permission use
//netbiosname/sharename/media/sharenamecifs
guest,rw,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
It appears that this problem affects me as well.
I have Intrepid Ibex 2.6.27-7-generic kernel. Since upgrade to Intrepid, I
cannot access samba folders.
My samba server is 2.0 (shipped with OpenWrt). I am mounting with simple fstab
line:
//asus-router/torrents /mnt/torrents smbfs
It appears that this problem affects me as well.
I have Intrepid Ibex 2.6.27-7-generic kernel. Since upgrade to Intrepid, I
cannot access samba folders.
My samba server is 2.0 (shipped with OpenWrt). I am mounting with simple fstab
line:
//asus-router/torrents /mnt/torrents smbfs
Malte,
Please file a separate bug report for your issue, which is unrelated to
the other issues discussed in this bug report.
Plaintext authentication with CIFS is, I believe, a marginal use case
anymore; I won't rule out the possibility of including a fix for this in
an update to Ubuntu 8.04,
Malte,
Please file a separate bug report for your issue, which is unrelated to
the other issues discussed in this bug report.
Plaintext authentication with CIFS is, I believe, a marginal use case
anymore; I won't rule out the possibility of including a fix for this in
an update to Ubuntu 8.04,
Since I have not seen any new posts on this thread for some months, I
would like to confirm the problems mentioned in the earlier bug reports:
1) After the upgrade to Ubuntu 8.04 I cannot access the files on a samba server
any longer.
When I try to mount the samba share by the following
Since I have not seen any new posts on this thread for some months, I
would like to confirm the problems mentioned in the earlier bug reports:
1) After the upgrade to Ubuntu 8.04 I cannot access the files on a samba server
any longer.
When I try to mount the samba share by the following
I'm experiencing similar problems and I definitely don't think it is
only a nautilus problem.
I'm sharing a folder from a windows98 vmware guest and am automounting the
folder, using cifs, via fstab on the host.
mounting is fine, without any error messages, but I can only acces directories.
I had same problem as yours. and i just changed file manager to Thunar and no
problem.
I believe this is a Nautilus bug. i suggest you better try to use another file
manager before you messed up samba setting.
see also Nautilus bug there must be real solution.
--
no way to read and write
Below the server side log, as for the file debug1.txt.
uid is same as on client, gid differs; gid is OK for client.
I did try to disable unix extensions on the client side, but this did not
change the results
Further information on the systems that may help:
Under previous Ubuntu versions, I was
Below the server side log, as for the file debug1.txt.
uid is same as on client, gid differs; gid is OK for client.
I did try to disable unix extensions on the client side, but this did not
change the results
Further information on the systems that may help:
Under previous Ubuntu versions, I was
I think I have almost found the answer. Look at this bug:
https://bugzilla.samba.org/show_bug.cgi?id=2512
I turned off Unix Extensions on the server side and lo and behold I
could mount the share on the client using CIFS and the program worked!
It looks like CIFS is not telling the how truth
My server: an old linux server: Linux 2.2.16-22 #1 Tue Aug 22 16:16:55 EDT 2000
i586 unknown
/usr/sbin/smbd -V: Version 2.0.7
On the server: both accounts where the uid is the same as on the client, and
(most) accounts where the uid differs from that on the client.
Passwords in plain text
Hi Jan,
The client-side log really only shows that the kernel driver got an
error accessing the file, and mapped this to the EACCES, which I don't
know to be incorrect.
The requested client- and server-side ls output, showing the respective
permissions, would still be helpful here.
--
no way
Steve,
To answer your questions about the bug I am seeing, I have compiled the
following. Look below, there is a significant difference in the client
side file permissions when cifs is used to mount the volume and when
smbfs is used. This is fully repeatable and the listings below did not
require
I think I have almost found the answer. Look at this bug:
https://bugzilla.samba.org/show_bug.cgi?id=2512
I turned off Unix Extensions on the server side and lo and behold I
could mount the share on the client using CIFS and the program worked!
It looks like CIFS is not telling the how truth
My server: an old linux server: Linux 2.2.16-22 #1 Tue Aug 22 16:16:55 EDT 2000
i586 unknown
/usr/sbin/smbd -V: Version 2.0.7
On the server: both accounts where the uid is the same as on the client, and
(most) accounts where the uid differs from that on the client.
Passwords in plain text
Hi Jan,
The client-side log really only shows that the kernel driver got an
error accessing the file, and mapped this to the EACCES, which I don't
know to be incorrect.
The requested client- and server-side ls output, showing the respective
permissions, would still be helpful here.
--
no way
tonyw,
I'm glad to hear that you were able to get your application working!
Based on your output, I'm not convinced that your problem is the same as
https://bugzilla.samba.org/show_bug.cgi?id=2512. For one thing, you
mention that you're able to access the files from a text editor, so
there at
Problem solved for me!
http://ubuntuforums.org/showthread.php?t=707370highlight=cifs+samba+hardy
Recompiling samba to use the smbfs libraries (as it should) did the
trick.
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this
Jan,
You want to get the samba 3.0.28a archive from
http://us1.samba.org/samba/ftp/old-versions/samba-3.0.28a.tar.gz
expand it into a temporary location, cd to the source folder and enter
the command:
./configure --with-smbmount --sysconfdir=/etc/samba --with-
lockdir=/var/cache/samba
Jan,
For questions about building samba from source to re-enable the smbfs
utilities, please follow up to the forums instead of to this bug report.
This bug report should be kept focused on finding a solution to the
actual bug that's preventing mount.cifs from working correctly (which,
btw, I
I have the same problem.
I can mount and browse shares using nautilus or smbmount but i cannot read or
write files.
Files Permissions are OK.
The server is Windows 2003 pc that shares a public access directory (no
username/pass required)
--
no way to read and write files on mounted samba share
Problem solved for me!
http://ubuntuforums.org/showthread.php?t=707370highlight=cifs+samba+hardy
Recompiling samba to use the smbfs libraries (as it should) did the
trick.
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this
I can confirm that TMwtP 's solution also works for me. Recompiling
samba on the client only and manually installing smbfs fixes the problem
I had with Tas Books.
Looks like the CIFS client distributed with Hardy 8.04 is broken.
--
no way to read and write files on mounted samba share on
Could you please help me out a little more on how to compile samba, so
that I can try it as well ?
I installed git and autogen from the package manager.
Then I got the git package as described in:
http://wiki.samba.org/index.php/Using_Git_for_Samba_Development
I did autogen.sh in the samba/source
There are several different sets of symptoms being described here, none of
which are reproducible for me.
- the original bug report says that the file permissions on the local mount are
correctly set, but the files are not readable or writable. This sounds like a
permissions problem on the
Jan,
You want to get the samba 3.0.28a archive from
http://us1.samba.org/samba/ftp/old-versions/samba-3.0.28a.tar.gz
expand it into a temporary location, cd to the source folder and enter
the command:
./configure --with-smbmount --sysconfdir=/etc/samba --with-
lockdir=/var/cache/samba
Jan,
For questions about building samba from source to re-enable the smbfs
utilities, please follow up to the forums instead of to this bug report.
This bug report should be kept focused on finding a solution to the
actual bug that's preventing mount.cifs from working correctly (which,
btw, I
I don't understand why it's set to incomplete all the time. People are
requesting SERVER logs all the time, while a CLIENT log is attached. The
bug clearly is in the CLIENT, not in the server, as the servers are
always non-Ubuntu, unchanged systems of all kinds. If ever requesting a
server log,
Hmm, I've been with the Ubuntu communty since 5.04, and this is the first time
something as serious as this has occurred for me. For instance, I can browse my
image files on the Samba server (a Fedora installation) as before, I even see
thumbnails of my pics, but I can't open them. I can't play
As asked before is there anything in your logfiles?
Thanks
chuck
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this bug notification because you are a member of
My samba log files on the server doesn't show anything out of the
ordinary. Remember - nothing has changed on the server, and as far as
the server can tell I can access my files.
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received
Hmm, I've been with the Ubuntu communty since 5.04, and this is the first time
something as serious as this has occurred for me. For instance, I can browse my
image files on the Samba server (a Fedora installation) as before, I even see
thumbnails of my pics, but I can't open them. I can't play
As asked before is there anything in your logfiles?
Thanks
chuck
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this bug notification because you are a member of
My samba log files on the server doesn't show anything out of the
ordinary. Remember - nothing has changed on the server, and as far as
the server can tell I can access my files.
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received
The same problem. I have a smb share on server which is public and writeable,
and with fstab like this:
//server/pub/media/pub smbfs
guest,uid=1000,rw,iocharest=utf8,file_mode=0775,dir_mode=0777 0 0
only root can write to /media/pub (even though 1000 is uid of normal user).
Marcin, the unmount on shutdown problem has been noted elsewhere (bug
#211631) and is probably a mis-ordering of the shtudown script.
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this bug notification because you are a
** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
The same problem. I have a smb share on server which is public and writeable,
and with fstab like this:
//server/pub/media/pub smbfs
guest,uid=1000,rw,iocharest=utf8,file_mode=0775,dir_mode=0777 0 0
only root can write to /media/pub (even though 1000 is uid of normal user).
Marcin, the unmount on shutdown problem has been noted elsewhere (bug
#211631) and is probably a mis-ordering of the shtudown script.
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this bug notification because you are a
** Changed in: samba (Ubuntu)
Status: Incomplete = New
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
There certainly appears to be a problem with the Hardy CIFS/SMBFS
implementation. For me it has broken a wine application that used
smbfs/cifs to access a remote set of files.
We use an old Windows based account packages (TAS Books). Works fine and
runs under Linux/wine, so no real need to
I have exaxctly the same problems. Due to this, my Ubuntu computer has
started to be a nuisance, especially because downgrading back to 7.* is
impossible, and gvfs cannot be disabled without removing Nautilus and
the Ubuntu desktop. What a pain is hardy !
My configuration: 1 Ubuntu hardy destop,
There certainly appears to be a problem with the Hardy CIFS/SMBFS
implementation. For me it has broken a wine application that used
smbfs/cifs to access a remote set of files.
We use an old Windows based account packages (TAS Books). Works fine and
runs under Linux/wine, so no real need to
I have exaxctly the same problems. Due to this, my Ubuntu computer has
started to be a nuisance, especially because downgrading back to 7.* is
impossible, and gvfs cannot be disabled without removing Nautilus and
the Ubuntu desktop. What a pain is hardy !
My configuration: 1 Ubuntu hardy destop,
In addition to the previous post, I also see strange behavior while connecting
via Nautilus:
- directory displays OK.
- at opening a text file I get a strange authentication required pop-up, for a
user called guest (see attached)
- then, everything seems to go fine after that.
- then an
I have the exact same problem. This is indeed a huge step back - I have
all my music, movies and stuff on a file server. After upgrading
everything is unusable. I can create new files and delete them, but I
can't play existing mp3s.
--
no way to read and write files on mounted samba share on
Is there anything in your log files on the samba server?
Thanks
chuck
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this bug notification because you are a
Is there anything in your log files on the samba server?
Thanks
chuck
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
no way to read and write files on mounted samba share on hardy
https://bugs.launchpad.net/bugs/210741
You received this bug notification because you are a
54 matches
Mail list logo
