I have two 10.8.3 servers.
Server 1 is the main Fileserver and also is running an OD master.
Server 2 is an FTP server (running Rumpus) but I also have Filesharing running for practical reasons. Server 2 are also running the internal DNS and is connected to the OD master through User & Groups.
Now the problem I have is that some of my Macs cannot login to either of the servers. It's not an issue with the users not beeing set up properly since I have tried the same user on all of them and it works on some but not on others. If I check the system log it only says:
|4/12/13 4:36:27.666 PM||kdc||Got a canonicalize request for a LKDC realm from 192.168.0.167:51123|
|4/12/13 4:36:27.666 PM||kdc||Asked for LKDC, but there is none|
|4/12/13 4:36:27.667 PM||kdc||Got a canonicalize request for a LKDC realm from fe80::21f:5bff:fe37:beed%bond0:51124|
|4/12/13 4:36:27.667 PM||kdc||Asked for LKDC, but there is none|
The above is one example but not all of the problem macs generates this message. At least not an entry with their IP address so I can tie the message to the mac. The weird thing is that this message (or similar) also can be found sometimes even if the login was successful. Like the next example where I logged in connected through our Cisico firewall using AnyConnect:
4/13/13 10:48:49.168 AM kdc: Got a canonicalize request for a LKDC realm from local-ipc
4/13/13 10:48:49.168 AM kdc: Asked for LKDC, but there is none
4/13/13 10:48:54.998 AM kdc: Got a canonicalize request for a LKDC realm from local-ipc
4/13/13 10:48:54.998 AM kdc: Asked for LKDC, but there is none
It seems to be tied to the particular macs or IP addesses but I have no idea where to look for a solution. Speaking of IP addresses, I checked all the macs that could not log on and compared with the address of those which could and could not find a pattern. They are all spread over the whole subnet.
Any ideas would be much appreciated!
Ok, I gave up trying to fix this isssue and started upgrading all the 10.7.5 Macs to 10.8 instead which fixes the problem. The only information I got is that for one reason or another 10.7 are having problems dealing with Kerberos. Don't ask me for the source on that since it was something a Mac tech told me he had heard from somewhere...