Have Linux FC 3 (smb 3.0.8) and upgraded to FC 4 (smb 3.0.14a). Samba server does not work since upgrade of Fedora Core. Have done extensive troubleshooting, but cannot get further in determining why nmbd does not work. Details of troubleshooting follow: Following guidelines of Procedure 37.1, Diagnosing your Samba server (http:// us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html), the following results are obtained. Preliminary: system-config-services reports that daemons nmbd, smbd and winbindd are running. Specifically, nmbd is running one process (pid 4418), smbd is running two (pid 4420 4416), and winbindd is running two (pid 2452 2445). 1. Check the configuration file. [root@Home_Linux samba]# pwd /etc/samba [root@Home_Linux samba]# testparm smb.conf Load smb config files from smb.conf Processing section "[homes]" Processing section "[printers]" Processing section "[J William Cupp's Desktop]" Processing section "[Cindy's Desktop]" Processing section "[Shandalyn's Desktop]" Processing section "[Rebecca's Desktop]" Processing section "[Rachel's Desktop]" Loaded services file OK. WARNING: You have some share names that are longer than 12 characters. These may not be accessible to some older clients. (Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.) Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions # Global parameters [global] workgroup = BREEZEWOODGROUP server string = Samba Server password server = None username map = /etc/samba/smbusers 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 idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 cups options = raw [homes] comment = Home Directories read only = No browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [J William Cupp's Desktop] comment = J William Cupp's Desktop path = /home/jwilliamcupp/Desktop valid users = jwilliamcupp read only = No [Cindy's Desktop] comment = Cindy's Desktop path = /home/cindycupp/Desktop valid users = cindycupp read only = No [Shandalyn's Desktop] path = /home/shandalyn/Desktop valid users = shandalyn read only = No [Rebecca's Desktop] path = /home/rebecca/Desktop valid users = rebecca read only = No [Rachel's Desktop] path = /home/rachel/Desktop valid users = rachel read only = No [root@Home_Linux samba]# 2. Ping the server from the client and the client from the server. The server is named Home_Linux on IP 192.168.0.100 and the client is iwu-50196 on IP 192.168.0.105. [root@Home_Linux samba]# ping 192.168.0.105 PING 192.168.0.105 (192.168.0.105) 56(84) bytes of data. 64 bytes from 192.168.0.105: icmp_seq=0 ttl=128 time=4.97 ms 64 bytes from 192.168.0.105: icmp_seq=1 ttl=128 time=2.39 ms 64 bytes from 192.168.0.105: icmp_seq=2 ttl=128 time=1.78 ms 64 bytes from 192.168.0.105: icmp_seq=3 ttl=128 time=1.77 ms 64 bytes from 192.168.0.105: icmp_seq=4 ttl=128 time=1.75 ms 64 bytes from 192.168.0.105: icmp_seq=5 ttl=128 time=1.77 ms 64 bytes from 192.168.0.105: icmp_seq=6 ttl=128 time=1.79 ms --- 192.168.0.105 ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6005ms rtt min/avg/max/mdev = 1.751/2.324/4.979/1.104 ms, pipe 2 [root@Home_Linux samba]# ping iwu-50196 ping: unknown host iwu-50196 Microsoft(R) Windows DOS (C)Copyright Microsoft Corp 1990-2001. C:\DOCUME~1\JWILLI~1.CUP>ping 192.168.0.100 Pinging 192.168.0.100 with 32 bytes of data: Reply from 192.168.0.100: bytes=32 time<1ms TTL=64 Reply from 192.168.0.100: bytes=32 time<1ms TTL=64 Reply from 192.168.0.100: bytes=32 time<1ms TTL=64 Reply from 192.168.0.100: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.0.100: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\DOCUME~1\JWILLI~1.CUP>ping Home_Linux Pinging Home_Linux [192.168.0.100] with 32 bytes of data: Reply from 192.168.0.100: bytes=32 time<1ms TTL=64 Reply from 192.168.0.100: bytes=32 time<1ms TTL=64 Reply from 192.168.0.100: bytes=32 time<1ms TTL=64 Reply from 192.168.0.100: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.0.100: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\DOCUME~1\JWILLI~1.CUP> Inspecting DNS server: [root@Home_Linux etc]# pwd /etc [root@Home_Linux etc]# cat resolv.conf ; generated by /sbin/dhclient-script search Breezewood nameserver 192.168.0.1 [root@Home_Linux etc]# Note that 192.168.0.1 is the wireless router which is running DCHP and has assigned the present IP addresses. The following is the present setting of the DCHP static addresses table in the wireless router: Static DHCP Client List Host Name IP Address MAC Address Upstairs 192.168.0.102 00-11-95-83-8D-AC Home_Linux 192.168.0. 100 00-0E-A6-90-46-CC iwu-50196 192.168.0.104 00-0B-5D-52- 38-AD iwu-50196_wireless 192.168.0.105 00-0E-35-50-B2-A9 Note further that this part of the configuration has not changed. The Samba server connected the Windows XP "iwu-50196" and Windows 98 "Upstairs" with the Linux "Home_Linux" using the same DHCP static table in the wireless router prior to upgrading Fedora Core 3 to Fedora Core 4. 3. Check for available shares on the server. [root@Home_Linux etc]# smbclient -L Home_Linux Password: Domain=[HOME_LINUX] OS=[Unix] Server=[Samba 3.0.14a-2] Sharename Type Comment --------- ---- ------- IPC$ IPC IPC Service (Samba Server) ADMIN$ IPC IPC Service (Samba Server) HP1209 Printer All in one printer scanner copier. jwilliamcupp Disk Home Directories Domain=[HOME_LINUX] OS=[Unix] Server=[Samba 3.0.14a-2] Server Comment --------- ------- Workgroup Master --------- ------- BREEZEWOODGROUP HOME_LINUX [root@Home_Linux etc]# 4. Confirm nmb services are available to the server. [root@Home_Linux etc]# nmblookup -B Home_Linux __SAMBA__ querying __SAMBA__ on 127.0.0.1 192.168.0.100 __SAMBA__<00> [root@Home_Linux etc]# 5. Confirm the availability of the client on the network. [root@Home_Linux etc]# nmblookup -B iwu-50196 '*' querying * on 0.0.0.0 192.168.0.100 *<00> [root@Home_Linux etc]# nmblookup -B 192.168.105 '*' querying * on 192.168.0.105 192.168.0.105 *<00> 192.168.0.106 *<00> [root@Home_Linux etc]# The domain name did not respond (as expected from above). The query using the IP address returned both the wireless network connection (-105) and the wired connection (-106). [For some reason, the assigned static IP address was not assigned to the wired connection, and the dynamic address -106 was assigned for this connection. I don't know why that happened, but it should not affect Samba.] 6. Repeat the above tests via broadcast. [root@Home_Linux etc]# nmblookup -d 2 '*' added interface ip=192.168.0.100 bcast=192.168.0.255 nmask=255.255.255.0 querying * on 192.168.0.255 name_query failed to find name * ... and for good measure: [root@Home_Linux etc]# nmblookup -d 3 '*' lp_load: refreshing parameters Initialising global parameters params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" Processing section "[global]" added interface ip=192.168.0.100 bcast=192.168.0.255 nmask=255.255.255.0 Socket opened. querying * on 192.168.0.255 name_query failed to find name * [root@Home_Linux etc]# A check of the client iwu-50196 ipconfig reports that it is indeed using subnet mask 255.255.255.0 and default gateway 192.168.0.1, so it should have caught the broadcast. 7. Confirm that smb is available from the console. [root@Home_Linux etc]# smbclient //Home_Linux/jwilliamcupp Password: Domain=[HOME_LINUX] OS=[Unix] Server=[Samba 3.0.14a-2] smb: \> dir . D 0 Fri Aug 5 16:23:57 2005 .. D 0 Sun May 22 23:28:14 2005 .bash_logout H 24 Tue Feb 11 08:34:44 2003 .bash_profile H 191 Tue Feb 11 08:34:44 2003 .bashrc H 124 Tue Feb 11 08:34:44 2003 .emacs H 847 Thu Feb 20 01:41:26 2003 .gtkrc H 120 Wed Feb 26 18:15:12 2003 .gnome2 DH 0 Tue Aug 2 21:03:11 2005 --- --- --- --- LARGE SECTION REMOVED FOR BREVITY -- WE'VE SHOWN IT WORKS --- --- --- --- ScrollingMarquee.txt 152 Thu Jun 23 16:33:08 2005 .openoffice.org2.0 DH 0 Thu Jul 28 17:26:54 2005 .rhn-applet.cache H 11 Fri Aug 5 18:24:39 2005 36961 blocks of size 1048576. 2576 blocks available smb: \> 8. Confirm that smb is available from the console of the client. C:\DOCUME~1\JWILLI~1.CUP>net view \\Home_Linux System error 53 has occurred. The network path was not found. C:\DOCUME~1\JWILLI~1.CUP> -> This is the step that fails! <- Workarounds suggested -- To overcome it, you could do one of the following (you only need to choose one of them): 1. Fix the nmbd installation. THIS IS WHAT I WOULD LIKE TO DO. It worked fine on smb 3.0.8 with Fedora Core 3 and with no other changes does not work with smb 3.0.14a with Fedora Core 4. 2. Add the IP address of BIGSERVER to the wins server box in the advanced TCP/IP setup on the PC. I tried this. No success. 3. Enable Windows name resolution via DNS in the advanced section of the TCP/IP setup. The default setting for my Windows XP network connections already is "Use NetBIOS setting from the DHCP server. If static IP address is used or the DHCP server does not provide NetBIOS setting, enable NetBIOS over TCP/IP." Therefore, Windows name resolution ought to be already possible via DNS. Nevertheless, I tried switching to always-on "Enable NetBIOS over TCP/IP" and this did not help. Add BIGSERVER to your lmhosts file on the PC. I tried this, but am not sure it was done correctly. 9. Confirm the availability of user log in across the network. I can't try this step until the previous one is working. 10. Look for the work group. [root@Home_Linux samba]# nmblookup -M BREEZEWOODGROUP querying BREEZEWOODGROUP on 192.168.0.255 name_query failed to find name BREEZEWOODGROUP#1d The work group does not answer, either. Following the tip, I modified smb.conf to set "preferred master = yes" and cycled smb (stop the service then restart). The results were the same.
After a quick glance, it is not apparent that there is any source bug here. Suggest you post to the main Samba mailing list for configuration debugging help.