Export (0) Print
Expand All

Administrator and user issues and solutions

Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Administrator and user issues and solutions

What problem are you having?

A Macintosh-accessible volume is unavailable to a user.

Cause:  The volume might be configured as a private volume. A private volume is any volume for which the primary and Everyone groups have no access permissions. Only the volume's owner has permissions. In this case, only the owner has access to the volume.

Solution:  To make the volume accessible to users, the owner should give the primary or Everyone group at least one permission for the volume.

Cause:  If the Macintosh-accessible volume is on a CDFS volume, and it appears in the Chooser but cannot be selected, the CD-ROM on which it was created might not be in the disk drive.

Solution:  Be sure that the correct CD-ROM is in the disk drive and that the drive door is closed.

A Macintosh user's password has expired without notification.

Cause:  Users will be notified that their passwords have expired only if the Microsoft user authentication module (MSUAM) files are installed on their clients. If they are using the Apple standard UAM, they will be told only that their logon attempts failed and to try again later. For more information on installing the Macintosh client software, see the Teachtext ReadMe file in the MSUAM volume or see Authentication and Services for Macintosh Concepts.

Solution:  Install the MSUAM files on the user's client computer.

Users have forgotten their passwords.

Cause:  If users have not logged in for an extended period of time, or the password they used was too complex, they may forget their password.

Solution:  Assign the users new passwords.

An "incorrect password" message is displayed, even though the password was entered correctly.

Cause:  Users might have two accounts, with different passwords, on separate domains.

Solution:  Have users enter the domain and then the account name in Name when they log on. For example:


The computer running Services for Macintosh appears in the Chooser on Macintosh clients and then disappears. The appearances are erratic and unpredictable.

Cause:  Two physical AppleTalk networks have been given the same network numbers. The server started first works as expected. When the second server is started, it appears in the Chooser on one Macintosh client, and then disappears and appears in the Chooser on a different client. The order of appearance is unpredictable.

Solution:  Check the network numbers used for each physical network. When you find the duplicates, change one so that all physical networks use unique network numbers. After you make the change, restart the AppleTalk Protocol on the server on which you made the change. If you find no duplicates, see if your network has a bridge that is filtering packets. It might be filtering out the requests from the second server to find a unique address.

Cause:  Zones and network numbers are no longer in correspondence. This situation could occur if you recently changed zone names.

Solution:  When you change the name of a zone, you must shut down the routers directly connected to the networks in question for 10 to 15 minutes before restarting. This allows the other routers to discard old zone information.

Cannot find a file or folder.

Cause:  The user might not have the necessary permissions for the folder that contains the file or folder in question.

Solution:  The administrator or the owner of the folder can reset permissions to allow the user to access the folder.

Cannot save a file with an 8.3 file name from the Macintosh computer.

Cause:  A file might already exist with that name. However, Macintosh users cannot see it.

Solution:  Give the file a different name.

Cannot find a server.

Cause:  There may be a problem with the cable system between the client and the server.

Solution:  Follow these steps:

  1. Be sure the cable system between the client and the server is correct. Be sure the network connection, layout, and cable termination conform to the specifications of the cable system you are using.

  2. Start with the client that can't find the server. If the cable system is LocalTalk, ensure that the LocalTalk connector box is firmly attached to the printer port on the back of the Macintosh client, not the modem port.

    If the cable system is not LocalTalk, ensure that the network connector is securely connected to its port. In Control Panel, double-click the Network icon to review other network settings.

  3. Determine whether other clients are having the same problem.

    If they are, check the cables and connections at the server, and ensure that the server is operating properly. If the server is not the source of the problem, proceed to step 4.

  4. Check for breaks in the cable system. If the missing server is on a local network, check each client between the client that can't find the server and the server until you find the server in the Chooser. The break in the cable system is between the client that shows the server in the Chooser and the one that does not.

    If the missing server is on a different physical network on the internet, use your router seeding plan and server information table to determine which client is the first one beyond the router that links the two networks. Test that client, and then test each client beyond it (in the direction of the server) until the server appears in the Chooser.

    If the server was visible at the first client, work backward toward your own network, testing the client adjacent to each router until the server fails to appear in the Chooser. Isolate the break by testing the clients on this network.

  5. When you have isolated the network break, check the network cables and connections at that location to make sure all are securely attached, and try again to display the server in the Chooser. If necessary, try replacing cables or connectors.

Cannot see any zones within the Chooser on a Macintosh computer.

Cause:  There might be router problems.

Solution:  Check for the following:

  • The Macintosh computer might be running on an AppleTalk Phase 2 network without the correct Ethernet driver.

  • The router might be using Phase 1 and the rest of the internet is using Phase 2.

  • The Macintosh computer is configured for one type of network media (such as LocalTalk) but is actually on a network that uses a different media type (such as Ethernet or token ring).

If the problem persists, make sure all routers are configured properly.

The Microsoft user authentication module volume cannot be found.

Cause:  When the computer running Services for Macintosh was installed, there might have been insufficient disk space for the Microsoft user authentication module (UAM) volume. Or the computer running Services for Macintosh might have been installed without an NTFS partition.

Solution:  You can create the volume by typing and entering the following at the command prompt: setup /i oemnxpsm.inf /c uaminstall. This command line copies UAM files to the AppleShare folder in the first NTFS partition and sets up registry values for this volume in the Registry Editor.

The view of a folder is erased or does not match the view selected in the View menu.

Cause:  The Finder occasionally cannot show the correct view of a folder.

Solution:  The folder owner must log on to the server, connect to the Macintosh-accessible volume, and, on the View menu, select a view (such as View By Icon, View By Name, and so on). The selected view then remains in effect.

A file is now displayed with the default Windows icon instead of the correct icon.

Cause:  The application that uses that type of data file might have been removed from the Macintosh computer.

Solution:  If the file had no resource fork, use the Apple ResEdit utility to reset the file type and file creator of the file. Use this utility only if you are experienced with it.

A user of an x86-based computer cannot see the contents of a folder.

Cause:  The user of the x86-based computer does not have sufficient permissions to view the contents of the folder.

Solution:  Use the computer running Services for Macintosh to make sure the user has Read permission, or the folder owner can use a Macintosh computer to give the user of the x86-based computer both the See Files and See Folders permissions. (A user of an x86-based computer must have both these permissions to get the Read permission.)

A Macintosh user did not receive a server message.

Cause:  The Macintosh user is running a version of the AppleTalk Filing Protocol that is older than version 2.1.

Solution:  Make sure that the user upgrades to version 3.0 of AppleShare, which allows users to receive messages.

A user cannot automatically connect to a Macintosh-accessible volume using an alias.

Cause:  Macintosh clients can be configured to automatically connect to volumes when the client is started or when the user double-clicks an alias to an object on a volume. However, automatic connection to volumes is not supported by the Macintosh system software if the volume is configured with a volume password, or if the user originally used the Microsoft user authentication module (MSUAM) to connect to the volume.

Solution:  If the volume has a password, you can mount it through the Chooser and then use the alias. Or you can specify that it be opened at system startup time when you mount the volume. If you are using MSUAM to log on to the server, you must mount the volume through the Chooser and then use the alias.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2014 Microsoft