Kerberos doesn't alow login

Hello Admins

I have a silly question.
Even that DNS is running properly.
See below.
********
Primary address = 192.168.99.1

Current HostName = server.private
DNS HostName = server.private

The names match. There is nothing to change.
dirserv:success = "success"
*******
I'm not able to login with "diradmin" and PW as well as "Directory Administrator" and PW after I hit the button "Kerberize". Does anyone have an idea why this is a problem?

Kind regards
Thomas Thaler

Intel Mac Mini 1.83GHz, Mac OS X (10.6.2), Snow Leopard Server 10.6.2

Posted on Feb 2, 2010 1:27 PM

Reply
18 replies

Feb 3, 2010 7:30 AM in response to Thomas Thaler1

Do you mean "login" or "authenticate"?

I have never been to login as DirAdmin, however I can authenticate as DirAdmin when using WG manager locally or remotely. In the latter case, I initially authenticate as the local administrator on the server and then use the Authenticate button, top-right, in WG manager to switch identities to modify the directory.

I suspect that the DirAdmin account is not enabled for login, although I can't immediately see what prevents it.

Feb 3, 2010 11:18 AM in response to herveyw

I mean the authentication screen after you hit "Kerberize" in the OD settings panel.
I did control the proper working of the DNS with changeip and nslookup and this from within the server and a client computer. Both times everything did work as it should. But as soon as I set the login over AFP, iCal or Addressbook to be done with Kerebros, I endup with not being able to login the each of this services.

Feb 8, 2010 11:42 AM in response to hooh

Dear Stefan

Thank you for your feedback.
Well I try to explain step by step what I did until now.
1.) Install SLS 10.6.0 and do set configure as "Configure manually"
2.) Update to SLS 10.6.2
3.) Check DNS with checkip -checkhostname and with nslookup
--> Both where successful
From now on everything is done in/with Server-Admin
4.) Add AFP to the list of services and start AFP
5.) Set access identification to Kerberos
6.) Add OpenDirectory and make it a Directory-Master
7.) In Open Directory on TAB Settings under General under Replica Status I see next to "Add Kerberos Entry" "Kerberize".
8.) Hit the button "Kerberize" and try to login one after an other with "diradmin", "ladmin", "root", all without success.
9.) On my local maschine, I open Ticket Viewer and try to get a ticket for "diradmn", "ladmin" and "root". All, but without "ladmin" do get a ticket from the server.
--> That "ladmin" doesn't get a ticket is OK and normal and should be that way, as it isn't a part of the OD user database.
10.) With Workgroup Manager, add a new user "Office".
11.) Set the home folder to "afp://server.private/Users".
12.) Create Home Directory for user "Office".
13.) In System Preference, I did check if the server is listed in the in the login options.
--> It is listed
14.) From my workstation, I try to Connect to Server with user "Office".
--> Successful
15.) Open Server Preferences and check the settings for services
--> On the start screen, NO service is shown as running!!!
16.) Check again with Server Admin and I see, that AFP, DNS and OD is running
17.) Back in Server Preferences I go to the list of users and select user "Office"
18.) Under the Services Tab, ALL (even NOT running Services) are marked as activated for this user but are grayed out!!
19.) I did try Article http://support.apple.com/kb/HT1194 an got the following output.
server:~ ladmin$ sudo mkpassdb -dump
signature: pwfi
version: 1
entrySize: 4360
sequenceNumber: 4
numberOfSlotsCurrentlyInFile: 512
deepestSlotUsed: 4
deepestSlotUsedByThisServer: 4
Shutdown State: 0

Access Features:
usingHistory=0 canModifyPasswordforSelf=1 usingExpirationDate=0 usingHardExpirationDate=0 requiresAlpha=0 requiresNumeric=0 expirationDateGMT=18446744073709551615 hardExpireDateGMT=18446744073709551615 maxMinutesUntilChangePassword=0 maxMinutesUntilDisabled=0 maxMinutesOfNonUse=0 maxFailedLoginAttempts=0 minChars=0 maxChars=0 passwordCannotBeName=0 requiresMixedCase=0 requiresSymbol=0 newPasswordRequired=0 minutesUntilFailedLoginReset=0 notGuessablePattern=0
last modified: 02/08/2010 18:52:40

Weak Authentication Methods:
SMB-NT
SMB-LAN-MANAGER
CRYPT
APOP

Public Key: 1024 35 1615383727705902906299720390420461221110053827847319995884930279961506663994841 80399378300406985450072374045536706802861470618338113755974878877939533648233375 30667924408551722228959303664286855578001621154379412278113580367017232043193465 6123979573910677308764724482356408003556907310943439381252247799919501 root@server.private


Replica Name: (Parent)

slot 0001: 0x00000000000000000000000000000001 diradmin 02/08/2010 07:00:50 PM
slot 0002: 0x4b704f686b8b45670000000200000002 root 02/08/2010 06:53:02 PM
slot 0003: 0x4b704f686b8b45670000000300000003 server.private$ 02/08/2010 06:55:13 PM
slot 0004: 0x4b704f985b761c270000000400000004 vpn_d5bae8a17d91 02/08/2010 06:53:28 PM

What it is looking strange is, that the entry of slot 0001 does show only zeros until the last digit which is a one. All other slots do have more equivalent numbers and letters.

I really don't know what's going on here, but more and more I believe, that SLS is NOT FINISHED YET! It behaves like a Beta or even Alpha Software and not a Release Software.

Does someone from Apple read in this group?
Please do a statement to this writing.

If anyone has some suggestions, I'm happy to try them out.

Kind regards
Thomas Thaler

Feb 8, 2010 2:13 PM in response to Thomas Thaler1

Hi Thomas,

In general, i wouldn't use both Server Admin and Server Preferences. You could indeed get wrong info from Server Preferences when you've configured stuff in Server Admin.
In 10.5 this wasn't even possible, and why not do it all with Server Admin ?
OK, it takes quite some time to read the documentation, and there are bugs, but you will get your server to be nice to you 🙂
It is common practice to first configure dns, open directory, and dhcp if you want to use dhcp.
Only after that you can start turning on all other services, they depend heavily on a well configured dns and od.

Steps 1 thru 3 are ok, after that i would:

4. On the server, go to System Prefences/Network and set DNS Server to its own ip address and Search Domains to your domain
5. Add Open Directory and make it an OD Master. Kerberos is now started as well, there is no need to hit the 'Kerberize' button
6. Check under the tab 'Overview' if LDAP Server, Password Server, and Kerberos Server are all running
7. Start Workgroup Manager (autheticate as diradmin) and switch from the local directory to the LDAP directory (the little globe just under the 'Server Admin' button)
8. Add a new user with default settings (so just fill in user name, short name, password and hit save, please leave the user ID as it is generated)
9. Start AFP, again use default settings, just start it
10. Select your server in Server Admin, go to Access, and check that your user is allowed to use AFP. You may also allow all users and groups for now
11. On the client machine, check in System Preferences/Accounts/Login Options that the client is connected to the LDAP database on your server
12. On the client machine, connect to server with afp://yourserver.example.com
13. If this works, go back to Server Admin/AFP, stop AFP and change the Authentication setting to Kerberos
14. Start AFP
15. On the client machine, try to connect to server with afp://yourserver.example.com
16. If this doesn't work, launch Ticket Viewer (you can find it at /System/Library/CoreServices/)
17. In Ticket Viewer, hit Add Identity and fill in username@YOURSERVER.EXAMPLE.COM and the password. If this doesn't work, please let me know what the popup says

Kind Regards, Stefan

Feb 8, 2010 4:07 PM in response to Thomas Thaler1

I don't have much to add to Stefan's recommendations on setup, but I'd like to go through the problems you're seeing and try to explain what's probably going on. In general, it sounds to me like things are set up and running ok, it's just that the UI is misleading you into thinking there's something wrong.

Step 8 (trying to use the Kerberize button): The OD domain should already be kerberized during normal setup, this button is only needed in certain cases where automatic kerberization didn't take place. Check in Server Admin -> Open Directory -> Logs -> Configuration Log, and you'll probably see something like:
slapconfig -kerberize
command: /user/sbin/sso_util info -r /DALPv3/127.0.0.1 -p
Warning: Kerberos is already configured on this server, use -f to override current settings.
... so the process is failing because it's unnecessary, not because of an authentication error (as the UI's behavior implies).

Step 15 (Server Preferences shows no services running): Server Preferences shows a very simplified view of the server's options and status; if things are set up in ways it doesn't quite understand, it may not display the setup very well. In this case, what seems to be going on is that SP's "File Services" corresponds to both AFP and SMB service; if you have only one running, it doesn't consider that "File Services" are running. The other services you're using are ones it simply doesn't display. In short, I'll second Stefan's recommendation to avoid Server Preferences.

Step 18 (Server Preferences shows services grayed out for user): Again, Server Prefs is trying to display a server configuration that doesn't quite match its assumptions. What Server Prefs is trying to show here is your service access control lists -- things you control in Server Admin -> servername in the sidebar -> Access -> Services. I'm assuming you don't have them set up, meaning that all users get access to all services (that're running). If you do set up SACLs, Server Prefs will let you add/remove users from the list with the checkboxes.

Step 19: (diradmin has a weird password server slot number): This is normal; I think it has to do with making sure the slot matches up when you restore an old OD archive.

So it looks to me like everything's more or less working. Are you running into any trouble other than the UI not showing what you expect?

Mar 15, 2010 8:15 AM in response to Gordon Davisson

Dear readers and helpful person

Sorry I answer this question this late. I had some familiar troubles in the last few weeks.
But now back to the server.
In the mean time I did install the server new again.

In the network settings of the server, the following is set.
IP 192.168.99.1
Subnet 255.255.255.0
Router 192.168.99.254
DNS 192.168.99.1
Search Domains private.lan

Under accounts --> Login Options --> Network Account Server the entry is set to Local Server.
If I open Directory Utility and choose LDAPv3, the server is set as Open Directory Server with SSL.

The DNS is set as follows.
99.168.192.in-addr.arpa
--> 192.168.99.1 server.private.lan
--> 192.168.99.2 office.private.lan
private.lan
--> office 192.168.99.2
--> server 192.168.99.1

The following tests show that DNS is up and running properly, except the "dig @192.168.99.1" command.

server:~ ladmin$ nslookup 192.168.99.1
Server: 192.168.99.1
Address: 192.168.99.1#53

1.99.168.192.in-addr.arpa name = server.private.lan.

server:~ ladmin$ nslookup server
Server: 192.168.99.1
Address: 192.168.99.1#53

Name: server.private.lan
Address: 192.168.99.1

server:~ ladmin$ nslookup 192.168.99.2
Server: 192.168.99.1
Address: 192.168.99.1#53

2.99.168.192.in-addr.arpa name = office.private.lan.

server:~ ladmin$ nslookup office.private.lan
Server: 192.168.99.1
Address: 192.168.99.1#53

Name: office.private.lan
Address: 192.168.99.2

server:~ ladmin$ nslookup office
Server: 192.168.99.1
Address: 192.168.99.1#53

Name: office.private.lan
Address: 192.168.99.2

server:~ ladmin$ dig @192.168.99.2
^Cserver:~ ladmin$ dig @192.168.99.1

; <<>> DiG 9.6.0-APPLE-P2 <<>> @192.168.99.1
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43950
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 14

;; QUESTION SECTION:
;. IN NS

;; ANSWER SECTION:
. 156422 IN NS a.root-servers.net.
. 156422 IN NS f.root-servers.net.
. 156422 IN NS k.root-servers.net.
. 156422 IN NS g.root-servers.net.
. 156422 IN NS h.root-servers.net.
. 156422 IN NS j.root-servers.net.
. 156422 IN NS d.root-servers.net.
. 156422 IN NS i.root-servers.net.
. 156422 IN NS e.root-servers.net.
. 156422 IN NS c.root-servers.net.
. 156422 IN NS b.root-servers.net.
. 156422 IN NS m.root-servers.net.
. 156422 IN NS l.root-servers.net.

;; ADDITIONAL SECTION:
a.root-servers.net. 105952 IN A 198.41.0.4
a.root-servers.net. 604475 IN AAAA 2001:503:ba3e::2:30
b.root-servers.net. 105978 IN A 192.228.79.201
c.root-servers.net. 105975 IN A 192.33.4.12
d.root-servers.net. 170645 IN A 128.8.10.90
e.root-servers.net. 171134 IN A 192.203.230.10
f.root-servers.net. 105974 IN A 192.5.5.241
f.root-servers.net. 604475 IN AAAA 2001:500:2f::f
g.root-servers.net. 170772 IN A 192.112.36.4
h.root-servers.net. 105976 IN A 128.63.2.53
i.root-servers.net. 170779 IN A 192.36.148.17
j.root-servers.net. 105971 IN A 192.58.128.30
j.root-servers.net. 105971 IN AAAA 2001:503:c27::2:30
k.root-servers.net. 105971 IN A 193.0.14.129

;; Query time: 0 msec
;; SERVER: 192.168.99.1#53(192.168.99.1)
;; WHEN: Mon Mar 15 16:09:27 2010
;; MSG SIZE rcvd: 488

When I try to add a identity with Ticket Viewer on the server with the entries diradmin@server.private.lan and its PW, I get all the time the error ""Kerberos Error - Cannot resolve network address for KDC in realm server.private.lan".

What can I do to get kerberos running?

Thank you in advance for your help and tips
Kind regards
Thomas Thaler

Mar 15, 2010 9:11 AM in response to Thomas Thaler1

Thomas,
what do you expect the command 'dig @192168.99.1' to achieve? Basically you're telling dig to use the DNS at (@) 192.168.99.1, the result is some information about the server; that's what's supposed to happen.

You should make sure that the answer to 'dig server.private.lan' is 192.168.99.1. If not, then your machines are looking in the wrong places. If your machines cannot resolve server.private.lan (assuming this is the machine where your KDC resides), then Kerberos won't work.

Take a closer look at the zones in Server Admin -> DNS to make sure you got the naming right. The other thing to check, as already mentioned by others, is Serveradmin -> Open Directory -> Overview. If you don't see 'running' three times, then something doesn't work out regarding your setup.

I guess you've been told this a thousand times, but I'll mention it nevertheless for good measure, do you still get a 'nothing to be done'-answer when you fire up 'changeip -checkhostname'? If not, use the command provided in the output of the above mentioned command for a quick fix.

Mar 15, 2010 10:43 AM in response to Erik Keller

Dear Erik

Thank you for your replay.
Sorry, I did use the wrong expression.
dig server.private.lan will output the following.
server:~ ladmin$ dig server.private.lan

; <<>> DiG 9.6.0-APPLE-P2 <<>> server.private.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44534
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;server.private.lan. IN A

;; ANSWER SECTION:
server.private.lan. 10800 IN A 192.168.99.1

;; AUTHORITY SECTION:
private.lan. 10800 IN NS server.private.lan.

;; Query time: 0 msec
;; SERVER: 192.168.99.1#53(192.168.99.1)
;; WHEN: Mon Mar 15 17:34:32 2010
;; MSG SIZE rcvd: 66

The changeip -checkhostname result is:
server:~ ladmin$ sudo changeip -checkhostname

Primary address = 192.168.99.1

Current HostName = server.private.lan
DNS HostName = server.private.lan

The names match. There is nothing to change.
dirserv:success = "success"

So, this result tells me that DNS is running properly and without problems.
NO other service is running yet.
Next I start OD as Master.
Setings:
Kerberos-Realm: SERVER.PRIVATE.LAN
LADP-Serach String: dc=server,dc=private,dc=lan

After its processing, a check of the running servers shows, that all three services are up and running.

Replica Tree is set to 192.168.99.1 --> server.private.lan
All other settings are set as default.

I then did enter a new user in the OD domain.
But if I try to get a ticket (from the server and from a client), I get the error as written before.
"Kerberos Error - Cannot resolve network address for KDC in realm server.private.lan"

So next I did a repair of the permissions.
Disk Utility had to repair Users, it found a ACL where it wasn't expected.
Also "private/var/db/openladp/openldap-data" had to be fixed. The access right where drwxr-xr-x instead of drw-------.

Well then. I now did update the server to 10.6.2 and all necessary updates too.
After all still no luck.

Any idea how to go on with that?

Kind regards
Thomas Thaler

Mar 15, 2010 5:05 PM in response to Gordon Davisson

Dear Gordon Davisson

Thank you very much for your replay.
This was the point.
Your answer saved my a lot.

Now I have only some problems left with Addressbook Server and iCal Server and Kerbeors.
Both don't like my username, if I set Kerberos as type of identity.
If I set it to any method, I can access both services.

I'm not sure if the place for this problems is here or if I should ask in the Collaboration Services Group.

Thank you anyway for your feedback.
Kind regards from Switzerland
Thomas Thaler

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Kerberos doesn't alow login

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.