There is no need to get a trace. We do not have the resources to
spend on developing the RPC interface to make browsing work from
Start Menu->Run...
Jeffrey Altman
Christopher Allen Wing wrote:
> Thanks for your work on OpenAFS.
>
> Do you have any idea why browsing \\afs works some of the ti
Under some circumstances browsing \\afs with explorer.exe is equivalent
to NET VIEW. Its not when you try to launch it with Start Menu->Run.
We do not implement the RPC services necessary for all of the queries
that Windows want to perform. This is part of the CIFS Remote
Administration Protocol.
Thanks for your work on OpenAFS.
Do you have any idea why browsing \\afs works some of the time and fails
at other times?
Would you like me to try to get a trace of a successful browse of \\afs
in the Explorer?
Thanks,
Chris
On Tue, 16 May 2006, Jeffrey Altman wrote:
P.S. - Thanks for
Thanks. It wasn't clear to me whether this was a known problem or if
something was broken in my system's configuration.
I was looking at documentation such as your status report from December:
https://www.secure-endpoints.com/talks/OpenAFS-Windows-Dec-2005-Status-Report.pdf
which see
P.S. - Thanks for the excellent report.
Jeffrey Altman wrote:
> We do not have a fully implementation of the Remote Administration
> Protocol. This issue is listed in the "issues" list distributed
> with the release.
>
> Jeffrey Altman
>
> Christopher Allen Wing wrote:
>> (I just entered a bu
We do not have a fully implementation of the Remote Administration
Protocol. This issue is listed in the "issues" list distributed
with the release.
Jeffrey Altman
Christopher Allen Wing wrote:
> (I just entered a bug report with this same text as bug #31903)
>
> I am testing the OpenAFS Windo
(I just entered a bug report with this same text as bug #31903)
I am testing the OpenAFS Windows client on a XP SP2 machine which should be
reasonably up to date with patches. I cannot reliably browse the '\\afs' root
in Windows Explorer. Sometimes this works, but other times I get the error:
