[OpenAFS] OpenAFS Windows client will not map drives

Sean Caron caron.sean@gmail.com
Wed, 8 Mar 2006 16:22:39 -0500


------=_Part_16903_24081938.1141852959466
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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 doe=
s
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
scaron@umich.edu
1-734-763-4206

------=_Part_16903_24081938.1141852959466
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

SO, after spending almost two weeks on-and-off trying to figure what on ear=
th was going on...<br>
<br>
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.<br>
<br>
it is remedied by uninstalling and reinstalling the client for microsoft ne=
tworks<br>
<br>
it is bound to both the loopback adaptor and the built-in ethernet adaptor =
over tcp/ip.<br>
<br>
and now everything seems to be working fine.<br>
<br>
so if anyone else ever gets this error: you install AFS by the book, and ev=
erything works exept drive mappings<br>
<br>
this could be very well how you might fix it.<br>
<br>
thanks to all those who tried to help.. even though i realize that some on =
this list probably found my query irritating.<br>
<br>
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.<br>
<br>
regards,<br>
<br>
sean caron<br>
associate systems administrator<br>
university of michigan school of public health<br>
<a href=3D"mailto:scaron@umich.edu">scaron@umich.edu</a><br>
1-734-763-4206<br>

------=_Part_16903_24081938.1141852959466--