On Thu August 4 2005 3:28 am, Andy Pieters wrote: > Hi > > There is nothing you must do to configure WINS. Specifying that it is > enabled is enough. > > To make things easier to debug, add the following entry to the global > section of the sm.conf > > log file=/var/log/samba/smb.log.%m > log level=3 > > restart samba > try to connect again with that windows box > now examine the log file > go to the directory /var/log/samba and you should see a file that ends with > the ip address of the misbehaving box. Examine it and if you don't > understand what it says, please post it here. > After following your instructions, modifying the smb.conf file and restarting samba and trying to connect to studypc, this is the list of logs that appear in the Samba directory. As you can see, the offending machine, called studypc doesn't appear smb.log.**** entries. The studypc logs that exist are older. file:///var/log/samba/192.168.2.101.log file:///var/log/samba/192.168.2.252.log file:///var/log/samba/192.168.2.254.log file:///var/log/samba/fhb.log file:///var/log/samba/julimobile.log file:///var/log/samba/julimobile.log.1 file:///var/log/samba/nmbd.log file:///var/log/samba/nmbd.log.1 file:///var/log/samba/nmbd.log.old file:///var/log/samba/smbd.log file:///var/log/samba/smbd.log.1 file:///var/log/samba/smb.log.192.168.2.1 file:///var/log/samba/smb.log.192.168.2.254 file:///var/log/samba/smb.log.julimobile file:///var/log/samba/smb.log.smbd file:///var/log/samba/smb.log.vrproductions2 file:///var/log/samba/studypc.log file:///var/log/samba/studypc.log.1 file:///var/log/samba/swat.log In my scenario: Linuxbox is 192.168.2.1 Studypc is 192.168.2.252 Julimobile is 192.168.2.254 Connecting Linuxbox>Studypc results in error Connecting Linuxbox>192.168.2.252 results in connection No log is generate for either attempt. The smbd.log has no additional lines in it after the try. The nmbd.log has the following: [2005/08/04 20:58:07, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(454) process_name_query_request: Name query from 192.168.2.252 on subnet 192.168.2.1 for name VRPRODUCTIONS2<00> [2005/08/04 20:58:07, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(569) OK [2005/08/04 20:58:07, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(454) process_name_query_request: Name query from 192.168.2.252 on subnet 192.168.2.1 for name VRPRODUCTIONS2<20> [2005/08/04 20:58:07, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(569) OK [2005/08/04 20:58:07, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(454) process_name_query_request: Name query from 192.168.2.252 on subnet 192.168.2.1 for name JULIMOBILE<20> [2005/08/04 20:58:07, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(454) process_name_query_request: Name query from 192.168.2.252 on subnet 192.168.2.1 for name JULIMOBILE<00> [2005/08/04 20:58:08, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(454) process_name_query_request: Name query from 192.168.2.252 on subnet 192.168.2.1 for name JULIMOBILE<20> [2005/08/04 20:59:08, 3] nmbd/nmbd_sendannounce.c:send_local_master_announcement(166) send_local_master_announcement: type c9a03 for name VRPRODUCTIONS2 on subnet 192.168.2.1 for workgroup WORKGROUP [2005/08/04 20:59:08, 3] nmbd/nmbd_sendannounce.c:send_workgroup_announcement(185) send_workgroup_announcement: on subnet 192.168.2.1 for workgroup WORKGROUP [2005/08/04 21:01:39, 3] nmbd/nmbd_winsserver.c:wins_process_name_query_request(1485) wins_process_name_query: name query for name *<1b> from IP 127.0.0.1 [2005/08/04 21:02:04, 2] nmbd/nmbd_browsesync.c:announce_local_master_browser_to_domain_master_browser(110) announce_local_master_browser_to_domain_master_browser: We are both a domain and a local master browser for workgroup WORKGROUP. Do not announce to ourselves. [2005/08/04 21:02:04, 2] nmbd/nmbd_browsesync.c:sync_with_dmb(154) sync_with_dmb: Initiating sync with domain master browser VRPRODUCTIONS2<20> at IP 192.168.2.1 for workgroup WORKGROUP Any other ideas, sherpas Pieters or Dalloz? One other oddity. Studypc has two hard drives C: and F: - both have been shared. When I connect using the IP address, C: is browsable, but F: displays only the root folders - if I try to browse any folder, it returns an error. I have gone over the Windows settings for shares a half dozen times, but I can't see any difference between the settings for C and F... -- Claude Jones Bluemont, VA, USA
