> | I have "log file = /var/log/samba/%m.log" also set > | in the smb.conf file. > > This should help explain why. > > http://marc.theaimsgroup.com/?l=samba&m=110029538204413&w=2
I've already read that post but the behaviour I perceived was different. See the other thread I mentioned. url: http://lists.samba.org/archive/samba/2005-April/104024.html I've looked into the samba code to find the place where the substitutions take place. >From the results, two places were possible: [EMAIL PROTECTED] source]$ grep -rH set_remote_machine_name . [..] ./smbd/reply.c: set_remote_machine_name(name2, True); ./smbd/server.c: set_remote_machine_name(get_peer_addr(smbd_server_fd()), False); [..] In reply.c, near the matching line, there was this code: [..] DEBUG(2,("netbios connect: name1=%s name2=%s\n", name1,name2)); [..] I looked through the log files, and only found this debug message in the log file for a linux client, from which I connected with smbclient. Then I realized, that all the clients in our network are WindowsXP clients with the following network protocols installed: - Client for Microsoft Networks - File and Printer Sharing for Microsoft Networks - QoS Packet Scheduler - Internet Protocol (TCP/IP) Now I'm no Microsoft networking expert, but is it possible, that these machines don't use NetBIOS at all? If they don't, can Samba handle that transparently? In server.c, the looks like this: [..] set_remote_machine_name(get_peer_addr(smbd_server_fd()), False); [..] This sets the remote machine name variable in lib/substitute.c to the IP address. This explains why it's not substituted for smb.conf.netbios_name If you could help me debug my problem, can you please point me to the code where the variable remote_machine is changed to the netbios name of the connecting machine? Thanks, Kolos -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba