[Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Hi, I can't get access to any shares when running "smbclient //DUCK/test -U Dominic". I'm getting the message: tree connect failed: NT_STATUS_BAD_NETWORK_NAME I'm pretty sure it's authenticating properly as it says "session setup ok" in the debug output. If I enter the wrong password I get: "session setup failed: NT_STATUS_LOGON_FAILURE" I'm running CentOS 5.4 with the following samba packages samba-common-3.0.33-3.15.el5_4.1 samba-3.0.33-3.15.el5_4.1 samba-swat-3.0.33-3.15.el5_4.1 samba-client-3.0.33-3.15.el5_4.1 My samba setup uses LDAP for authentication. All logging seems to indicate that authentication and LDAP is working well. My /etc/samba/smb.conf was generated with SWAT and has the following shares: [tmp] comment = temporary files path = /tmp hosts allow = hosts deny = [test] comment = test files path = /test hosts allow = hosts deny = Both shares contain a file called myfile.txt. When I connect to the "tmp" share, I don't get the "tree connect failed: NT_STATUS_BAD_NETWORK_NAME", but I can't list any files: [r...@duck cache]# smbclient //DUCK/tmp -U dominic Password: Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1] smb: \> ls . D0 Mon Dec 28 04:02:13 2009 .. D0 Sun Dec 27 21:16:53 2009 36224 blocks of size 8388608. 34082 blocks available smb: \> When I connect to the "test" share I get the "tree connect failed: NT_STATUS_BAD_NETWORK_NAME": [r...@duck cache]# smbclient //DUCK/test -U dominic Password: Domain=[ORANDA] OS=[Unix] Server=[Samba 3.0.33-3.15.el5_4.1] tree connect failed: NT_STATUS_BAD_NETWORK_NAME The permissions on the /tmp and /test folders are the same: drwxrwxrwt 2 root root 4096 Dec 27 21:35 test drwxrwxrwt 4 root root 4096 Dec 28 04:02 tmp There are no complex acls on them either: [r...@duck /]# getfacl tmp # file: tmp # owner: root # group: root user::rwx group::rwx other::rwx [r...@duck /]# getfacl test # file: test # owner: root # group: root user::rwx group::rwx other::rwx I've tried getting more debug info by setting log levels to 10 in both smb.conf and using the -d10 parameter on the command line, but it gives me nothing useful in the logs or in the output. I've been through 'The Samba Checklist' (http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html) and had no other problems. Here is the rest of my smb.conf: [global] workgroup = ORANDA server string = Duck passdb backend = ldapsam:ldap://localhost/ pam password change = Yes passwd program = /usr/sbin/smbldap-passwd %u passwd chat = *New*password* %n\n *Retype*new*password* %n\n *all*authentication*tokens*updated* unix password sync = Yes log level = 10 log file = /var/log/samba/log.%m load printers = No printcap name = /dev/null disable spoolss = Yes add user script = /usr/sbin/smbldap-useradd -m "%u" delete user script = /usr/sbin/smbldap-userdel "%u" add group script = /usr/sbin/smbldap-groupadd -p "%g" delete group script = /usr/sbin/smbldap-groupdel "%g" add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g" delete user from group script = /usr/sbin/smbldap-groupmod -x "%u" "%g" set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u" add machine script = /usr/sbin/smbldap-useradd -w "%u" logon script = login.cmd logon path = \\%N\profiles\%U logon drive = H: domain logons = Yes os level = 127 wins support = Yes ldap admin dn = cn=admin,dc=oranda,dc=internal ldap delete dn = Yes ldap group suffix = ou=Group ldap idmap suffix = ou=Idmap ldap machine suffix = ou=Computers ldap passwd sync = Yes ldap suffix = dc=oranda,dc=internal ldap user suffix = ou=People panic action = /usr/share/samba/panic-action %d admin users = dominic hosts allow = 192.168.10., 127. hosts deny = ALL printing = bsd print command = lpr -r -P'%p' %s lpq command = lpq -P'%p' lprm command = lprm -P'%p' %j use client driver = Yes This has had me stumped for 3 days straight now and I don't know what else I can try. Samba just isn't giving me any more clues. I've found lots of other posts like mine through google with no replies to them. Does anyone have any ideas of what to do next? I would greatly appreciate if someone could point me in the right direction. Best regards, Dominic. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] slow printing from windows xp to a samba print share
uh oh, could this be the dreaded xp client bug? Follow this thread and it's related suggestions to see if it fixes your problem: http://lists.samba.org/archive/samba/2005-September/110571.html Ralph Blach wrote: I have a windows xp maching which have very slow printing to a linux samba server I am running fedora core 10 x86_64 as the serverr and here is my smb.conf file THIS IS THE MAIN sAMBA CONFIGURATION FILE. yOU SHOULD REAd the # SMB.Conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options (perhaps too # MAny!) most of which are not shown in this example # # For a step to step guide on installing, configuring and using samba, # read the Samba-HOWTO-Collection. This may be obtained from: # http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf # # Many working examples of smb.conf files can be found in the # Samba-Guide which is generated daily and can be downloaded from: # http://www.samba.org/samba/docs/Samba-Guide.pdf # # Any line which starts with a ; (semi-colon) or a # (hash) # is a comment and is ignored. In this example we will use a # # for commentry and a ; for parts of the config file that you # may wish to enable # # NOTE: Whenever you modify this file you should run the command "testparm" # to check that you have not made any basic syntactic errors. # #--- # SELINUX NOTES: # # If you want to use the useradd/groupadd family of binaries please run: # setsebool -P samba_domain_controller on # # If you want to share home directories via samba please run: # setsebool -P samba_enable_home_dirs on # # If you create a new directory you want to share you should mark it as # "samba-share_t" so that selinux will let you write into it. # Make sure not to do that on system directories as they may already have # been marked with othe SELinux labels. # # Use ls -ldZ /path to see which context a directory has # # Set labels only on directories you created! # To set a label use the following: chcon -t samba_share_t /path # # If you need to share a system created directory you can use one of the # following (read-only/read-write): # setsebool -P samba_export_all_ro on # or # setsebool -P samba_export_all_rw on # # If you want to run scripts (preexec/root prexec/print command/...) please # put them into the /var/lib/samba/scripts directory so that smbd will be # allowed to run them. # Make sure you COPY them and not MOVE them so that the right SELinux context # is applied, to check all is ok use restorecon -R -v /var/lib/samba/scripts # #-- # #=== Global Settings = [global] # --- Netwrok Related Options - # # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH # # server string is the equivalent of the NT Description field # # netbios name can be used to specify a server name not tied to the hostname # # Interfaces lets you configure Samba to use multiple interfaces # If you have multiple network interfaces then you can list the ones # you want to listen on (never omit localhost) # # Hosts Allow/Hosts Deny lets you restrict who can connect, and you can # specifiy it as a per share option as well # workgroup = chipsdomain server string = Samba Server Version %v ;netbios name = MYSERVER interfaces = lo wlan0 eth0 hosts allow = 127.0.0.1 10.0.0.0/24 ;null passwords = yes # --- Logging Options - # # Log File let you specify where to put logs and how to split them up. # # Max Log Size let you specify the max size log files should reach # logs split per machine log file = /var/log/samba/log.%m # max 50KB per log file, then rotate max log size = 50 log level = 5 # --- Standalone Server Options # # Scurity can be set to user, share(deprecated) or server(deprecated) # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. security = user passdb backend = tdbsam # --- Domain Members Options # # Security must be set to domain or ads # # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # # Use password server option only with security = server or if you can't # use the DNS to locate Domain Controllers # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * ;realm = MY_REALM ;password server
[Samba] NTLMv2 in Sun's 'official' Samba 3.0.37?
Hi all. Just looking for some guidance as to what works, and what doesn't. Recently I've noticed that no matter what I do, I can't seem to get NTLMv2 to negotiate using Windows Vista, Windows 7 or Mac OS X 10.6.x against Solaris 10 Samba 3.0.37. If I 'tune' the client OS that it only negotiates with NTLMv1, all is well. In my global block, on the Solaris Samba server, I have: [global] client lanman auth=no client ntlmv2 auth=yes ntlm auth = no Now, I'd have thought that this would be enough to make NTLMv2 work along it's merry way - but apparently not. Whenever I attempt to connect and negotiate using NTLMv2, the client OS is given a generic 'incorrect username or password' response. So - the question. Does 3.0.37 actually even support NTLMv2? Am I doing something wrong in trying to turn it 'on'? Sun aren't talking, but I'm sure somebody here would know the history behind this... Thanks all. JC -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] slow printing from windows xp to a samba print share
I have a windows xp maching which have very slow printing to a linux samba server I am running fedora core 10 x86_64 as the serverr and here is my smb.conf file THIS IS THE MAIN sAMBA CONFIGURATION FILE. yOU SHOULD REAd the # SMB.Conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options (perhaps too # MAny!) most of which are not shown in this example # # For a step to step guide on installing, configuring and using samba, # read the Samba-HOWTO-Collection. This may be obtained from: # http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf # # Many working examples of smb.conf files can be found in the # Samba-Guide which is generated daily and can be downloaded from: # http://www.samba.org/samba/docs/Samba-Guide.pdf # # Any line which starts with a ; (semi-colon) or a # (hash) # is a comment and is ignored. In this example we will use a # # for commentry and a ; for parts of the config file that you # may wish to enable # # NOTE: Whenever you modify this file you should run the command "testparm" # to check that you have not made any basic syntactic errors. # #--- # SELINUX NOTES: # # If you want to use the useradd/groupadd family of binaries please run: # setsebool -P samba_domain_controller on # # If you want to share home directories via samba please run: # setsebool -P samba_enable_home_dirs on # # If you create a new directory you want to share you should mark it as # "samba-share_t" so that selinux will let you write into it. # Make sure not to do that on system directories as they may already have # been marked with othe SELinux labels. # # Use ls -ldZ /path to see which context a directory has # # Set labels only on directories you created! # To set a label use the following: chcon -t samba_share_t /path # # If you need to share a system created directory you can use one of the # following (read-only/read-write): # setsebool -P samba_export_all_ro on # or # setsebool -P samba_export_all_rw on # # If you want to run scripts (preexec/root prexec/print command/...) please # put them into the /var/lib/samba/scripts directory so that smbd will be # allowed to run them. # Make sure you COPY them and not MOVE them so that the right SELinux context # is applied, to check all is ok use restorecon -R -v /var/lib/samba/scripts # #-- # #=== Global Settings = [global] # --- Netwrok Related Options - # # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH # # server string is the equivalent of the NT Description field # # netbios name can be used to specify a server name not tied to the hostname # # Interfaces lets you configure Samba to use multiple interfaces # If you have multiple network interfaces then you can list the ones # you want to listen on (never omit localhost) # # Hosts Allow/Hosts Deny lets you restrict who can connect, and you can # specifiy it as a per share option as well # workgroup = chipsdomain server string = Samba Server Version %v ;netbios name = MYSERVER interfaces = lo wlan0 eth0 hosts allow = 127.0.0.1 10.0.0.0/24 ;null passwords = yes # --- Logging Options - # # Log File let you specify where to put logs and how to split them up. # # Max Log Size let you specify the max size log files should reach # logs split per machine log file = /var/log/samba/log.%m # max 50KB per log file, then rotate max log size = 50 log level = 5 # --- Standalone Server Options # # Scurity can be set to user, share(deprecated) or server(deprecated) # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. security = user passdb backend = tdbsam # --- Domain Members Options # # Security must be set to domain or ads # # Use the realm option only with security = ads # Specifies the Active Directory realm the host is part of # # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration. # # Use password server option only with security = server or if you can't # use the DNS to locate Domain Controllers # The argument list may include: # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name] # or to auto-locate the domain controller/s # password server = * ;realm = MY_REALM ;password server = # --- Domain Controller Options # # Security must be set to user for domain controllers # # Backend to store user information in. New installations should # use either td
