Link to home
Start Free TrialLog in
Avatar of MutleyFDI
MutleyFDIFlag for United States of America

asked on

Mac OS X Clients Unable to Connect to Shared Volume on Windows 2003 Server

Experts:
Have had a Macintosh/Windows file share running smoothly for all users (Mac and PC) on a Windows 2003 server for over a year now.  Two days ago the server was abruptly powered off (user disconnected power cord instead of USB cable...duh!) and, after restarting, none of the Mac users are able to connect to the server while all PC users see all shared folders without problem.
I have tried restarting FSM...no luck; uninstalling/reinstalling FSM...no change; uninstalling/reinstalling AppleTalk protocol...no love there, either.  Deleting/recreating a new Macintosh volume...nothing seems to help.
I've also followed the steps outlined in http://support.microsoft.com/kb/147909/en-us and am coming across this unusual observation: Method 5 in the KB article is an intentional corruption of the Macintosh volume index, then stopping/restarting FSM to force a rebuild of the index.  An error message is supposed to appear in the Event logs when the index is corrupted but none appears.  It's as if the server shows all signs the share is being created (no errors from the Wizard) but it's like it doesn't actually happen.
Short version is I'm desperate now.  Have tried (nearly) everything under the sun but cannot get Mac users reconnected...they are trying to connect to afp://10.10.10.14 (like so many times before) but time out...no username/password prompting (share is set for both Apple Cleartext or Microsoft authentication...have tried changing those parameters, too)...any help would be greatly appreciated.
Thanks.
SOLUTION
Avatar of pheidius
pheidius

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of MutleyFDI

ASKER

I've checked into the information in the links above (thanks for the info) but still am getting no love from either the Mac OS X clients nor the Windows 2003 server.

Given this screnario:
  OS X clients were connected at 2pm ->
  Server abruptly powered off/brought back online at 2:10pm ->
  OS X clients no longer able to connect at 2:11pm
what else might I be looking at here?  the OS X clients can ping the server so network issues aren't at play (I don't think)...corruption of Windows system files?  Seems unlikely given that PC users have no problems interacting with the shared folders...only our Mac peeps.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
All had been connecting via afp when the incident occurred.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Sorry for th delay in getting back to this. Tried the above with no luck in Mac users regaining access to the share.  Ultimately resorted to creating a new share on another windows 2003 server and copying all of the files from the old to the new. Inelegant but effective.
Avatar of ctsmequon
ctsmequon

Futher comments from a user who experienced this exact same problem that may help a user in the future:

These are my internal notes to our tracking system regarding this issue.

User reported the server went down last night due to a power outage. After rebooting the server, the AFP/SFM shared volumes were not accessible to the Macs, but the SMB volumes (even the same folders) were accessible to both PCs and Macs. The server did not show any error messages in the logs regarding this issue. I was not able to find any configuration settings that were not correct (none had been changed), but the AFP/SFM volumes starting coming back on their own one at a time, with the Production volume (320GB) coming back after five hours from the boot time. It would seem the server needed to recreate a AFP/SFM index, but I do not know which one, how to monitor its progress, or how to initiate it should it fail to come back the next time.

*AFP/SFM = Apple File Protocol/Services For Macs