[OpenAFS] Win2k problem

[Matthew Mauzy]

Another thing to check: is your windows client also a client to a separate 
windows AD domain?  If it is, make sure that you are authenticated to the 
Win AD before trying to do the AFS client stuff.  I've had problems with 
AFS "service not starting" etc., when I was using a laptop that was set as 
an AD client at home where it wasn't talking to the PDC.

--Matthew

--On Tuesday, August 05, 2003 10:09 AM -0400 Todd DeSantis <atd@us.ibm.com> 
wrote:

>
>
>
>
> Hi -
>
> On the AFS client on the PCs, it may try using port 750 or port 88 for the
> AFS authentication.  Again, it depends on the /etc/system equivalent files
> on the PC.
>
> And your kaserver machines must be also listening to ports 750 and 88,
> again depending on the ports that your PCs want to use.
>
> Check the AuthLog on your kaserver machines to see which additional
> ports it is listening on.
>
> And you might also want to make sure the /etc/services file on the
> kaserver machines have definitions like
>
> kerberos5         88/udp
> kerberos5         88/tcp
> kerberos4         750/udp
> kerberos4         750/tcp
>
> If you have to change the /etc/services file, then you must restart the
> kaserver
> process on the machine.
>
> The problem may well be any firewalls you have running, but making sure
> the PCs and kaserver are using the same ports for kerberos authentication
> is required.
>
> Thanks
>
> Todd
>
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info



__________________________________________________________________
                        Matthew W. Mauzy
                      Systems Administrator
                      Applied Math @ UNC-CH
email : mauzy@amath.unc.edu           pager : mpager@amath.unc.edu
 (W) 919.962.9819   www.amath.unc.edu/~mauzy/   (P) 919.347.0390
__________________________________________________________________