Our school network has 2 x Windows Servers, 100 XP SP2 PCs and 5 Tiger eMacs networked. No problems when Servers were 2000. Upgraded Servers to 2003, and now users home directory won't mount on Macs, and hence login fails. If I login as local admin on the Mac, I can connect to the Server Users' share with SMB, but not with AFP, which I believe is required to mount the home folder at login. I tried connecting to a share on another Mac with AFP, which worked, showing the Mac end is OK. This confirms there is a problem at the 2003 end (since it worked with W2000).
Services for Mac is installed, but it seems that AFP requests aren't responded to. Windows firewall is turned off. I also right-clicked on My Computer on Server, and under 'Manage', set 'Shared Folders' to 'configure file server for Mac'.
We want the home folder to be the same, so that users see the same files whether they log on to a Mac or a PC.
I used dsconfigad on the Mac, and can see that it's getting the right home dir from the user profile on the Server.
I ran TCPView on the server, but the process sfmsvc which I think is the Mac File Server doesn't seem to have any port open. But perhaps it doesn't work like that?
I have Googled everywhere. Plenty of info about dealing with signed comms, but not much on home folder mapping. I should point out that If I change the home folder protocol to smb, login (authentication) proceeds OK, but the home folder doesn't mount. But you can use Connect to Server to mount the Windows user folder. That's not as good as being the same place as Home! The users will be forever putting files in the wrong place, and blame me!
Start Free Trial
