Re: Welcome to the "OpenAFS-Win32-devel" mailing list

Good morning,

My apologies if this is the wrong place to direct this question; if so 
please feel free to let me know where I should go.

That said, I have looked over the list archives, and found only one 
reference to a problem similar to mine; this message was from over a 
year ago and has not received any replies. So, I thought I'd give it 
another try.

We are getting ready to roll out AFS and Kerberos for our users. The 
versions we have been experimenting with are OpenAFS for Windows v1.3.66 
and Kerberos for Windows v2.6.4, running under Windows XP SP1. Things 
seem to be working fine with the exception of integrated login. Upon 
logging in to Windows with a username and password identical to those 
used for Kerberos, we get the following error: "Integrated login failed: 
Cannot resolve network address for KDC in requested realm." Logging in 
to Windows finishes successfully, then the Leash window pops up. 
Entering username and password here results in succefully getting AFS 
tokens. Any ideas? Perhaps it is a simple configuration error, although 
I have been unable to find anything in the AFS setup to do with our KDC 
address.

Thanks for your help,
Ben Fineman
System Administrator
Internet2
*
Tim Boyden * [email protected]  
<mailto:trboyden%40PLANT.MIT.EDU>wrote:

> Hello,
>
> I've recently been trying out OpenAFS for connecting to my MIT AFS 
> shares.
> Everything seems to work except for the integrated login. After 
> logging in I
> get a message box saying "Integrated login failed" followed by a line of
> garbage text and an OK button that I always click. To have an easier 
> way of
> logging on seeing how this wasn't working I installed Wake and enabled 
> the
> separate login box to pop up so I can enter my username an password 
> and get
> tickets and tokens. Part of the Wake interface lets you see the 
> credentials
> in the Microsoft cache, it always indicates there is none. My Windows 
> login
> is identical to my Kerberos one so I'm sure there is no issue their. I do
> know this setup used to work in Windows 2000 Pro when I used that awhile
> back but since switching to a new Windows XP box it doesn't work.
>
> Any ideas or things to try or check?
>
> Thanks,
>
> Tim Boyden
> MIT Department of Facilities
> Applications & Desktop Services Team
>