> On Sat, Apr 21, 2018, 1:24 AM Rupert Gallagher <r...@protonmail.com> wrote: > > > This is what I observed on a controlled environment of three "windows 10 > > pro" 1709 clients. > > > > The obsd nfs server had a single share: > > > > /path/to/folder -network 192.168.1 -mask 255.255.255.0 > > > > When mounting a share for the first time, Windows allows browsing the > > network to find the resource. This is what happens: > > > > 1. The client asks for the list of nfs resources; > > 2. the server shows a stream of accepted mounts, no warnings, no errors; > > 3. while 2 happens, the client shows a warning that the server is not > > responding; > > 4. when eventually the client returns the list of nfs folders, the server > > crashes. > > > > The above occurs systematically. Restarting the server and repeating the > > client steps lead to a new server crash. The only way to mount the share is > > to type in the path, without browsing. > > > > When the server crashes, the debug shows no warnings and no errors. > > > > The problem did not occur with W10Pro 1703. However, the server should not > > crash, and if it does, it should report useful diagnostics.
Packet captures from broken and working clients would be a good start to figuring out what's going on. On 2018/04/21 06:31, MB wrote: > Why are you using ooenbsd for anything but a firewall. Even then its > lagging way behind unless you deploying in a dentist office. Openbsd sucks > at pretty much everything else. Sorry I come from corporate real world > experience not Soho stuff. Use Linux. Or Windows, you might as well get some nice features to go with the complex mess.
