On Fri, 1 Feb 2002, Shyh-Wei Luan wrote: > > Did you ever *uninstall* OpenAFS 1.0.4a client from your machine? There > was a known problem the unistallation procedure of 1.0.4a causing problem > to Netbios.
I never had OpenAFS 1.0.4a installed. > If not, what is the version of the OpenAFS client are you using? Did you > try to manually set the LANA number in the Advanced configuration of the > AFS client? It could be a problem if you did so. Actually, the problem turned out to be a conflict with the AT&T VPN client I use to access my employer's internal network from home. After uninstalling the client, the network bindings returned to a normal appearance (no more disabled icons). I was then able to successfully install the Transarc NT client (haven't tried yet with OpenAFS). This was a big step in the right direction. After AFS was up and running, I reinstalled the VPN client and lo-and-behold it all works! I'll never understand the Windows network stack as long as I live... Pure voodoo. I can mount my private cell and authenticate without incident - one happy camper. Steve > To: > cc: "Cameron, Frank" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> > Subject: RE: [OpenAFS] RE: Problems under WinNT 4.0sp6 > > > > On Mon, 28 Jan 2002, Steven N. Hirsch wrote: > > Following up on myself. I'm quite Windows-ignorant, but finally found the > logs. This is what it's reporting at startup: > > > The description for Event ID ( 6063 ) in Source ( AFS Client ) could not > be found. It contains the following insertion string(s): Error at file > smb.c, line 6063: Netbios NCBENUM error code 63. > > Hopefully this means something to the maintainers? _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
