AppleTalk and Services for Macintosh Compatibility Information
On Windows 2003, you can easily install AppleTalk without installing SFM (Windows XP and Windows Vista do not come with support for AppleTalk). Please see the Access Connect Manual for more information.
Windows Server 2008 no longer includes AppleTalk or SFM.
If you have the AppleTalk protocol installed, then Access Connect will appear in the Chooser for Mac OS 9 users. Access Connect will log errors which occur trying to register on the AppleTalk network in the Windows Event log. If your server does not appear in the Chooser, look for an error in the Event Viewer "Application" section on the server.
Using Services for Macintosh (SFM) on the same machine as Access Connect is supported in certain configurations, but not recommended.
Access Connect and Services for Macintosh should not be configured to share the same volumes. Because Access Connect and Services for Macintosh use exactly the same format for sharing type and creator information, the two services should not be used together to share the same volumes; otherwise, they will compete for access to the ":AFP_AfpInfo" stream and problems may occur. If Access Connect detects that Services for Macintosh is running and sharing the same volume, Access Connect will shutdown this volume and log an error to the Event Viewer.
If you must continue using Services for Macintosh, then you should be aware of the following issue. If you manually configure Access Connect to use the same machine name as SFM, then either SFM or Access Connect will not function properly. If SFM is started first, then Access Connect will work, but it will not appear in the Chooser; in this situation, Access Connect will log an error to the Event Viewer. If, however, Access Connect is started first, then SFM will not start up because it cannot register itself on the AppleTalk network. By default, Access Connect will not use the same name as SFM. SFM's default name is the name of the Windows computer, while Access Connect will use the name of the Windows computer + " IP". Consequently, if you use the defaults for both SFM and Access Connect, you will not encounter this limitation.
If you run Access Connect and Services for Macintosh on the same machine, you will need to reconfigure the TCP/IP port of Access Connect (two servers cannot use the same port). Consult the Access Connect documentation for information on changing the TCP/IP port for Access Connect.
Support for Microsoft Networking Domains
Access Connect supports Microsoft Active Directory. When you connect to an Access Connect server from the Macintosh, you normally enter your user name and password. Access Connect will authenticate this account against the primary domain of the Windows machine that it is running on. If this machine is not a member of a domain, then the account must be a member of the local accounts that appear in User Manager. If the machine is a member of a domain, then the user name you supply can be either a member of the primary domain, the local accounts or a trusted domain.
You may specify to be authenticated against a specific domain by prefixing the user name with the domain name and a backslash ('\'). For example, to authenticate using the account "rob" from the "MARKETING" domain, you would enter "MARKETING\rob" in the user name portion of your AFP client logon.
Access Connect uses the same technique for accessing owners and groups for folders in the sharing information using the Finder.
Be advised that older Macintosh clients prior to Mac OS 9.2 have only limited support for passwords longer than 8 characters.
Known Issues
Folders shared from Windows XP or 2003 will not have guest access enabled unless the "Network access: Let Everyone permissions apply to anonymous users" Local Security Setting is enabled. See http://support.microsoft.com/kb/278259 for more information about enabling this setting.
Start-up may take as long as a minute if Kerberos support is enabled within Access Connect but the server cannot access the active directory service or takes a long time to do so. If Kerberos is not needed, you can avoid the delay by disabling the checkbox Allow Kerberos Logins on the Security Settings dialog of Access Connect.