Home › Forums › OS X Server and Client Discussion › File Serving › Topic: 10.4.6 clients dropping 10.3.9 server home folder
- This topic has 2 replies, 1 voice, and was last updated 18 years, 6 months ago by
jkonrad.
-
AuthorPosts
-
June 8, 2006 at 6:19 pm #366372
jkonrad
ParticipantFor over a year our school had many 10.3.x clients authenticating against a win2k AD, and then finding their home folders via AFP on an OS X server 10.3.x. Worked very, very well.
Now we upgraded one lab of our clients to 10.4.6 and the process breaks.
What happens is now a student will log on successfuly (against the AD), their home folder will connect. In the finder they will be able to go to their document folder or their desktop or where ever and all is good. Then they run apps. Now their “Documents” folder in the left edge becomes un reachable. If they opened a file from there, then try to just save again, it will say the file is locked.
However if the use the “Network”, then “Servers” then specific stuff they can still see their home folder, and then their documents folder and can save a new copy of their document to the server!
For 90% of the students this means they cannot work. It’s too many steps. I can’t even get my staff to follow the Network>servers>studentserver>share path.
Especially the save while working being broken. It loses most of them.
Please help!
(Yes I posted this to Applie forums, but no one is helping over there!)June 15, 2006 at 9:53 pm #366426Anonymous
GuestSimilar issue here– using a Linux NFS Server, but the behavior seems identical.– heres what I posted to apple:
This one has got me scratching my head. We run workstations authenticated by an Mac OS X 10.3 server, that access files on a Linux NFS file server. All directories for users are automounted, including home. We have automounts for a Public directory AND home directories that exist on the same Linux volume.
This had worked trouble free until our workstations were upgraded from Panther to Tiger. Then we started getting occasional hiccups, where a person would be saving a file to a Public directory (generally from a CAD program, though not always) and all of a sudden, Finder would report the file couldn’t be found and not allow the save. The user can save to Desktop (which is Network mounted) or even to another folder in the Public directory– just not to the directory that was being worked in. Restarting finder will not report the correct contents of said directory. Only a reboot will fix the issue.
I have tried changing from TCP NFS to UDP NFS and back, I have turned off Spotlight on all the workstations, I have applied all updates, and nothing seems to cure the problem. There is nothing in any log on the workstations recording any connectivity or finder problem, nor is there any indication of problems in the server logs. I have done an fsck on the server volume to check for corruption, and it has reported being clean (twice).
This issue only seems to hit one or two random people on average once a day. There is no regularity in pattern, work being done or user. The only common thread is this behavior did not occur on Panther.
I’m stumped. Any ideas?
September 26, 2006 at 5:18 am #367114jkonrad
ParticipantThis is not a fix, but I found a similar discussion on Apple’s site. The workaround goes like this:
STEPS (***ON THE CLIENT***)
(1) Open the following file : /etc/hostconfig
(2) Change the line “SPOTLIGHT=-YES-” to “SPOTLIGHT=-NO-”
(3) Reboot
Spotlight will be disabled however your files should stop vanishing.
Thank you very much apple. We are happy that there is now a
workaround, people were losing work. Now we can rest easy. Thank you.PS : TESTED ON 10.4.5 Client and Server
Upgrading to 10.4.6 Server stopped login working before this
workaround was applied to the clients.
It seems people have had mixed results with the 10.4.6 upgrade.
Be prepared to roll back to 10.4.5 if you are applying this upgrade.”This has definately helped our lab. The full thread is here:
http://discussions.apple.com/thread.jspa?threadID=309002
Hope this some labs.
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed