Services for Macintosh
Services for Macintosh |
|
When a Macintosh user is unable to gain access to a Services for Macintosh resource, first check the Macintosh and ensure that the following are true:
To determine whether the issue is with the Macintosh computer, try to gain access to a network entity other than the computer that is running Windows 2000 Server or a printer (for example, an AppleShare server or a printer that is not used by Services for Macintosh). If the Macintosh computer has no access to any network entity, the problem might be with the Macintosh computer.
If a computer that is running Windows 2000 Server fails to start and Event Viewer is filled with AppleTalk error messages, see whether your network has a bridge that is filtering packets. It might be filtering out the server's request to find a unique address.
The following sections address common user problems and their solutions.
The volume might be configured as a private volume. A private volume is any volume for which the owner, primary group, or categories have no access permissions; only the volume's owner has permissions. In this case, only the owner has access to the volume.
To make the volume accessible to users, the owner should use the Permissions dialog box, available from the MacFile menu, to give the primary Group or Everyone categories at least one permission for the volume.
If the Macintosh-accessible volume is on a CDFS (CD-ROM File System)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.
Make sure that the correct CD-ROM is in the disk drive and that the drive door is closed.
Users are notified that their passwords have expired only if MS-UAM files are installed on their clients. If they are using the standard UAM for Apple, they are told only that their logon attempts failed and that they should try again later. For more information about installing the Macintosh client software, see the Teachtext Readme file in the MS-UAM volume.
To correct this problem, install the MS-UAM files on the user's client computer.
Assign the user a new password.
The user might have two accounts on separate domains, each with a different password. Have the user enter the domain name and then the account name in the Name box when they log on. For example, type:
Domain1\alex02A
Two physical AppleTalk networks have been given the same network numbers. The server that started first works fine. 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.
Use the Configure button, available when you choose Network to check the network numbers used for each physical network. When you find the duplicates, change one so that all physical networks are using 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 second server's requests to find a unique address.
Zones and network numbers are no longer in correspondence. When you change the name of a zone, you must shut down the routers that are directly connected to the networks in question for 10 to 15 minutes before restarting. This allows the other routers to discard old zone information. If you have not changed zone names recently, this situation could occur if an AppleTalk network number is duplicated on your AppleTalk network.
The user might not have the necessary permissions for the folder that contains the file or folder in question. The administrator or the owner of the folder can reset permissions to allow the user access to the folder.
A short name might already exist with the 8.3 file name; however, Macintosh users cannot see it. Give the 8.3 file name a different name.
Follow these steps:
If the cable system is not LocalTalk, ensure that the network connector is securely connected to its port. Click Network to review other network settings.
If they are, check the cables and connections at the server. Ensure that the server is operating properly. If the server is not the source of the problem, proceed to step 5.
If the missing server is on a different physical network in 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 and test 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.
Make sure AppleTalk is active in the Chooser. Click Network. Make sure the correct network port is selected.
There might be network problems, so check for the following:
If the problem persists, make sure all routers are configured properly.
When the computer running Windows 2000 Server was installed, there might have been insufficient disk space for the Microsoft UAM volume. Or the computer running Windows 2000 Server might have been installed without an NTFS partition.
You can create a 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 folder owner must log on to the server, connect to the Macintosh-accessible volume and select a view (such as View By, View By Name) from the View menu. The selected view then remains in effect.
The Finder occasionally cannot show the correct view of a folder. Having the folder owner log on and select the view resolves the situation.
The application that uses that type of data file might have been removed from the Macintosh.
If the file had no resource fork, use the Apple ResEdit tool to reset the file type and file creator of the file. Use this tool only if you are experienced in using it.
The Windows 2000 user does not have sufficient permissions to view the contents of the folder. Use the computer that is running Windows 2000 Server to make sure the user has Read permission, or the folder owner can use a Macintosh to give both the See Files and See Folders permissions. (A Windows 2000 user must have both these permissions to get the Windows 2000 Server Read permission.)
Only Macintosh clients that are running version 2.1 (or later) of the AppleTalk Filing Protocol can see server messages. Make sure the client has installed version 3.0 of AppleShare, which uses later versions of this protocol.
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 connected to the volume by using MS-UAM.
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 MS-UAM to log on to the server, you must mount the volume through the Chooser and then use the alias.