It was the latter (which should be %systemroot% and not %windir%\afslogon.dll for both).
Sounds like double clicking on the .msi on the desktop counts as a 32-bit command shell environment. On Fri, Dec 07, 2007 at 01:44:15PM -0500, Jeffrey Altman wrote: > The Network Provider is not being called. > > Check to make sure that "TransarcAFSDaemon" is listed in > HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder > "ProviderOrder" and that > HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider > "AuthentProviderPath" and "ProviderPath" refer to %windir%\afslogon.dll > and not %windir%\SysWOW64\afslogon.dll. > > The latter can happen if you run the installation from a 32-bit command > shell environment. > > > > > > Dave Botsch wrote: > > Hi. > > > > As the subject says, integrated login on Win XP 64-bit isn't happening. > > Since > > we're doing roaming profiles in afs, integrated login is kind of necessary. > > > > What's interesting, is that when logging in on 64-bit XP, there is no box > > that > > pops up saying that integrated login failed. And, of course, one does not > > have > > tokens. > > > > Using oafs 1.5.27 64-bit, the 32-bit oafs 1.5.27 tools, and kfw-3.2.2 64-bit > > beta 1. > > > > Event log with Trace Option set to 1 attached. > > > > -- ******************************** David William Botsch Programmer/Analyst CNF Computing [EMAIL PROTECTED] ******************************** _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
