Apple Mac OS X Server Print Service Administration For Version 10.4 or Later Instrukcja Użytkownika Strona 201

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 232
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 200
Chapter 11 Solving Problems 201
A Mac OS X User in Shared NetInfo Domain Cant Log In
This problem occurs when a user tries to log in to a Mac OS X computer using an
account in a shared NetInfo domain, but the server hosting the domain isn’t accessible.
The user can log in to the Mac OS X computer by using the local user account created
automatically when he or she set up the computer to use a NetInfo account. The user
name defaults to administrator” (short name defaults to “admin”) though both can be
modified when the user ID and password is created at the time of account creation.
Users Can’t Authenticate Using Single Sign-On or Kerberos
When a user or service that uses Kerberos experiences authentication failures, try these
remedies:
Kerberos authentication is based on encrypted time stamps. If there’s more than a 5
minute difference between the KDC, client, and service computers, authentication
may fail. Make sure that the clocks for all computers are synchronized using the
Network Time Protocol (NTP) service of Mac OS X Server or another network time
server. For information about the NTP service of Mac OS X Server, see the network
services administration guide.
Make sure that Kerberos authentication is enabled for the service in question.
If a Kerberos server used for password validation is not available, reset the users
password to use a server that is available.
Make sure that the server providing the Kerberized service has access to directory
domains containing accounts for users who are authenticated using Kerberos. AFP,
mail, and other Kerberized services of ProductName always have access to user
accounts in the servers local directory domain and its LDAP directory domain, if it
has one. For information about configuring access to directory domains on other
servers, see the Open Directory administration guide.
Refer to the KDC log (kdc.log) for information that can help you solve problems.
Incorrect setup information such as wrong configuration file names can be detected
using the logs.
If users can’t authenticate using single sign-on or Kerberos for services provided by a
server that is joined to an Open Directory masters Kerberos domain, the servers
computer record might be incorrectly configured in the Open Directory masters
LDAP directory. In particular, the servers name in the computer list must be the
server’s fully qualified DNS name, not just the servers host name. For example, the
name could be server2.example.com but not just server2.
To reconfigure a server’s computer record for single sign-on and Kerberos
authentication:
1 Delete the server from the computer list in the LDAP directory.
2 Add the server to the computer list again.
3 Delegate authority again for joining the server to the Open Directory masters Kerberos
domain.
Przeglądanie stron 200
1 2 ... 196 197 198 199 200 201 202 203 204 205 206 ... 231 232

Komentarze do niniejszej Instrukcji

Brak uwag