Lars:
Thanks for testing the various builds.
This problem is fixed in 1.5.13 which should be available soon. If
there is a 1.4.3 build, then it will be fixed there as well.
Jeffrey Altman
Secure Endpoints Inc.
smime.p7s
Description: S/MIME Cryptographic Signature
Hi,
I tested the other versions and with 1.4.2beta2 the problem occurs. I
checked the source files and there are changes in "afslogon.c". I don't
have an environment for compiling the sources. So I can't test any fixes.
I hope, it helps, that you can find a solution.
Regards Lars
Jeffrey Al
That would be quite helpful.
Jeffrey Altman
Lars Richter wrote:
>
> Tomorrow I will test the other versions in the office and try to locate
> the version, where the problem occurs.
>
> Lars
>
> Jeffrey Altman wrote:
>> All beta and release candidate installers are available from
>>
>> /afs
Tomorrow I will test the other versions in the office and try to locate
the version, where the problem occurs.
Lars
Jeffrey Altman wrote:
All beta and release candidate installers are available from
/afs/grand.central.org/software/openafs/candidate/
Jeffrey Altman
Lars Richter wrote:
All beta and release candidate installers are available from
/afs/grand.central.org/software/openafs/candidate/
Jeffrey Altman
Lars Richter wrote:
> Hi,
>
> this was the last version I used for tests because of problems with
> delayed write operations. I decided to wait for further tests, un
Hi,
this was the last version I used for tests because of problems with
delayed write operations. I decided to wait for further tests, until
1.4.2 was released. I don't have the other beta releases. If I could get
them, I can test it tomorrow, where the problem occurs.
Is it possible to down
Lars:
Are you saying that the breakage occurred in 1.4.2-beta2 ?
Jeffrey Altman
Lars Richter wrote:
> Hi,
>
> I have the same problem after update from version 1.4.1 to 1.4.2.
>
> Version 1.4.1:
> Packets were send through the network to check the connectivity to
> kasserver. Integrated login
Hi,
I have the same problem after update from version 1.4.1 to 1.4.2.
Version 1.4.1:
Packets were send through the network to check the connectivity to
kasserver. Integrated login works!
Version 1.4.2:
There are not any network packets send to check the connectivity to
kasserver. Integrated
Ok, thankyou.
Upon doing as you suggested of using afslogon.dll and attempting to login,
Integrated Logon did not work, however, it did not give any errors at all,
just didn't work. I was able to login with the normal afs task bar login.
I've attached another event log from an AFS logon.
On 12/
The file is not part of the AFS Service. Its part of the Windows LSA.
Rename the file, copy the new version in, reboot the machine
Andrew Radamis wrote:
> Sorry, I had finals...
>
> This is going to sound lame, but how do I do this? Windows is not
> letting me even after I stop the restart and
Sorry, I had finals...
This is going to sound lame, but how do I do this? Windows is not letting me
even after I stop the restart and stop the service (from another machine
with out logining in to the destination machine).
On 12/13/06, Jeffrey Altman <[EMAIL PROTECTED]> wrote:
If you manually
These are are my notes for running the conversion with MIT krb5 which i
was originally planning on adding to the wiki, but they aren't complete. I
was missing something trivial at the end. probably the keytab entry for
the host or something simple. My boss did the last little piece and the
actual
If you manually replace the %WinDir%\System32\afslogon.dll
with the 1.4.1 version, are you able to successfully authenticate?
smime.p7s
Description: S/MIME Cryptographic Signature
The behavior is that of a lack of network connectivity.
I don't know what the cause of the problem is but I am
attempting to help you narrow it down. Is there traffic
being exchanged with the kaserver?
If so, are there responses being sent back?
If there is no traffic being sent, then the quest
But it works with out issue with 1.4.1, with no other changes to the system.
I tried 1.4.2 and had the same issue. As soon as I downgrade back to
1.4.1it works again. I can login to the machine as soon as the login
box
appears. System authentication is on an NT domain, using Samba. The Samba
PD
You privately sent the event log entries.
I see nothing in there that is wrong.
Although I must wonder whether or not the machine
actually has network access at the time it is
failing.
The error indicates that none of the KdC addresses
that are being contacted are responding. You might
want to mo
Filter on "AFS Logon" and save the result to a file. These are not
the critical entries.
Andrew Radamis wrote:
> I don't know if I got the right ones, but there was a lot of entries,
> and there a pain to copy. If there a log file somewhere I missed that'd
> be helpful. I can fish out more of t
If I understand correctly, you meant adding the reg key to make it log to
the system log, which gave me a lot of results, the ones I'm guessing are
relevant below.
Event Type: Information
Event Source: AFS Logon
Event Category: None
Event ID: 0
Date: 12/12/2006
Time: 11:43:57 PM
User: N/A
When you following the directions for debugging integrated logon as
specified in the Release Notes. What is the full set of log messages
that are written to the event log?
Andrew Radamis wrote:
> I am able to obtain credentials with the login box that opens after I
> login to the machine, but I
I am able to obtain credentials with the login box that opens after I login
to the machine, but I have not tried with klog.
On 12/12/06, Jeffrey Altman <[EMAIL PROTECTED]> wrote:
Migrating to Kerberos 5 would be a good thing. There is a collection
of information in the Wiki at
http://www.
Migrating to Kerberos 5 would be a good thing. There is a collection
of information in the Wiki at
http://www.dementia.org/twiki/bin/view/AFSLore/KerberosV
There are also several talks on the subject from the various AFS &
Kerberos Best Practice Workshops accessible off the www.openafs.org
we
21 matches
Mail list logo
