When I save a file on a FC3 samba 3.0.11-6 box I get in my messages: Apr 27 18:32:23 epia smbd[3107]: [2005/04/27 18:32:23, 0] smbd/service.c:make_connection_snum(567) Apr 27 18:32:23 epia smbd[3107]: Can't become connected user! Apr 27 18:32:24 epia smbd[3107]: [2005/04/27 18:32:24, 0] smbd/service.c:make_connection_snum(567) Apr 27 18:32:24 epia smbd[3107]: Can't become connected user! Apr 27 18:32:24 epia smbd[3107]: [2005/04/27 18:32:24, 0] smbd/service.c:make_connection_snum(567) Apr 27 18:32:24 epia smbd[3107]: Can't become connected user! This is with a very basic smb.conf: [global] workgroup = bla server string = VIA Epia Samba Server interfaces = 192.168.xx.0/24, 127.0.0.1/8 bind interfaces only = Yes log level = 1 log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = /etc/printcap os level = 56 preferred master = Yes domain master = Yes dns proxy = No wins support = Yes ldap ssl = no remote announce = 192.168.xx.255 valid users = udo, root hosts allow = 192.168.xx., 127. [homes] comment = Home Directories read only = No browseable = No [data] comment = Data path = /usr/local/data valid users = udo read only = No create mask = 0760 [data2] comment = Data2 path = /usr/local/data2 username = udo valid users = udo read only = No create mask = 0760 Stuff works OK, messages are annoying. Messages appear in older versions as well. Lots of similar complaints on the web.
Upgraded to Fedora Core 4 with Samba 3.0.14a-2 and custom kernel version 2.6.12.1. The error now looks like: Jun 28 17:01:37 epia smbd[27734]: [2005/06/28 17:01:37, 0] smbd/service.c:make_connection_snum(577) Jun 28 17:01:37 epia smbd[27734]: Can't become connected user!
Are any selinux settings enabled perhaps ?
(In reply to comment #2) > Are any selinux settings enabled perhaps ? We boot with selinux=0. (although there is selinux in the kernel for later experiments)
Try running 'strace smbd -d 0 -i 2>&1 > logfile' and connect using smbclient.
Created attachment 1294 [details] The strace. I hope it helps to show what is wrong. A setup problem or a real bug... The strace asked for. I used window to connect since that's what I use as client.
the satrec didn't shoiw what I hoped. Can't you attach a level 10 debug log surrounding the error messages?
Did you see this mail? I know I already asked about this but perhaps it applies. http://marc.theaimsgroup.com/?l=samba&m=112058027926933&w=2
We boot with selinux=0 so it is turned off completely, AFAIK. (like I posted before) I could try to build a kernel completely without selinux which should yield same results if I am right.
Created attachment 1296 [details] Debuglevel=10 log
Ok, move the 'valid users' from [global] to each individual share. Or add [ipc$] valid users = udo root nobody ipc$ needs to be accessible anonymously. Volker
Thanks, will test the IPC$ thing out!
Volker's comment works very well: Ok, move the 'valid users' from [global] to each individual share. Or add [ipc$] valid users = udo root nobody ipc$ needs to be accessible anonymously. So the problem is fixed. (question is how samba could function without the fix?)
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.