Am Fr, den 05.08.2005 schrieb Claude Jones um 3:09: > 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 From log list: 192.168.2.1 was 192.168.0.101 before, or where does that IP come from? > 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 The above log look proper to me. Is "VRPRODUCTIONS2" the netbios name of the "Linuxbox"? I am missing the "Studybox" name query. > 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 It is mostly ever a good thing to post the exact error string, rather than saying "an error appeared" ;) > 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... I can't help myself, but as you are trying to get things running for several days now, and meanwhile it is hard to follow what you changed when to what (maybe you yourself lost the line), it may be reasonable to start from scratch? I mean, stop Samba, remove all Samba logs, review smb.conf and strip it down to just the basic needs, review your network setup (IPs given, DHCP, DNS, machine names, /etc/hosts files, Windows® network settings, firewalling) and then start just using 2 machines: Samba and 1 single client host. > Claude Jones Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 16:24:28 up 14:27, 18 users, 0.10, 0.11, 0.24
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
