My current samba configuration worked until I upgraded to this version which occurred when I upgraded my system from Suse Linux 10.0 to Suse Linux 10.2. Following is the Globals section of my smb.conf which was created first by me, and then updated by SWAT. workgroup = MCCLATCHEY realm = DAD.MCCLATCHEY.FAM server string = Samba %v running on Dad interfaces = lo, eth0 bind interfaces only = Yes map to guest = Bad User passdb backend = tdbsam algorithmic rid base = 100000 passwd program = /usr/bin/passwd %u passwd chat = *password* %n\n *password* %n\n *changed* passwd chat debug = Yes username map = /etc/samba/smbusers username level = 1 log level = 3 passdb:5 auth:10 winbind:2 debug pid = Yes debug uid = Yes reset on zero vc = Yes name resolve order = host lmhosts wins bcast time server = Yes server signing = auto enable asu support = Yes max smbd processes = 1000 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192 SO_RCVBUF=8192 printcap name = cups add user script = /usr/sbin/useradd -m %u delete user script = /usr/sbin/userdel -r %u add group script = /usr/sbin/groupadd %g delete group script = /usr/sbin/groupdel %g add user to group script = /usr/sbin/groupmod -A %u %g delete user from group script = /usr/sbin/groupmod -R %u %g add machine script = /usr/sbin/useradd -s /bin/false -d /var/lib/nobody %u logon script = scripts\logon.cmd logon path = \\%L\profiles\%U logon drive = H: logon home = \\%L\%U domain logons = Yes os level = 35 preferred master = Yes domain master = Yes wins proxy = Yes wins support = Yes ldap ssl = no message command = csh -c 'xedit %s;rm %s' & usershare allow guests = Yes idmap uid = 10000-20000 idmap gid = 10000-20000 template homedir = /home/%U template shell = /bin/bash winbind cache time = 600 winbind enum users = Yes winbind enum groups = Yes winbind use default domain = Yes admin users = doug, root create mask = 0664 directory mask = 0775 cups options = raw case sensitive = No msdfs proxy = no The shares are pretty standard. I can access the clients, but whenever I try to access my Linux server, I get the following results. Anonymous login successful tree connect failed: NT_STATUS_BAD_NETWORK_NAME Domain=[MCCLATCHEY] os=[Unix] Server=[Samba 3.0.23d-6-1083-SUSE-SL10.2] But what is interesting is what shows up in log.smbd, which is not the entire log, just what shows up after I try to connect? [2007/01/09 08:53:07, 3, pid=20629, effective(0, 0), real(0, 0)] smbd/service.c:make_connection(1120) refusing connection to dfs proxy share 'ipc$' (pointing to no) [2007/01/09 08:53:07, 3, pid=20629, effective(0, 0), real(0, 0)] smbd/error.c:error_packet(146) error packet at smbd/reply.c(676) cmd=117 (SMBtconX) NT_STATUS_BAD_NETWORK_NAME [2007/01/09 08:53:07, 3, pid=20629, effective(0, 0), real(0, 0)] smbd/process.c:timeout_processing(1359) timeout_processing: End of file from client (client has disconnected). [2007/01/09 08:53:07, 3, pid=20629, effective(0, 0), real(0, 0)] smbd/sec_ctx.c:set_sec_ctx(241) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2007/01/09 08:53:07, 3, pid=20629, effective(0, 0), real(0, 0)] smbd/connection.c:yield_connection(69) Yielding connection to [2007/01/09 08:53:07, 3, pid=20629, effective(0, 0), real(0, 0)] smbd/server.c:exit_server_common(675) Server exit (normal exit) If there is any more information you need, please let me know, as I would be more than happy to send you my configuration and log files if it will help to resolve this issue. Thanks Loads! ldmcclatchey@gmail.com
Do you have settings for ipc$ in your smb.conf? Volker
I adjusted my smb.conf logging to: log level = 3 passdb:5 auth:10 winbind:2 Attempted to log into the machine and found an entry in the log to the effect msdfs proxy = yes. After I created my original config file, I used Swat to update it. Swat put that entry in there, I went back and changed it and it had no effect, but when I commented that entry out of the config file, I was able to successfully access the samba server! So it seems that it is Swat that has problems since it likes to rewrite the config file adding entries along the way? Thanks Leon McClatchey
can't see where swat changes the msdfs proxy parameter. Please reopen this if you see this again in recent versions of samba.