Services for Macintosh (SFM) was introduced with Windows 2000 Server and is still a part of the OS in Windows Server 2003. There are a couple of differences, though, which threw me off the first time I encountered them.
Authentication and Mac OS 9
In order to connect to a Mac File Share on Windows Server 2003, the client must have the Microsoft UAM installed. This authentication module is stored in a file share on the Windows server. But the client can't connect to the file share until the software is installed. One solution is to temporarily reduce the security level of the Mac File Share by permitting unencrypted connections. Then after installing the authentication module the security level can be increased again.
Another possible problem with this is if the password for the Windows account is too long, the Mac user will be unable to log in using the regular Apple authentication.
Share is Read Only
In Windows Server 2003, file shares for the Macintosh are created read-only by default. To allow Mac users to add, modify, and delete files on the Windows server, right-click on the file share in the Computer Management control panel and uncheck the read-only box on the General tab.