I am having the same problem referred to in bug 4535. The resolution there is to turn off msdfs, however this does not help me as I need this functionality. Today I have tested 3.0.25c (on SLES 10SP1) and the problem is still there.
The problem is not apparent with Microsoft shares or NetApp CIFS shares.
Symantec say the problem is with Novell's file "nwfilter.sys" from analysis of our crash dump.
We have raised a bug with Novell. Their workaround for now is to turn off "UNC Path Filter" in the "Advanced Settings" tab of the Novell Client Properties which seems to work.
The problem can be avoided if we either don't push out any Windows updates to newly installed pcs or remove Symantec antivirus.
So, to resolve this, please reproduce exactly the same scenario with a NetApp-based MSDFS root server, and do a comparative sniff. Do a tcpdump with the files residing on the NetApp MSDFS root share, as you would do with Samba, and then the same with the files residing on Samba. Then we can compare and see what Samba does wrong. But please create the same environment on both hosts.
Why is this our bug? We already work around enough bug in Windows.
Do we now have to start working about bugs in Novell's client
redirector as well?
Fair enough, I've done the testing and put DFS on NetApp and the problem moves with it. I didn't appreciate the role of the DFS host. Sorry to bother you.