I just verified that the UNC path names work if the security is applied properly to the LocalFS Add entry.

From your UNC path it looks like you may be specifying the path incorrectly. You should be pointing LocalFS at a folder name, not a filename. \\server\sharepoint\folder or \\server\sharepoint

Pointing to a filename results in: Error Type: OSError Error Value: [Errno 267] Unknown error Which is invalid directory, because the filename is not a directory.

...

...

-----Original Message----- From: Joel Burton [mailto:jburton@scw.org] Sent: Wednesday, March 28, 2001 9:59 AM To: ASHISHRANJAN_V Cc: zope@zope.org Subject: RE: [Zope] LocalFS product

On Wed, 28 Mar 2001, ASHISHRANJAN_V wrote:

...

I regret , I could not put the complete information in my previous mail. Zope runs on WIN2k/ Windows Nt . The shared file is on an windows workstation. I have given \\computername\sharename\filename as path And Windows domain name and password for accessing the file . Still it gives the error : Error Type: OSError Error Value: [Errno 267] Unknown error.

I do not know the behavior of LocalFS product on Windows NT/2K OS . Is there any document that can help on this. Thanks

Yeeps. No idea. Hopefully, someone will be able to provide some assistance on using remote filesystems with \\foo\bar UNC notation.

If not, could you map this remote directory to a drive letter? If you can do that in the OS, it should be no problem to use that in LocalFS.

Good luck,

-- Joel Burton <jburton@scw.org> Director of Information Systems, Support Center of Washington

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )