This is crazy... a new post after over 2 years!

Well, I just thought I'd throw this out there in hopes it might help someone else. Apple support and warranty service is the absolute worst in the world!...

2 problem-resolution items here for Apple Xserve (Mac OS X Server 10.4.9):

PROBLEM-RESOLUTION 1:

When attempting to connect to an Apple Xserve (bound to a Windows Active Diretory) by hitting Command-K, entering afp://server (e.g. afp://x1.bbdohk.com), and using Active Directory credentials, the following error pops up:

Connection Failed
Unknown user, incorrect password, or login is disabled.

When logging in using a local, Open Directory account, connection is successful.

On the Xserve in the Console app, a ton of the following errors are logged:

May 11 08:42:54 x1 DirectoryService[90]: Active Directory DS Plugin: Kerberos Time Skew Too Large. Check Date/Time!\n
May 11 08:44:54 x1 DirectoryService[90]: Active Directory DS Plugin: Kerberos Time Skew Too Large. Check Date/Time!\n
May 11 08:46:54 x1 DirectoryService[90]: Active Directory DS Plugin: Kerberos Time Skew Too Large. Check Date/Time!\n

So the fix is to match the times on the Xserve and Windows AD servers.

PROBLEM-RESOLUTION 2:

In Windows, when attempting to connect to an Apple Xserve by entering \\servername (or using the IP address, such as \\10.1.1.20) in an Explorer window, the following error appears:

Windows cannot find ‘\\servername’. Check the spelling and try again, or try searching for the item by clicking the Start button and then clicking Search.

Fix is to start the “Windows” service on the Xserve using Server Admin.

The problem is on my Xserve, the Windows startup state (Running or Stopped) does not stick after a reboot. And it may even stop on its own. Not sure what the fix is for that.