No Memory Status on XServes Running Leopard Client

I am currently netbooting 10.5.6 client on a slew of XServes and using Server Monitor on an old G5 to ensure that all the hardware is OK. In Server Monitor, I am able to view the status of all the usual items (fan speed, temperature, etc) except for the memory status. I am able to view the memory status on the two XServes running 10.5.6 Server, so I'm inclined to believe that this is a difference between the client and server OS.
How can I enable memory monitoring on the XServes running 10.5.6 Client?

Yeah, I was afraid that would be the case. It's actually not just the memory, but network and some other stuff as well (I'm not as interested in those things, so I forgot to mention them!). From what I can tell, without running server, you are only able to get the status of items via ipmi.
Does anybody know, exactly, what monitors the memory in server or if there is any other way to tell when the memory starts throwing errors? I don't need the fancy-schmancy gui, just some way to tell that there is a problem while the machine is up.

Similar Messages

Leopard Clients take a Long Time to Login (roughly 1~2 minutes)

Hello all,
I've spent the last few weeks scouring these groups and then net and searching and searching for someone with a similar problem to my own, but have come up pretty much empty handed and so now turn to here to see if any else has had this issue or can at least point me where to look to resolve the problem.
I've got a clean install of a XServe running Leopard server 10.5.2 with OD, AFP services and User home folders configured and fully working.
The problem:
Clean install of Tiger client logs into the server (OD binded) perfectly. Takes maybe 15 seconds tops to for the client to log in and show the all the AFP mounts and client settings and user's desktop and files, etc.
However, a fresh Leopard client install (OD binded) takes roughly 1~2 minutes to do the exact same thing.
I've gone through any log file I can find on server and client side, checked my DNS running on this xserve, created new users without "home" folders, and searched just about everywhere for an answer to this issue and am still empty handed.
This is not a show stopper issue, but there is something definitely not normal about what is happening with Leopard client logins.
I'm trying to explain this as best as I can without making a wall of text, but I'm sure I'll forget something, so please ask questions if you have them.
Things I'm seeing in the logs during the time of the login happening are:
Server-side Logs:
- Kerberos Server Log -
Apr 14 11:27:39 ns1.mydomain.com krb5kdc[167](info): TGS_REQ (7 etypes {18 17 16 23 1 3 2}) 172.16.9.14: ISSUE: authtime 1208190459, etypes {rep=16 tkt=16 ses=16}, [email protected] for ldap/ns1.mydomain.com@NS1. MYDOMAIN.COM
Apr 14 11:28:46 ns1.mydomain.com krb5kdc[167](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 172.16.1.205: NEEDED_PREAUTH: CRC0002$@NS1. MYDOMAIN.COM for krbtgt/NS1. MYDOMAIN.COM@NS1. MYDOMAIN.COM, Additional pre-authentication required
- Password Service Server Log -
Apr 14 2008 11:43:03 KERBEROS-LOGIN-CHECK: user {0x47f3ab5903c4b01c0000002a0000002a, CRC0005$} is in good standing.
Apr 14 2008 11:43:03 KERBEROS-LOGIN-CHECK: user {0x47f3ab5903c4b01c0000002a0000002a, CRC0005$} authentication succeeded.
Apr 14 2008 11:43:04 RSAVALIDATE: success.
Apr 14 2008 11:43:04 AUTH2: {0x47c721234c9608250000000700000007, myusername} DIGEST-MD5 authentication succeeded.
Apr 14 2008 11:43:04 RSAVALIDATE: success.
Apr 14 2008 11:43:04 AUTH2: {0x47c721234c9608250000000700000007, myusername} DHX authentication succeeded.
Apr 14 2008 11:43:04 KERBEROS-LOGIN-CHECK: user {0x47c721234c9608250000000700000007, myusername} is in good standing.
Apr 14 2008 11:43:04 KERBEROS-LOGIN-CHECK: user {0x47c721234c9608250000000700000007, myusername} authentication succeeded.
Apr 14 2008 11:43:05 RSAVALIDATE: success.
Apr 14 2008 11:43:05 AUTH2: {0x47c721234c9608250000000700000007, myusername} DHX authentication succeeded.
Apr 14 2008 11:43:06 KERBEROS-LOGIN-CHECK: user {0x47f3ab5903c4b01c0000002a0000002a, CRC0005$} is in good standing.
Apr 14 2008 11:43:06 KERBEROS-LOGIN-CHECK: user {0x47f3ab5903c4b01c0000002a0000002a, CRC0005$} authentication succeeded.
Apr 14 2008 11:43:06 KERBEROS-LOGIN-CHECK: user {0x47c721234c9608250000000700000007, myusername} is in good standing.
Apr 14 2008 11:43:06 KERBEROS-LOGIN-CHECK: user {0x47c721234c9608250000000700000007, myusername} authentication succeeded.
Apr 14 2008 11:45:26 KERBEROS-LOGIN-CHECK: user {0x47f3ab5903c4b01c0000002a0000002a, CRC0005$} is in good standing.
Apr 14 2008 11:45:26 KERBEROS-LOGIN-CHECK: user {0x47f3ab5903c4b01c0000002a0000002a, CRC0005$} authentication succeeded.
Client Side Logs:
- All Messages -
4/14/08 10:09:12 AM loginwindow[9868] Login Window Started Security Agent
4/14/08 10:15:01 AM loginwindow[9868] Login Window - Returned from Security Agent
- Console Messages -
4/14/08 10:15:03 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[9880]) Exited: Terminated
- SingleSignOnTools.log -
kdcmond cannot retreive the computer's local Hostname , retrying ..
Kerberos configuration is up to date
Kerberos configuration is up to date
Kerberos configuration is up to date
Kerberos configuration is up to date
.. and so on
All other logs don't appear to show anything of importance in between the time frame of Login window started and login window exited.
I'd like to know what exactly the client workstation is doing during this time with the server, but it looks like it just hangs and does nothing since nothing shows up in the logs that I can find during this time period where the client hangs. Maybe I can try an Ethereal trace to see what traffic is being sent back and forth during this timeframe. I don't know if this is a configuration issue on my part or a OD / AFP bug on Apple's part since Tiger clients connect perfectly.
Logouts happen immediately, so no problems there on that end. And everything else with the system is working flawlessly (besides the OD Crashing issue which I'm sure everyone is well aware of right now with 10.5.2).
Thank you to anyone that can assist in shedding some light on this issue and I apologize if I didn't provide enough information.
-Jessee

FOUND IT!!! Well for our install anyway. The culprit was AUTH2.
In our case computers would (randomly) have the same ..SLOW.. symptoms as your original post described, and the 'Apple Password Server log' on our server showed the same log entries.
It turned out that Single-Sign-On was being screwed up by two Authentication Authorities as applied in the LDAP (Computer and User) Attributes,
and showed up in the log as competing authentications from KERBEROS-LOGIN-CHECK and AUTH2. as follows:
Apr 30 2008 16:22:17 RSAVALIDATE: success.
Apr 30 2008 16:22:17 AUTH2: {0x4818c423083a8ddd0000000a0000000a, user} DIGEST-MD5 authentication succeeded.
Apr 30 2008 16:22:17 RSAVALIDATE: success.
Apr 30 2008 16:22:17 AUTH2: {0x4818c423083a8ddd0000000a0000000a, user} DHX authentication succeeded.
Apr 30 2008 16:22:17 KERBEROS-LOGIN-CHECK: user {0x4818c423083a8ddd0000000a0000000a, user} is in good standing.
Apr 30 2008 16:22:17 KERBEROS-LOGIN-CHECK: user {0x4818c423083a8ddd0000000a0000000a, user} authentication succeeded.
Apr 30 2008 16:22:18 RSAVALIDATE: success.
Apr 30 2008 16:22:18 AUTH2: {0x4818c423083a8ddd0000000a0000000a, user} DHX authentication succeeded.
Now, all the entries in our log (for remote logins) show:
May 2 2008 10:35:39 KERBEROS-LOGIN-CHECK: user {0x4818c423083a8ddd0000000a0000000a, user} is in good standing.
May 2 2008 10:35:39 KERBEROS-LOGIN-CHECK: user {0x4818c423083a8ddd0000000a0000000a, user} authentication succeeded.
May 2 2008 10:35:39 KERBEROS-LOGIN-CHECK: user {0x4818c423083a8ddd0000000a0000000a, user} is in good standing.
May 2 2008 10:35:39 KERBEROS-LOGIN-CHECK: user {0x4818c423083a8ddd0000000a0000000a, user} authentication succeeded.
May 2 2008 10:35:39 KERBEROS-LOGIN-CHECK: user {0x4818c423083a8ddd0000000a0000000a, user} is in good standing.
May 2 2008 10:35:39 KERBEROS-LOGIN-CHECK: user {0x4818c423083a8ddd0000000a0000000a, user} authentication succeeded.
i.e...Single-Sign-On and they're FAST.
no more AUTH2 entries overlapping with KERBEROS.
(local Authentications still show AUTH2 when using WGM)
The solution was pretty straight forward, But only applies if the system is using Single-Sign-On with AFP shared home folders and the Authentication for AFP is set to Kerberos.
Delete ;ApplePasswordServer entries from all user/computer combinations that are having problems.
I actually deleted it from all users and Computers. (Except the Server Computer and Directory Administrator that uses WGM. When I tested these, WGM would not authenticate Diradmin)
It can be done in the GUI from the inspector tab in WGM
find the attibute
dsAttrTypeStandard:AuthenticationAuthority
click to open
If there are two entries: ApplePasswordServer and Kerberosv5 then:
Edit the ApplePasswordServer entry (You can copy the text into an editor and save it for future use if needed, all entries are the same for all computers and users, so you only need 1 copy, and you can paste it back into new entry to put it back,...If needed....maybe for older systems, mine are all Leopard.
Now delete, OK, and Save the changes
After its done, check the logs again to make sure that all remote logons now show
KERBEROS-LOGIN-CHECK:
and they should be FAST.
Hope this helps
Steve

Intel Xserve with Leopard Server 10.5.5 won't let me in via login

A power outage appears to have created some issues with my intel Xserve, running Leopard server 10.5.5
The System identifier light was blinking, so I booted up from the Leopard disk and found out that my mirrored internal array needed to be rebuilt. No problem, 4 hours later, I repair permissions on the mirrored internal array, everything gets "repaired". Change bootup disk to the internal 10.5.5 mirrored array and reboot. System Identifier light stopped blinking, things were looking good.
The login screen comes up and when I put in the admin username and password, the screen does the shake of the wrong login.
What's weird is, on my laptop I can use Server Admin, Workgroup Manager, and the screen sharing for the server....with the admin username and password.
So, I figure, perhaps the mirror rebuild requires me to reset the admin password. So, boot back up from the Leopard Server install DVD, run the password utility. and reset the main account password.
I change the boot drive back to the internal mirror, same thing. I'm stuck. I can't get past the login screen on the actually server....or via the screen sharing...and Server Monitor appears to be stuck at 'waiting for response'. I can, again, use Server Admin and Workgroup Manager on my laptop and make changes to the X server software....but I can't log into the X serve.
My webpage, wiki, etc....are all serving fine. But, I'd like to be able to figure out what I'm doing wrong...log back in and run super duper, etc.
Help...please...

Spent all day with apple support. They said it sounded like the LADP database was corrupted. They had me try to login as root, via an opendir account, etc. No luck.
So, they suggested I do a fresh install of the Leopard server on an external drive. Did that. They then suggested I use my laptop and the workgroup manager app to log in to the xserver, export users, groups and computers....and to copy over the library/collaboration folder to the external "clean install" of Leopard server.
Did that and followed the instructions to "relink" the metadata.plist files in each group, to the GUID to the groups in workgroup manager. First issue, they weren't different GUID strings.
Well, that didn't work...kept getting file not found error. When trying to access the domain.com/groups/groupname...it should've asked for authentication. And let me into that wiki...but no, apache error page.
So, they had me create a new "test" group....added a user. Start and stopped the web...etc. This didn't create a new wiki entry (when we replaced my custom index.html to the default index where groups/wikis/blogs populate automatically at the main). And, there's no new "test" folder in the library/collaboration files.
They then said "well, it must be because you don't have reverse DNS configured right, that's why the new wikis won't set up". I've contacted dyndns.com...but I don't think that's the problem.
So, I've rebooted my xserver to the internal drive. The wiki and blog is still there, still accessible the way I like....I still can't login to the xserver.
So, I'm wondering, if anyone knows a way I can boot up my xserve in the target drive mode, hook up my laptop and replace / swap whatever admin files so that when I boot up my xserve, I can login again.
There has to be a way to hard fix a hidden file? Replace a DB? Some awesome terminal command to get me in and fix the admin account / password....
Or, does anyone know if the reverse DNS issue applecare cites is legit? Doesn't make sense how, the same public ip and domain name, that's worked for some time...suddenly doesn't???
I'm hoping someone can help me.

Can I install/run the Client version of Leopard on an XServe?

Can I run an XServe with the client version of Leopard? I'd like to use the license which ships with the new server on another system.

Hi
Yes.
Tony

Are there any problems with Snow Leopard Server (Xserve) and PPC Clients

Hi,
are there any problems identified yet with Snow Leopard Server, installed on a Xserve and PPC Clients running Mac OS X Tiger and Leopard?
Currently I have a Xserve Intel running Leopard Server and about 12 Mac Minis PPC running Mac OS X Tiger and Mac OS X Leopard. The Xserve serves services like DNS, OpenDirectory, Software Update Server, NetBoot, etc. All users have Home Directories stored on the Xserve.
Now I want to install Snow Leoaprd Server on the Xserve, but I wonder if there are any problems using the PPC Clients? I have read something like this on a german website.
Thanks!

We've actually found that the Server 10.6.3 DVD does an amazingly smooth job of upgrading 10.5.8. We've been upgrading our production servers and nothing has gone wrong yet. Snow Leopard employs an archive and install method of upgrading which results in an install which is very close to a clean install. So it's been very convenient for us because our servers are used as Windows PDCs and it's a pain in the *** to have to re-join all PCs to the domain if we start from scratch.

Server Monitor on Xserve running Client OS

I have an Xserve running the regular client OSX (Filemaker Server, didn't see the point in installing the full Server OS). Is there any way to get Server Monitor running? I would like to be able to keep an eye on the hardware functions.

Is there any way other than loading Mac OS X Server, you mean? Not directly.
You could enable and use the [SNMP daemon within the Leopard Mac OS X client|http://www.bynkii.com/archives/2007/12/aprimer_to_snmp_on_mac_os_x1.html], but that won't give you the Server Monitor interface.
Or you could see if the [Lithium software|http://lithiumcorp.com] is sufficient for your needs.
Or you could load the 10-client Mac OS X Server distribution, which has the monitoring stuff baked in.

Can I fool the Mac App Store into thinking my mini runs Snow Leopard Client rather than server?

I've googled this to death and can't find an answer because, well, Google ain't all its cracked up to be.
I highly object to Apple forcing you to pay for both Lion Client & Server if you have a server model Mac. Especially seeing as Lion Server software is just an app that sits on top of standard Lion, and that you can remove/disable it anyway. I bought a Mini from a chap in Hong Kong purely because it was way more powerful for the price than any Mini's available running a client OS here in the UK. I have no intention of learning to use the server side products, its not an interest and never will be. Plus some of the ways in which OS X 10.6 server operates gets on my nerves because of the control the server has over certain functions.
I'm happy to go through the process of a fresh install of retail Snow Leopard firest IF I really have to as it's cheaper than Lion & Lion Server, but ultimately it's just £26 spent for the sake of it. I was wondering if anyone knows of a system file that can be tweaked so when the App Store checks my OS version, it doesn't see server, only standard Snow Leopard?
Having read the online instructionals on how to move and save the download files and then perform a fresh install from a boot device (as the upgrade under the above circumstances would likely wreck the system) I'm living in hope I don't need to go through retail Snow Leopard first.
Thanks all!

Probably the best idea although do read their Terms Of Use first. Do realize that anybody here who answers your question is in contravention of the YOU as much as you would be for posing the question.
But good luck
Pete

Deployment status sucess but program does not run in client machine

Hello Guys,
I have created a package program to Run a batch script Install.bat
Program Properties:
Command Line: Install.bat
Run: Normal
After Running: No action required.
Run Mode: Run with administrative rights (Allow interact with users)
When i deploy this package i see Success in deployment status very soon, But the program doesnot run in client machine.
Please find my batch script below for more info.(manually installed Install.bat in system context cmd, it works perrfectly )
Please help me, where am going wrong
rem ECHO OFF
SETLOCAL
SET WORKING=%~dp0
echo Installing Office 365 pro plus NY package:
echo ------------------------------------------
%WORKING%setup.exe /configure %WORKING%install32ny.xml
IF NOT EXIST "C:\Program Files\Microsoft Office 15\root\" (goto _ExitInstall)
:_CopyingFile
echo Copying Script to Office 365 INSTALLDIR:
echo ----------------------------------------
XCOPY %WORKING%Pin-Unpin.vbs "C:\Program Files\Microsoft Office 15\root" /C /F
IF NOT EXIST "C:\Program Files\Microsoft Office 15\root\Pin-Unpin.vbs" (goto _ExitActivesetup)
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\Office365ProPlusNY" /v "StubPath" /d "cscript.exe \"C:\Program Files\Microsoft Office 15\root\Pin-Unpin.vbs\""
/t REG_SZ /f
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\Office365ProPlusNY" /v "Version" /d "1.0" /t REG_SZ /f
%WORKING%Launch.vbs
exit /b %errorlevel%
:_ExitInstall
echo Aborting Installation:
echo ----------------------
echo Office 365 installation failed.
echo %errorlevel%
exit /b 3
:_ExitActivesetup
echo Aborting Installation:
echo ----------------------
echo Activesetup Script error to INSTALLDIR
echo %errorlevel%
exit /b 4

It's just starting the command lines one after the other and after that simply returns a success of starting all the commands. Two things you should do to successfully use a batch file like this:
Use start-wait constructions, so the next action won't start before the previous action is finished. For the exact command lines see:
http://technet.microsoft.com/en-us/library/bb491005.aspx;
First test the batch file with psexec, to see how it behaves with SYSTEM credentials.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Can an xserve running 10.5.8 handle clients machines running 10.8.3

I have an xserve running 10.5.8. We got three new machines running 10.8.3. None of the programs on the client machines want to open, iphoto, mail, contact etc.

Just an FYI for anyone who might be searching for this solution. I recently discovered that the NSF share fix works also on a 10.6.8 OD server with OS X 10.8 clients using network homes, to resolve write to network application compatibility issues.

Binding Snow Leopard Clients to 10.5.8 server

We have just purchased three new iMacs to add into our current network. We are using Network Home Directories hosted on an Intel Xserve running 10.5.8 server. The iMacs are all loaded with Snow Leopard (10.6.1).
I cannot bind the computers to the server to allow login using network accounts. I attempt this via System Preferences-> Accounts -> Login Options -> Join Network Account Server.
The error message is "Authentication failed. Please check the name and password and try again."
I have attempted to add the computer using both the first authentication window (when clicking Join), and the Open Directory Utility.
I can add computers using 10.5.8 client. I was also able to install Snow Leopard (10.6) as an upgrade to one of the 10.5.8 machines and maintain the network login functionality.
Thanks for any help or advice.

I am not sure I am doing what you suggest correctly.
From the directory utility i was able to pull down the File menu
and connect to the xserve using the diradmin account. This caused
a new path to appear in the search policy tab.
However, i still cannot bind to the server and still get the
authentication error when I try.
After rereading your post, I realized that you had added the path
a different way. So I deleted the one I had added via File -->
Connect and just went to the Search Policy tab and added a custom
path the way you said. Same results in the end. I could not bind.
I may just install 10.5 on these computers and be done with it.
My method was a little different. In Directory Utility, I went
to Advanced Settings, hit the '+' and added the open directory
server. Then I went to the Services tab, selected LDAPv3, and
hit the little pencil to edit. Then I selected the open
directory server, hit Edit, and tried to bind, but it wouldn't
work at first. Back in the Directory Servers tab, I noticed that
the little status light was grey instead of green. Then I went
to the Search Policy tab and noticed that the open directory
server wasn't in the path, so I went to Custom Path and manually
added it. After that, I was able to bind and the little status
light went green.
However, in this process I also did some other messing around on
the command line. After the first time I tried to bind and
couldn't, I quit the Directory Utility and opened a Terminal
window. As root, I wiped out the /private/etc/krb5.keytab file
and the contents of the /private/var/db/krb5kdc directory, and
then rebooted. That is:
cd /private/etc
sudo mv krb5.keytab krb5.keytab.orig
cd /private/var/db/krb5kdc
sudo rm -rf *
(Be careful with the last command!)

Leopard client controls view of tiger server share point

Hi, recently purchased a Mac Mini running Leopard all patched. Connected via afp to a Xserve RAID, Xserve running a sharepoint using ACL's. In list view the leopard client controls the list view on the Xserve, meaning that all the other Tiger clients see the leopard clients folder structure when they connect to the sharepoint. I have not changed any settings on the Xserve, just re-propogated the permissions and ACL's.
Any ideas would be great,
Andy

ipb1962 wrote:
BUT When I use the DHCP service to specify my DNS to a Leopard Client from (Tiger Server on a G5)
it does not resolve to any internet address.
Can you clarify what you mean here?

Leopard client login problem (Tiger server)... why can't I authenticate?

I look after a number of Macs and PCs at my company. Most Macs are running the latest version of Tiger but the newest machine came with Leopard. All users log into network accounts on our Xserve, running OSX Server (Tiger). However, the Leopard client machine refuses to log in to any network account, including the one I set up specifically for the machine's user, shaking its login window at me.
Users connect using Open Directory Master on the server and none of the Tiger clients have ever had problems logging in.
On the troublesome client machine, I have bound to the server correctly in Directory Utility which declares that the server is responding normally. At the login screen I get a green light and "Network Accounts Available" when I click through the options above the user name field so I know the machine can see the server.
I can successfully log in to a local account and subsequently mount the server volumes using the new name and password I've set up for the user.
What have I missed?
So far, in my attempts to resolve this I have done the following:
Removed the password from the new account;
Unbound from the server, changed the short name of the computer, re-bound to the server;
Tried logging in to other accounts known to be working;
In WGM checked that the NFSHomeDirectory entry shows the complete path for the user's home directory;
Trawled through endless forums for clues.
Kerberos is not running. Does it need to be for authenticating Leopard users?
Is there an issue with clear text passwords in Leopard? Seemingly eliminated through a no-password test account.
I'm sure that I logged in successfully once after setting up the machine but, after installing Leopard updates, logging in has consistently failed.
Anyone else having similar problems? Better yet, anyone have any answers?

No need to apologize. I learned the same way you are...
I think you may end up re-binding the 10.4 clients if you kerberize the server.
You may want to go to the server forum for folks with more definitive annswers.
http://discussions.apple.com/category.jspa?categoryID=96
In any case, make sure you have a reliable backup before you do anything.
Jeff
Message was edited by: Jeff Kelleher

Distributing OS X 10.8 Updates with Xserve running 10.6.8?

Hello All,
Is it at all possible to distribute Mountain Lion updates via our Xserve running 10.6.8? We are currently distributing updates for previous OS X releases via this server, including Lion.
Is it required to have Mountain Lion Server to distribute updates to ML machines? Or can these updates be pooled in our current Software Update repository? We currently only have one Mountain Lion machine for testing purposes, but this will impact how we move forward.

For clarification the Server is running 10.6.8 intentionally for compatibility with essential software for our business. We are not specifically looking to upgrade the server to Mountain Lion. Predominantly we would simply like to direct each client machine towards the server to receive softwre updates as we do with the Snow Leopard and Lion machines.
I am simply asking if ML software updates can be added to the Xserve's software update service as opposed to having to run a separate ML server for ML clients.

Can a Snow Leopard client connect to a Lion Server?

I have an XSAN setup with two Mac Mini servers.
I have a few Xserve lying around and I want to make use of them.
One Duo Core which is not working at the moment. I think I can install Lion on that one? Right?
Then I have two G5 - none intel, which I'm thinking I'll reinstall Snow Leopard on and use them as clients.
Can they connect to a Lion Server? I have a few XSAN licenses left which I think I need for OS's older than Lion?
I short, can a Snow Leopard client connect to a Lion Server?

One Duo Core which is not working at the moment. I think I can install Lion on that one? Right?
You can't install Lion on a Core Duo-based system It requries Core2 Duo as a baseline. The Core Duo is a 32-bit chip whereas the Core2 Duo is 64-bit.
Then I have two G5 - none intel, which I'm thinking I'll reinstall Snow Leopard on and use them as clients.
Nope, again. Snow Leopard requires an Intel-based system. The highest you can go with the PowerPC machines is Leopard (10.5.x)
Can they connect to a Lion Server? I have a few XSAN licenses left which I think I need for OS's older than Lion?
This may be irrelevant given the above, but define 'connect' please. There are a myriad of ways of 'connecting' a client to a server. In many cases they don't have to be the same OS, platform, processor or anything else (how many web servers do you think are running Mac OS X to match your client?

Binding Snow Leopard Clients to 10.5.8 server 2

Has anyone found a solution to this infuriating problem of not being able to pair a Snow Leopard client to 10.5.8 server?
http://discussions.apple.com/thread.jspa?messageID=10969925

I am not sure I am doing what you suggest correctly.
From the directory utility i was able to pull down the File menu
and connect to the xserve using the diradmin account. This caused
a new path to appear in the search policy tab.
However, i still cannot bind to the server and still get the
authentication error when I try.
After rereading your post, I realized that you had added the path
a different way. So I deleted the one I had added via File -->
Connect and just went to the Search Policy tab and added a custom
path the way you said. Same results in the end. I could not bind.
I may just install 10.5 on these computers and be done with it.
My method was a little different. In Directory Utility, I went
to Advanced Settings, hit the '+' and added the open directory
server. Then I went to the Services tab, selected LDAPv3, and
hit the little pencil to edit. Then I selected the open
directory server, hit Edit, and tried to bind, but it wouldn't
work at first. Back in the Directory Servers tab, I noticed that
the little status light was grey instead of green. Then I went
to the Search Policy tab and noticed that the open directory
server wasn't in the path, so I went to Custom Path and manually
added it. After that, I was able to bind and the little status
light went green.
However, in this process I also did some other messing around on
the command line. After the first time I tried to bind and
couldn't, I quit the Directory Utility and opened a Terminal
window. As root, I wiped out the /private/etc/krb5.keytab file
and the contents of the /private/var/db/krb5kdc directory, and
then rebooted. That is:
cd /private/etc
sudo mv krb5.keytab krb5.keytab.orig
cd /private/var/db/krb5kdc
sudo rm -rf *
(Be careful with the last command!)

No Memory Status on XServes Running Leopard Client

Similar Messages

Maybe you are looking for