Hello, Le Lundi 08 Mars 2010 05:13:34, vous avez icrit : > On Sun, Mar 7, 2010 at 1:37 PM, Jean-Francois <jfsimon1...@gmail.com> > wrote: ... > > > I am not sure but believe the problem is in smb.conf > > ...but you'll not actually show the contents of that file. I take it > you're taking the problem to the samba mailing lists then?
I used the default file, with "security user" and two mount points shared as user. I then tried to change the paramters as "local master" and "domain master" as explained in the mal and examples. I did not ask to samba mailing list simply because I did not yet suggested it came from smb.conf - I am not sure about this. > > I tried to change many parameters to make nmbd LISTEN and answer UDP/137 > > requests without success. > > Repeat after me: UDP IS STATELESS. Thanks for the reminder. Yet I did not know that for this reason, LISTEN was'nt mentionned. > Indeed, a quick examination of the output of netstat on any OpenBSD > system shows that the state column is *always* empty for UDP sockets. > > As for answering requests, how do you know it isn't? Did you trace > the process? Did you use tcpdump to confirm that the packets were > being received? Have you confirmed that your pf config isn't blocking > them? I did'nt trace the process, but tcpdump show the packets, pflog confirms that the rule pass in pf.conf lets correctly passing the packets. > It's been years since I've had to deal with samba, so I can't really > help you further...other than to point out that you failed to provide > any information about your system or the samba you're running. What > version of OpenBSD? Did you install the samba package from the ftp > site, or did you build the port yourself, or did you download the > source and build it yourself without using the ports framework? It's 4.6 default + samba 3 default from packages. I did not copy all informations such as content of smb.conf and pf.conf as I did not feel it necessary - for the first, it is close enough from default and for the second it's perfectly patching what is needed for process to work. > > Philip Guenther
