Did you find this out via experimentation? Or did Microsoft tell you something? If not Microsoft, did you have it reported by the UMich PSS contact?
Jeffrey Altman Sean Caron wrote: > SO, after spending almost two weeks on-and-off trying to figure what on > earth was going on... > > it turns out that the System Error 67: network name not found errors > were caused by some issue with the client for microsoft networks that > doesn't really manifest itself in any other way but to screw up the AFS > client. > > it is remedied by uninstalling and reinstalling the client for microsoft > networks > > it is bound to both the loopback adaptor and the built-in ethernet > adaptor over tcp/ip. > > and now everything seems to be working fine. > > so if anyone else ever gets this error: you install AFS by the book, and > everything works exept drive mappings > > this could be very well how you might fix it. > > thanks to all those who tried to help.. even though i realize that some > on this list probably found my query irritating. > > and by-the-by, i guess this proves conclusively that the openafs client > does indeed work with the loopback adaptor given even the most > convoluted novell configurations. > > regards, > > sean caron > associate systems administrator > university of michigan school of public health > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > 1-734-763-4206
smime.p7s
Description: S/MIME Cryptographic Signature
