coverup Posted February 27, 2005 Report Share Posted February 27, 2005 (edited) I have this funny problem with samba server. The samba server is cofigured in the system services to run on startup. But it always needs restarting afterwards, otherwise other computers on the LAN can't see the server. Here is the content of the /var/log/samba/log.nmbd before and after restart. Right after the computer is started, before the server restart [2005/02/28 06:01:19, 0] nmbd/nmbd.c:main(795) Netbios nameserver version 2.2.8a started. Copyright Andrew Tridgell and the Samba Team 1994-2002 service smb status shows that samba is running smbd (pid 2510) is running... nmbd (pid 2520) is running... but windows computers on the LAN can't see it. Now I am restarting samba, # service smb restart Shutting down SMB services: [ OK ] Shutting down NMB services: [ OK ] Starting SMB services: [ OK ] Starting NMB services: [ OK ] Let's look at the logs. [2005/02/27 20:36:02, 0] nmbd/nmbd.c:terminate(59) Got SIGTERM: going down... [2005/02/27 20:36:02, 0] nmbd/nmbd.c:main(795) Netbios nameserver version 2.2.8a started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2005/02/27 20:36:06, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235) find_response_record: response packet id 6395 received with no matching record. [2005/02/27 20:36:06, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(235) find_response_record: response packet id 6396 received with no matching record. Now, I can browse the server from the Windows boxes, and few new lines are being added to the logs [2005/02/27 20:38:51, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(404) ***** Samba name server LINUXHOST is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.2 ***** Here is a simple question, why does the server need restarting? Any ideas please? Edited February 27, 2005 by coverup Quote Link to comment Share on other sites More sharing options...
coverup Posted February 27, 2005 Author Report Share Posted February 27, 2005 Nevermind, the problem is solved - for some (unrelated) reason, my HW clock was set to GMT. By the time the clock was syncronized to the local time, smb had already been up. Believe it or not, that appeard to matter. Changing HW clock settings to the local time made windows boxes happy. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.