Bug#424610: NT_STATUS_OBJECT_PATH_NOT_FOUND also
On 5/17/07, Christian Perrier [EMAIL PROTECTED] wrote: Which version of samba? Do you run etch (ie samba 3.0.24-6etch1) or unstable (so, 3.0.25-1)? 3.0.25-1 Could you try sending us a level 10 log of the error? In the process of doing this, I rebooted my Windows box and the problem went away. Chalk this up to a Heisenbug. As far as I am concerned, this can be closed but you'd need to get more info from the original reporter. -- Caleb Epstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#424610: NT_STATUS_OBJECT_PATH_NOT_FOUND also
forwarded 424610 https://bugzilla.samba.org/show_bug.cgi?id=4619 thanks Quoting Caleb Epstein ([EMAIL PROTECTED]): On 5/17/07, Christian Perrier [EMAIL PROTECTED] wrote: Which version of samba? Do you run etch (ie samba 3.0.24-6etch1) or unstable (so, 3.0.25-1)? 3.0.25-1 Could you try sending us a level 10 log of the error? In the process of doing this, I rebooted my Windows box and the problem went away. Chalk this up to a Heisenbug. As far as I am concerned, this can be closed but you'd need to get more info from the original reporter. Apparently, someone else in Samba bug #4619 also found out that just disconnecting the shares and reconnect them is enough to solve the bug Let's record that this bug is very very probably samba bug #4619 signature.asc Description: Digital signature
Bug#424610: NT_STATUS_OBJECT_PATH_NOT_FOUND also
I'm getting this same error. At first I was getting password expiration errors (thats new!), but resetting my password fixed those. Now I'm getting NT_STATUS_OBJECT_PATH_NOT_FOUND errors. As a result, I can't attach to any of my shares. Everything worked fine until this upgrade. See attached for my smb.conf. -- Caleb Epstein smb.conf Description: Binary data
Bug#424610: NT_STATUS_OBJECT_PATH_NOT_FOUND also
Quoting Caleb Epstein ([EMAIL PROTECTED]): I'm getting this same error. Which version of samba? Do you run etch (ie samba 3.0.24-6etch1) or unstable (so, 3.0.25-1)? Could you try sending us a level 10 log of the error? That would mean setting log level to 10.restart sambaempty the log filetry the connection experiencing the failure.immediately stop samba and send us the (compressed) log file. Combined with your smb.conf that would make enough information to send out to upstream. If you can do exactly the same, but with the former samba version (the one that works), that'd be perfect. signature.asc Description: Digital signature
