derekmahar.12026693@bloglines.com
2005-Jun-15 01:35 UTC
[Samba] FC4, Samba 3.0.14-2, Windows 2K: cannot access home directory
What might be the possible causes of an smbclient NT_STATUS_BAD_NETWORK_NAME error? smbclient generates this error when I attempt to connect to my [homes] share from a Mandrake Linux 10.1 (Samba 3.0.7) box to my Fedora Core 4 box (Samba 3.0.14a-2). Similarly, my Windows 2000 machine complains that folder "\\Fedora\derek is not accessible. The network name cannot be found." I can browse all the shares and read shares 'public' and 'data' (see below), but despite having both Samba and file write permissions, I cannot write to these shares. I do not encounter these problems on my Mandrake 10.1 PC (Samba 3.0.7). What might be the problem and what is the solution? Has Samba changed significantly between versions 3.0.7 and 3.0.14a-2? Server configuration: Fedora Core 4 Samba 3.0.14a-2 Windows 2000 --- Output of smbclient: [derek@linux derek]$ smbclient //fedora/derek -U derek Password: Domain=[FEDORA] OS=[Unix] Server=[Samba 3.0.14a-2] tree connect failed: NT_STATUS_BAD_NETWORK_NAME --- Excerpt from /var/log/samba/derek.log: [2005/06/14 21:06:41, 2] auth/auth.c:check_ntlm_password(305) check_ntlm_password: authentication for user [derek] -> [derek] -> [derek] succeeded [2005/06/14 21:06:41, 1] smbd/service.c:make_connection_snum(642) derek (192.168.1.101) connect to service data initially as user derek (uid=500, gid=500) (pid 2800) [2005/06/14 21:07:28, 0] smbd/service.c:make_connection_snum(615) '/home/derek' does not exist or is not a directory, when connecting to [derek] [2005/06/14 21:07:29, 0] smbd/service.c:make_connection_snum(615) '/home/derek' does not exist or is not a directory, when connecting to [derek] [2005/06/14 21:07:29, 0] smbd/service.c:make_connection_snum(615) '/home/derek' does not exist or is not a directory, when connecting to [derek] [2005/06/14 21:07:29, 0] smbd/service.c:make_connection_snum(615) '/home/derek' does not exist or is not a directory, when connecting to [derek] --- Output of testparm: [root@fedora data]# testparm Load smb config files from /etc/samba/smb.conf Processing section "[homes]" Processing section "[printers]" Processing section "[public]" Processing section "[data]" Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions # Global parameters [global] workgroup = ROSEMONT server string = Fedora Core, Samba Server %v passwd program = /usr/bin/passwd %u passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully* unix password sync = Yes log level = 2 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 dns proxy = No cups options = raw [homes] comment = %u's Home Directory read only = No browseable = No [printers] comment = All Printers path = /var/spool/samba guest ok = Yes printable = Yes browseable = No [public] comment = Public folder path = /usr/share/public read only = No guest ok = Yes [data] comment = Data folder path = /data read only = No guest ok = Yes --- Shared directory file permissions: [root@fedora data]# ls -ld /home/derek /data /usr/share/public drwxrwxrwx 2 root root 4096 Jun 14 20:59 /data drwx------ 29 derek derek 4096 Jun 14 20:55 /home/derek drwxrwxrwx 2 root root 4096 Jun 13 21:37 /usr/share/public Thank you for your help! Derek
Nazrul Izham Abdul Ghaffar
2005-Jul-05 16:17 UTC
[Samba] FC4, Samba 3.0.14-2, Windows 2K: cannot access home directory
On FC4 you need to make SELinux permissive before you can get your samba works as Ed Oliver said You can do this by changing the line SELINUX=enforcing to SELINUX=permissive in file named config in /etc/selinux So far it works well with me.