You are not logged in.
with smbclient 3.4.3-2 smbnetfs and dolphin find my workgroup but no host or shares .
interestingly dolphin promts me for a username password for my workgroup ,not a specific host but for the workgroup itself , but that doesn't help anything.
in dolphin smb://hostname works
parintachin
Last edited by parintachin (2009-11-23 12:04:37)
Offline
I am having this same issue when trying to access network hosts from nautilus.
Offline
Same thing here. I see the top folders but they are empty.
Few weeks ago when I installed Arch I also had to do the following extra steps to get smbnetfs running:
#chown nobody:nobody /mnt/smbnet
#chown nobody:nobody /etc/smbnetfs
#chmod 600 /etc/smbnetfs/.smb/smbnetfs.conf
Also I did notice that having smbnetfs in rc.conf would start the daemon but would never show any share. I had to manually restart the daemon in order to see my network shares.
I hope that someone will find a way to fix it. I never tried the fusesmb option as it appears to be marked as broken in the wiki.
Alphazo
Offline
with smbclient 3.4.3-2 smbnetfs and dolphin find my workgroup but no host or shares .
interestingly dolphin promts me for a username password for my workgroup ,not a specific host but for the workgroup itself , but that doesn't help anything.
in dolphin smb://hostname works
parintachin
I have the same problem and I have checked so that the latest version of samba on the server have the passwords generated to the new passwd file. And I have checked with another computer with windows 7 and it works fine.
I read in another thread that you could try to downgrade to the version before 3.4.3 and this problem will be solved.
Offline
I may be wrong but i think samba new version changed the way samba users and passwords are stored.
Old smbusers and smbpasswd files are no longer used. Instead, infos are stored in passdb.tdb and secrets.tdb
So you have to register again samba users with
smbpasswd -a username
From the samba-3.4.0 release notes:
!!! ATTENTION !!!
The default passdb backend has been changed to 'tdbsam'! That breaks existing
setups using the 'smbpasswd' backend without explicit declaration! Please use
'passdb backend = smbpasswd' if you would like to stick to the 'smbpasswd'
backend or convert your smbpasswd entries using e.g. 'pdbedit -i smbpasswd -e
tdbsam'.
Offline
Not quite sure when this happened, but after I did a pacman -Syu today sometime, my logs grew to silly sizes with these types of entries:
Nov 13 22:45:27 hostname nmbd[3269]: [2009/11/13 22:45:27, 0] lib/util_tdb.c:385(tdb_log)
Nov 13 22:45:27 hostname nmbd[3269]: tdb(/var/cache/samba/gencache.tdb): tdb_oob len 980837756 beyond eof at 12288
Related to the Samba problems described above, I wonder?
PS: I use 'security = share' in my smb.conf![]()
Added later: Killing that cache file after stopping the samba daemon seemed to do the trick:
# rm /var/cache/samba/gencache.tdbLast edited by ninian (2009-11-15 12:14:33)
Offline
I may be wrong but i think samba new version changed the way samba users and passwords are stored.
Old smbusers and smbpasswd files are no longer used. Instead, infos are stored in passdb.tdb and secrets.tdb
So you have to register again samba users with
smbpasswd -a username
You are right. Dispite readding users the problem still remains with smbclient, unfortunately ![]()
Offline
Not quite sure when this happened, but after I did a pacman -Syu today sometime, my logs grew to silly sizes with these types of entries:
Nov 13 22:45:27 hostname nmbd[3269]: [2009/11/13 22:45:27, 0] lib/util_tdb.c:385(tdb_log)
Nov 13 22:45:27 hostname nmbd[3269]: tdb(/var/cache/samba/gencache.tdb): tdb_oob len 980837756 beyond eof at 12288Related to the Samba problems described above, I wonder?
PS: I use 'security = share' in my smb.conf
I reckon it probably has something to do with the new way samba stores passwords and users.
Offline
We seem to have two different threads here. The OP was about smbclient and smbnetfs, of which I'm having the same problem. The other stuff is about full blown samba. Let's keep this thread to the OP and open another (if necessary) for the samba stuff.
Offline
We seem to have two different threads here. The OP was about smbclient and smbnetfs, of which I'm having the same problem. The other stuff is about full blown samba. Let's keep this thread to the OP and open another (if necessary) for the samba stuff.
I agree.
There are a thread about the new samba update people can start with if they have issues with samba. http://bbs.archlinux.org/viewtopic.php?id=84416
Offline
There are a thread about the new samba update people can start with if they have issues with samba. http://bbs.archlinux.org/viewtopic.php?id=84416
Thanks for pointing out that thread.
Offline
has somebody found a solution ?
ps. the same problem hit debian sid
Offline
has somebody found a solution ?
ps. the same problem hit debian sid
No, not really. Been searching but not really found a solution.
I guess the only thing we can do is to revert to the version before 3.4.3-2 and wait until they patch the new
version.
Offline
solved with smbclient 3.4.3-3 ![]()
Offline