mbn wrote: > Jeffrey Altman-2 wrote: >> >> What name is being registered by afsd_service.exe in the >> %windir%\temp\afsd_init.log file? >> > > Do you mean this? > > 1/12/2009 11:23:06 AM: Mount root /afs
Mount root is the name used for the root in symlink target paths. I'm referring to the entries such as: 1/9/2009 11:41:57 PM: Netbios NCBADDNAME lana=8 code=0 retcode=0 complete=0 1/9/2009 11:41:57 PM: Netbios NCBADDNAME added new name >AFS < 1/9/2009 11:41:57 PM: Netbios NCBADDNAME succeeded on lana 8 1/9/2009 11:42:28 PM: Using >AFS< as SMB server name 1/9/2009 11:42:36 PM: smb_localNamep is >AFS< 1/9/2009 11:42:36 PM: Netbios NCBRESET lana 8 succeeded 1/9/2009 11:42:36 PM: lana_list.length 1 > > > Jeffrey Altman-2 wrote: >> >> What is the output of "nbtstat -n" >> > > C:\>nbtstat -n > > AFS: > Node IpAddress: [10.254.254.253] Scope Id: [] > > NetBIOS Local Name Table > > Name Type Status > --------------------------------------------- > LAPTOP <00> UNIQUE Conflict > WORKGROUP <00> GROUP Registered > WORKGROUP <1E> GROUP Registered > AFS <20> UNIQUE Registered The "LAPTOP" name conflict is disturbing. If the laptop cannot register its own name it won't be able to communicate with anything. > Jeffrey Altman-2 wrote: >> and "nbtstat -S"? >> > > C:\>nbtstat -S > > AFS: > Node IpAddress: [10.254.254.253] Scope Id: [] > > NetBIOS Connection Table > > Local Name State In/Out Remote Host Input > Output > > ---------------------------------------------------------------------------- > LAPTOP <00> Connected Out 10.254.254.253 > 15KB 14KB > AFS Connected In 10.254.254.253 > 15KB 14KB > AFS Listening This indicates that the "AFS" netbios name is not only properly registered as listed above but that it is actively connected to "LAPTOP". My guess is that the CreateFile() is failing because the "LAPTOP" name is in conflict. Names of machines and services must be unique. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
