I have a classroom of 24 MacBooks running Tiger. The students are training to use Finder -> Go -> Connect to Server to mount their samba file server account shares and a communal share for shared files. However, in every class session, for about 3 or 4 students, the Username-Password dialog box reappears after the student mounts the share, but the share does not show on the desktop or the Finder. If the student reinputs the information correctly, an error message appears that reads that the user is already connected to the server. However, there is no icon on the desktop or in the Finder, and applications browsing to save files to or open files from the network share cannot get there.
If I do Alt-Cmd-Esc and force relaunch of the Finder, the icons appear on the desktop but not in the Finder window.
Also, here's a scenario:
1 - User-A logs into the "student" account and then mounts a samba share and then logs out but does not reboot the Mac.
2 - User-B logs into the "student" account.
Result - User-B has User-A's samba share still mounted and available, and what is more, if s/he tries to unmount the disk, the OS won't let him/her, and in addition, if s/he tries to mount his/her file server share, the error message about already being connected comes up.
I have looked this problem up on MacOSXHints and other forums like MacRumors, but the threads ended with "This has been fixed in Leopard."
That is not an acceptable solution.
Is there a fix for this problem that would be usable in a classroom where students' user level is very low? That means no terminal tricks. The computers must be predictable and reliable to avoid wasting class time with technical problems.
If I do Alt-Cmd-Esc and force relaunch of the Finder, the icons appear on the desktop but not in the Finder window.
Also, here's a scenario:
1 - User-A logs into the "student" account and then mounts a samba share and then logs out but does not reboot the Mac.
2 - User-B logs into the "student" account.
Result - User-B has User-A's samba share still mounted and available, and what is more, if s/he tries to unmount the disk, the OS won't let him/her, and in addition, if s/he tries to mount his/her file server share, the error message about already being connected comes up.
I have looked this problem up on MacOSXHints and other forums like MacRumors, but the threads ended with "This has been fixed in Leopard."
That is not an acceptable solution.
Is there a fix for this problem that would be usable in a classroom where students' user level is very low? That means no terminal tricks. The computers must be predictable and reliable to avoid wasting class time with technical problems.