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.
The next time I issue a status report I will clarify "browsing with NET VIEW". Jeffrey Altman Christopher Allen Wing wrote: > 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 seemed to suggest that this would work: > > 1.6.3. Windows Explorer Shell > - AFS UNC paths now supported in the Explorer > - Browsing of the "AFS" Server is now supported (limited to 13 > character names) > > > Maybe you should update the 'afs-issues.txt' file to explicitly state > that browsing \\afs from the Explorer is known to be unreliable. (while > 'net view \\afs' should always work, right?) > > > As long as referring to complete UNC paths for drive mapping works OK > this isn't a big deal for us. I was just afraid that I had broken > something because I was able to browse \\afs with the Explorer when I > first installed OpenAFS, but then it failed later on. > > > Thanks, > > Chris Wing > [EMAIL PROTECTED] > > > > On Tue, 16 May 2006, 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 > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info
smime.p7s
Description: S/MIME Cryptographic Signature
