Home › Forums › OS X Server and Client Discussion › Open Directory › Network Library and Application shares inaccessible
- This topic has 1 reply, 1 voice, and was last updated 17 years, 11 months ago by
amsterdam.
-
AuthorPosts
-
November 24, 2008 at 2:05 pm #374837
amsterdam
ParticipantI’ve got a strange problem that cropped up today when I installed the 2008.007 security update.
System:
10.5.5 server, Active Directory/Open Directory integrated, with a Application and Library sharepoint mounted by other 10.5 clients.Problem:
/Network/Library and /Network/Application sharepoints are no longer accessible. I do most of my work from the command line… When trying to “cd” to either directory, the clients report “Unknown error: 118” while doing the same commands on the server reports “Too many levels of symbolic links”What I’ve tried:
1) I discovered 4 entries in the Open Directory database, under /LDAPv3/[server]/Mounts. 2 of them pointed to the correct location of the sharepoints under /Volumes/raid — the Xraid attached drive, the other 2 pointed to Library and Applications sharepoints on /Shared Items, which aren’t there. I removed the entries… but it didn’t fix things.2) I re-ran dsconfigad -enablesso because I noticed that other sharepoints configured to mount when the user logs in (via computer group prefs under WGM) where not working because the server wasn’t recognizing kerberos tickets from Active Directory. After re-kerberizing, the other sharepoints mounted properly, but the Library and Application shares still did not work as expected.
3) Re-indexed ldap… a shot in the dark, but no avail.
As I said, the problem only appeared today when I ran software update that installed the 2008.007 security update, as well as the CD/DVD Migration Sharing update and a Java Update, then rebooted. It’s been a while since I rebooted, so it was either the security update or something to do with rebooting.
Can anyone point me to some other tests to perform?
November 25, 2008 at 1:42 am #374853amsterdam
ParticipantWell, the solution was easy… Guest access was somehow disabled on the AFP service. Doh!
I did, however, read up on the security update and there was a change made to singe-signon which explains why I had to re-run dsconfigad -enablesso
word to the wise…
-
AuthorPosts
- You must be logged in to reply to this topic.