I reported about this in December when it seemed I was the first one who stumbled across this. I written the developers twice about it by now and it is still not fixed. Now it is kind of annoying since I get a bunch of people email me every week asking the same question again and again. If you use XP and Samba and veto files in smb.conf then you must use veto files = /.?*/ and not veto files = /.*/ to avoid this error on the client side: [path] refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information might have been moved to another location. Thanks, Marcel
Marcel Kunath wrote:> > I reported about this in December when it seemed I was the first one who > stumbled across this. I written the developers twice about it by now and it is > still not fixed. Now it is kind of annoying since I get a bunch of people email > me every week asking the same question again and again.What are you proposing as the fix? Can you include a patch?> If you use XP and Samba and veto files in smb.conf then you must use > > veto files = /.?*/ > > and not > > veto files = /.*/ > > to avoid this error on the client side:There are many ways to configure samba to make it inoperable, but we should at least document it. A patch for the docbook sources would go down nicely. Andrew Bartlett -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net