[OpenAFS] OpenAFS 1.5.56 and Vista Home Premium 64bit SP1
mbn
anonymoususr@gmail.com
Mon, 12 Jan 2009 12:22:54 -0800 (PST)
Thanks Jeff, I changed the hostname from "laptop" to something else and now
AFS is working properly.
On the other hand, I have noticed another issue. In the "AFS Client" applet,
when I click in "Configure AFS Client", nothing happens. The configuration
dialog is not shown. Why could this be happening?
Mark
Jeffrey Altman-2 wrote:
>
>> 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
>
>
>
--
View this message in context: http://www.nabble.com/OpenAFS-1.5.56-and-Vista-Home-Premium-64bit-SP1-tp21396550p21422871.html
Sent from the OpenAFS - General mailing list archive at Nabble.com.