Copyright: Services for Macintosh
Citation: Services for Macintosh


Introduction to Services for Macintosh
Chapter 1	1 of 11

Introduction to Services for Macintosh

Microsoft® Windows NT™ Server Services for Macintosh® is a thoroughly integrated component of Microsoft Windows NT Server, making it possible for PC and Apple® Macintosh clients to share files and printers.

When you install Windows NT Server, you can choose to set up Services for Macintosh and other components, such as Microsoft Windows NT Server Remote Access Service, or you can set up these components later. Once Services for Macintosh is set up, a computer running Windows NT Server can also function as an AppleTalk® router. Routing capability is supported for AppleTalk Phase 2.

With Services for Macintosh, Macintoshes need only the Macintosh operating system software to function as clients; no additional software is required. You can, however, set up the optional user authentication module, which is software that provides a secure logon to the Windows NT Server.


Features in This Version
Introduction to Services for Macintosh	2 of 11

Features in This Version

Version 1.0 of LAN Manager Services for Macintosh made it possible for a LAN Manager server to share files and printers with Macintosh clients. This meant that both PC and Macintosh clients could share resources on the same network. This version of Services for Macintosh does that and more. Version 3.5 uses the capabilities of Windows NT Server, which include built-in networking services for multiple-domain networks of MS-DOS® – based, Windows™ – based, and OS/2® clients. Version 3.5 includes these features:

Increased performance because of better resource use.

Secured logon, which provides added protection from network "sniffers." (Sniffers can detect cleartext passwords.)

Easy-to-use graphical administration tools that are fully integrated into the Windows NT Server File Manager, Print Manager, and Server Manager.

Printing to non-PostScript® printers.

Increased number of clients that can be simultaneously connected to the server.

Compatibility with all the computers that can run Windows NT Server, including 80386, 80486, MIPS®, Pentium™, Alpha AXP™, and multiprocessor systems.

Support of AppleTalk Phase 2, which is available for routers and networking protocols. (AppleTalk Phase 1 is not supported in this version of Services for Macintosh.)

Moreover, a conversion utility is included to make it easier to upgrade from version 1.0 to version 3.5 of Services for Macintosh (version 3.1 requires no modifications). See the Windows NT Server System Guide for more information about migration.


What Services for Macintosh Can Do
Introduction to Services for Macintosh	3 of 11

What Services for Macintosh Can Do

Using Services for Macintosh on your network gives you many benefits-including the following:

File sharing

For example, some people in your department use Microsoft Excel for Windows. Others prefer using Microsoft Excel for Macintosh. With Services for Macintosh, all these users can work on the same spreadsheet files.

Printer sharing

For example, your small network has only one PostScript printer. With Services for Macintosh, both PC and Macintosh users can have access to the PostScript printer.

Or your network has two printers for PC clients and two printers for Macintosh clients. However, PC users get frustrated when the PC printers are busy and the Macintosh printers are not, and vice versa. With Services for Macintosh, all users can send print jobs to all printers, which means users have more choices for getting their work done. Moreover, you can control all of the print queues from a single location-your computer running Windows NT Server or Windows NT Workstation.

Simplified administration

For example, you have several Macintoshes that you'd like to put on the network. With Services for Macintosh, you don't need a Macintosh server; your computer running Windows NT Server can provide file sharing and file security for your Macintoshes and PCs. And by using your computer running Windows NT Server with Macintosh clients, you have only one list of users to maintain, instead of two (one on a computer running Windows NT Server and one on a Macintosh server).

AppleTalk routing support

For example, you want to connect an AppleTalk internet, a group of two or more AppleTalk physical networks. With Services for Macintosh, you can attach networks with Macintosh clients to create an AppleTalk internet.


File Sharing
Introduction to Services for Macintosh	4 of 11

What Services for Macintosh Can Do

File Sharing

Even though the MS-DOS, OS/2, and Windows NT file systems differ greatly from that of the Macintosh operating system, both PC clients and Macintosh clients can use the same files stored on the server. Services for Macintosh works in the background to make this possible.

For both Macintosh and PC users, files appear as they usually do: A PC user sees files located in a directory tree structure, and a Macintosh user sees files located in the familiar Macintosh folder structure.

Using Cross-Platform Applications on PCs and Macintoshes

For many applications that have versions for PCs and for Macintoshes, users of both versions can work on the same data file using Services for Macintosh. When Macintosh users view directories on the server containing these data files, they see the files represented by the appropriate icon.

For example, a person using a PC version of Microsoft Excel can create a spreadsheet file, and then store it on the server in a shared directory that also is configured as a Macintosh-accessible volume. A Macintosh user who opens that folder sees the file represented by the Macintosh icon that represents a Microsoft Excel spreadsheet. The Macintosh user can double-click the file icon, and Microsoft Excel for Macintosh starts and opens the file. The Macintosh user can modify the file, and then save it. When the PC user opens the file, the modified version of the file appears.

Services for Macintosh uses extension-type associations to display PC files with the correct icon when the Macintosh user is viewing them in the Finder. For example, the Macintosh user sees a Microsoft Excel for Macintosh document icon for a Microsoft Excel for Windows file (a *.XLS file).

Services for Macintosh comes with extension-type associations already defined for many applications. You can also add extension-type associations. For information and instructions on how to add more associations, see Chapter 5, "Configuring Services for Macintosh."


Printer Sharing
Introduction to Services for Macintosh	5 of 11

What Services for Macintosh Can Do

Printer Sharing

With Services for Macintosh, Macintosh and PC users can send print jobs to any printer attached to a computer running Windows NT Server, as well as to PostScript printers that register themselves as a LaserWriter on the AppleTalk network.

Services for Macintosh provides additional benefits for Macintosh users who use AppleTalk printers-it provides spooling. With spooling, Macintosh users can start other tasks as soon as they send a print job to the computer running Windows NT Server, where print jobs are stored until a printer becomes available. Without spooling, users must wait until the print job completes before doing anything else.


Simplified Administration
Introduction to Services for Macintosh	6 of 11

What Services for Macintosh Can Do

Simplified Administration

Simplified administration means that you have one set of users to maintain, instead of separate user accounts on the Macintosh server and the computer running Windows NT Server. It also means a consistent file-level security for PC and Macintosh users.

Services for Macintosh translates file permissions, which adds a level of security to your network. Services for Macintosh translates Windows NT file permissions and Macintosh-style permissions (referred to as access privileges by Macintosh users). A Macintosh user sets permissions according to the Macintosh scheme; Services for Macintosh translates these to Windows NT permissions. The reverse is also true: Windows NT permissions set by PC users are translated to Macintosh-style permissions for Macintosh users.

Administrators and Server Operators can both administer Services for Macintosh.


AppleTalk Routing Support
Introduction to Services for Macintosh	7 of 11

What Services for Macintosh Can Do

AppleTalk Routing Support

With Services for Macintosh, the computer running Windows NT Server can also provide routing and seed routing support. An AppleTalk router broadcasts routing information, such as network addresses, and keeps track of and directs data packets on AppleTalk networks. Seed routers perform these functions and also seed the physical networks on which they reside. Seeding a network means establishing and initializing the network address information for that network.

You can install an unlimited number of network adapters to a computer running Windows NT Server to add to an AppleTalk internet, which is a group of two or more physical networks connected by one or more routers.

For more information about routing and internets, see Chapter 3, "Planning Your AppleTalk Network."


System Requirements
Introduction to Services for Macintosh	8 of 11

System Requirements

To set up Services for Macintosh, you need a PC that is running Windows NT Server; to make full use of it, you need Macintosh clients. Requirements for each of these follow.

In addition, Services for Macintosh supports version 6.x (or later) of the LaserWriter printer driver, and AppleTalk Filing Protocol versions 2.0 and 2.1.


Requirements for Computers Running Windows NT Server
Introduction to Services for Macintosh	9 of 11

System Requirements

Requirements for Computers Running Windows NT Server

Setting up Services for Macintosh with Windows NT Server requires that your server meet specifications for both Windows NT Server as well as for Services for Macintosh.

For information about the Windows NT Server requirements, refer to the Windows NT Server System Guide.

Services for Macintosh requires these additions to the computer running Windows NT Server:

2 megabytes (MB) of extra hard disk space

A Windows NT file system (NTFS) partition in order to create directories (Macintosh-accessible volumes) that can be used by Macintosh clients


Requirements for Macintosh Clients
Introduction to Services for Macintosh	10 of 11

System Requirements

Requirements for Macintosh Clients

All Macintosh computers that can use AppleShare® (the Apple networking software for the Macintosh) can use Services for Macintosh. These include all Macintoshes except the Macintosh XL and Macintosh 128K. To use Services for Macintosh, the Macintosh must have version 6.0.7 or later (including System 7™ or higher) of the Macintosh operating system.

Services for Macintosh supports LocalTalk®, ethernet, token ring, and Fiber Distribution Data Interface (FDDI). Ethernet and token ring are commonly used when integrating Macintoshes into PC networks. For more information about these networks, see Chapter 3, "Planning Your AppleTalk Network."


Where to Go from Here
Introduction to Services for Macintosh	11 of 11

Where to Go from Here

For more conceptual information about Services for Macintosh, read Chapter 2, "How Services for Macintosh Works."

For instructions on setting up Services for Macintosh and a discussion of how to plan your Apple internet setup, see Part 2, "Setting Up and Configuring Services for Macintosh."

For step-by-step instructions that explain how to administer Services for Macintosh after it is set up and how to set up files and printers to be shared by Macintosh and PC users, see Part 3, "Administering Services for Macintosh."


How Services for Macintosh Works
Chapter 2	1 of 14

How Services for Macintosh Works

The two main services for SFM clients are File Server for Macintosh and the Print Server for Macintosh. The file server enables Macintosh users to access files stored on the computer running Windows NT Server. The print server enables Macintosh users to print to any printer connected to the computer running Windows NT Server, and to spool print jobs for AppleTalk printers (such as the LaserWriter).

This chapter explains how these services work. It also explains how Macintosh users gain access to the computer running Windows NT Server and how security applies to Macintosh users. For instructions on how to administer and manage these services and the other tools added to Server Manager and Control Panel, see Part 3, "Administering Services for Macintosh."


How Files Are Shared
How Services for Macintosh Works	2 of 14

How Files Are Shared

With Services for Macintosh, both PC users and Macintosh users can easily share files stored on the server. Shared files appear as expected to PC users and to Macintosh users. For example, when an MS-DOS user views these shared files, the filenames follow the MS-DOS standard naming convention, whether or not they were created that way by a Macintosh user. When a Macintosh user views the files, they appear as Macintosh files, like files on the Macintosh client itself or on Macintosh servers running AppleShare.


How Shared Files Appear to Users
How Services for Macintosh Works	3 of 14

How Files Are Shared

How Shared Files Appear to Users

On a computer running Services for Macintosh files are stored in shared directories or in Macintosh volumes. For a file to be accessible to PC clients, it must be in a shared directory (or in a subdirectory of a shared directory). Each server can have one or more shared directories. Each shared directory on a server is assigned a unique share name, which is sometimes referred to simply as a share.

With Services for Macintosh, Macintosh users cannot automatically gain access to all shares. To make a directory, and consequently its subdirectories (which may or may not be shared on the Windows NT system network) available to Macintosh users, the administrator must designate the directory as a Macintosh-accessible volume.

Note

Some PC users are familiar with the terms volume and volume labels as they relate to a hard disk partition. In this manual, however, a volume is either one of the following: a directory that has been designated as both a share and a Macintosh-accessible volume, which means that both types of clients can gain access to the files in the volume; or, a directory that is available only to Macintosh users on the network. (There is one exception to this convention-when CD-ROM, or Compact Disc Filing System (CDFS), volumes are mentioned.)

Within a directory that is both a share and a Macintosh-accessible volume, networked PC users see directories and files. In fact, this is what is actually stored on the server's hard disk. To Macintosh users the volume appears to contain Macintosh files and folders (the Macintosh equivalent of directories). When Macintosh users browse through the files available on the server, they see icons that represent each file and folder.

Macintosh files and folders can have Macintosh filenames, including long names and names containing spaces and other characters. They are not limited to the 8.3 naming convention of the file allocation table (FAT) file system used with the MS-DOS system and some OS/2 computers. The file server and the NTFS translate the names so that users can see them.


How Services for Macintosh Stores Files
How Services for Macintosh Works	4 of 14

How Files Are Shared

How Services for Macintosh Stores Files

Understanding how Macintosh files work is helpful in understanding how Services for Macintosh and Windows NT Server present files to both PC and Macintosh users.

Each Macintosh file has two parts, or forks, a data fork and a resource fork. The data fork contains the actual data of the file. The resource fork contains Macintosh operating system information about the file, such as code, menu, font, and icon definitions.

When a Macintosh file is shared on a computer running Services for Macintosh, the two forks are saved in a single NTFS file.


How Filenames Are Translated
How Services for Macintosh Works	5 of 14

How Files Are Shared

How Filenames Are Translated

There are two types of filename translations to consider when running Services for Macintosh:

How Macintosh filenames are maintained and presented to various users

How the longer NTFS names (more than 32 characters) are presented to the Macintosh user

When a Macintosh user creates a file or a folder on the server and gives it a name, Services for Macintosh checks it for illegal NTFS characters. If the filename contains illegal NTFS characters, File Server for Macintosh replaces the illegal characters. Otherwise, the original Macintosh name is the same as the NTFS name. Macintosh users see the name as it was created. Windows NT Server users will see the same name, with illegal characters replaced, if any.

Once the file server has determined what characters in a Macintosh filename are illegal NTFS characters and replaced them, Windows NT Server takes over the file translation process. Names that are too long for MS-DOS users to see them are shortened by truncating the name to six characters, plus a tilde (~) and a unique number. If the name has an extension, it is preserved. For more information about this process, refer to Appendix B, "How Filenames Are Translated," and the Windows NT Server System Guide.

For example, in a directory and volume called MACFILES, Windows NT Server and Macintosh users see a sample file as File Made by Macintosh. When MS-DOS users view the contents of the MACFILES directory, however, they see the short version of the filename-FILEMA~1. More examples follow:

Files Made By Macintosh (Old) is translated to the following:

FILEMA~2.

This prevents duplicate filenames if FILEMA~1 has already been created.

MARCHSALES.Sales Report.XLS is translated to the following:

MARCHS~1.XLS

Notice that the extension (.XLS) has been retained. The last period in a name is recognized by NTFS as signaling the extension.

Windows NT users creating long NTFS filenames (up to 256 characters) should name files with 31 characters (the Macintosh limit) or fewer so that Macintosh users can readily decipher the filenames. Long NTFS filenames are automatically translated to short names so that MS-DOS users can gain access to the files. If an NTFS name is longer than 31 characters, Macintosh users will also see the short name.

Here is a quick summary:

A file created using the FAT file naming convention displays as created to NTFS users and Macintosh users alike.

A file created using the 31-character limit of the Macintosh system displays as created to NTFS users. MS-DOS users see a short name.

A file created using the NTFS 256-character limit displays as created to Macintosh users if it is 31 characters or fewer. Otherwise, it displays in the shortened form to both MS-DOS and Macintosh users.

Note

Because MS-DOS users refer to files created by Macintosh users by the translated short names, you may want to instruct Macintosh users to give the FAT standard names (eight characters, and an optional period and three-character extension) to files and folders that will also be used by MS-DOS users. That way, MS-DOS users won't have to decipher short names that may or may not be self-explanatory. (For files that only Macintosh users or Windows NT clients will use, Macintosh users can freely use long filenames and folder names.)


Configuring Macintosh-Accessible Volumes
How Services for Macintosh Works	6 of 14

Configuring Macintosh-Accessible Volumes

With Windows NT Server, you can share directories on the server in any combination. For example, you can share a single directory twice with two different share names, and you can share a directory with one share name and then share a subdirectory of that directory with another share name.

However, different rules apply when you use Services for Macintosh to configure Macintosh-accessible volumes. You cannot configure two directories in the same directory tree as volumes.

This means that you cannot do the following when configuring Macintosh-accessible volumes:

Configure a single directory twice as two different volumes

Configure a directory as a volume if it exists anywhere in the directory tree under another directory configured as a volume

Configure a directory as a volume if one of its subdirectories, or any subdirectory of one of its subdirectories, is configured as a volume

For example, in the directory tree shown in the following illustration, if you configure the DATA1993 directory as a Macintosh-accessible volume, you cannot configure the JANUARY, FEBRUARY, or REPORTS directories as Macintosh-accessible volumes.

The only other directory that can be designated a volume is Data 1992.

All Macintosh-accessible volumes must be on an NTFS partition or a CDFS volume. (The CDFS volumes are, by design, read-only.) The number of volumes that can be seen by the users is determined by the length of the volume names, which all must fit in a buffer in order to be displayed. (The size of the buffer is determined by an underlying AppleTalk protocol.) Volume names can have a maximum of 27 characters. Try to strike a balance between clearly naming volumes so that users can identify them easily and keeping the names short so that all of the volume names can be displayed.

Note

If you need to know the number of Macintosh-accessible volume names that can be displayed, use this formula:

N * (M+2) <=4624

where N is the number of volumes, and M is the average length of the names in bytes.


Printing
How Services for Macintosh Works	7 of 14

Configuring Macintosh-Accessible Volumes

Printing

With Services for Macintosh, users gain three major printing benefits:

Macintosh users can print PostScript jobs to non-PostScript printers directly connected to the computer running Windows NT Server. To the Macintosh user, these printers appear like the standard LaserWriter.

PC users can send print jobs to PostScript printers on the AppleTalk network. PC users can also check print jobs from their clients.

Macintosh and PC print jobs are spooled before they go to the printer. So, Macintosh and PC users can both send jobs to the printer and then continue working at their computers. This means that users don't have to wait for their jobs to print before using their computers to do other tasks or wait for a printer to be available.


Capturing AppleTalk Printers
How Services for Macintosh Works	8 of 14

Configuring Macintosh-Accessible Volumes

Capturing AppleTalk Printers

When you set up a printer on the AppleTalk network to be used with Services for Macintosh, you can specify whether Services for Macintosh will capture the printer. This means that the printer will not accept print jobs from any source other than the print server, thus giving Windows NT Server administrators complete control over the printer.

In general, it is best to always capture a printer, unless a source other than the print server prints jobs on the printer. For example, you would not capture printers if you were using Apple LaserShare, which provides spooled printing for Macintosh clients, or using a minicomputer that sends print jobs from minicomputer users to the printer.

If a printer won't be used by anything other than Windows NT Server, Microsoft recommends that you capture it. Doing so ensures that users don't accidentally bypass the print server and send print jobs directly to the printer or reset the printer, which may cause spooler problems. You'll also avoid "LaserPrep Wars." For more information about how to avoid LaserPrep Wars, see the next section.

If a printer is not captured and both Windows NT Server and another source send jobs to the printer, no jobs will be interrupted; however, while the printer is printing a job from one source, it will appear busy to the other sources.

For information about how to capture AppleTalk printers, see Part 3, "Administering Services for Macintosh."


Avoiding LaserPrep Wars
How Services for Macintosh Works	9 of 14

Configuring Macintosh-Accessible Volumes

Avoiding LaserPrep Wars

With some AppleTalk networks, a condition known as "LaserPrep Wars" causes slow printing performance. Services for Macintosh solves this problem.

LaserPrep Wars occur when a network has Macintosh clients that use two or more versions of Chooser Packs, which include a PostScript preparation file (also called a LaserPrep file) and a PostScript driver. A printer can use only one version of the LaserPrep file at a time. When a Macintosh user sends a print job to the printer, the Macintosh checks for the printer's version of the LaserPrep file; if the printer currently has a different version than the Macintosh client uses, the Macintosh client sends its version of the LaserPrep file along with the print job, and it instructs the printer to load that file as the printer's resident LaserPrep file. Because Macintoshes with different LaserPrep file versions send print jobs to a printer, different versions of the LaserPrep file are loaded and unloaded on the printer.

For example, suppose a Macintosh user whose client uses Chooser Pack version 6.0 sends a document to the printer. The LaserPrep version 6.0 file is made resident on the printer. Then, if the next document sent to the printer comes from a client using Chooser Pack version 7.0, the printer must reset, load LaserPrep 7.0, and print a new startup page before printing the document.

Performance problems result because the printer has to load and unload versions of the LaserPrep file, and then print a startup page each time it makes a different LaserPrep file resident. This can also reduce the life cycle of the printer.

Services for Macintosh solves the LaserPrep Wars problem by sending the LaserPrep file with each job. Although the print server must send a LaserPrep file to the printer with every print job, overall performance is improved because the printer never has to spend time making a LaserPrep resident or printing a startup page.

Note that for printers on an AppleTalk network, LaserPrep Wars are guaranteed to be avoided only if the printer is captured. If the printer is not captured, users who send print jobs directly to the printer, bypassing the print server, can initiate LaserPrep Wars.

LaserPrep Wars are always prevented when printers are attached directly to a computer running Windows NT Server that is set up with Services for Macintosh.


Network Security
How Services for Macintosh Works	10 of 14

Network Security

With Windows NT Server and Services for Macintosh, network security is enforced for Macintosh users in the same way it is enforced for PC users. Services for Macintosh translates user identification, authentication (passwords), and permissions so that the integrity of the server is maintained regardless of the type of client used. The following sections explain how network security applies to Macintosh users and cover the following topics:

Windows NT Server user account restrictions for Macintosh users

Password protection, including guest logons from Macintosh clients

Translation of Windows NT Server file permissions to Macintosh-style permissions

Macintosh-accessible volume passwords


Windows NT Server Accounts for Macintosh Clients
How Services for Macintosh Works	11 of 14

Network Security

Windows NT Server Accounts for Macintosh Clients

Services for Macintosh uses the same user accounts database as Windows NT Server. Therefore, if you already have Windows NT Server accounts created for the people who will be using Macintoshes on the network, you don't need to create additional accounts. You must create accounts only for users who don't already have accounts on the computer running Windows NT Server and Services for Macintosh.

One aspect of Windows NT Server user accounts, the user's primary group, applies only to Services for Macintosh. The user's primary group is the group the user works with most, and it should be the group with which the user has the most resource needs in common. When a user creates a folder on a server, the user becomes the owner. The owner's primary group is set as the group associated with the folder. The administrator or owner can change the group associated with the folder.


Passwords
How Services for Macintosh Works	12 of 14

Network Security

Passwords

Macintosh users are logged on to a computer running Windows NT Server in one of three possible scenarios:

As a guest

As a user with a cleartext password

As a user with an encrypted password

Guest Logons

Using Services for Macintosh, you can set up guest logons, which allow users without accounts to log on to the server using a Macintosh. You can specify what access to resources guest logon users have; administrators typically grant guest users fewer permissions than users who have accounts on the server. If the guest logon option is enabled, the server always approves the logon request without requiring a password.

For information about how to set up guest logons, see Chapter 8, "Managing the File Server."

Cleartext Passwords

Cleartext password protection is part of the AppleShare client software on Macintoshes. It provides less security than encrypted password protection because the passwords are sent over computer lines and can be detected by "sniffers," which are network monitors that can look for passwords. Moreover, the AppleShare passwords can be no longer than eight characters. This method of protection is offered for Macintosh users who use the standard AppleShare client software or System 7 File Sharing.

Encrypted Passwords

An encrypted, or encoded, password is more secure than the cleartext password type of security. Windows NT Server encodes passwords and stores them so that they cannot be directly stolen from the client itself. Encrypted passwords can be as long as 14 characters. Services for Macintosh offers encrypted passwords to Macintosh clients.

For more information about security, see Part 3, "Administering Services for Macintosh," and the Windows NT Server System Guide.


Permissions
How Services for Macintosh Works	13 of 14

Network Security

Permissions

Access to network files and directories is controlled with permissions. With the Windows NT security system, you specify which users can use which shares, directories, and files, and how they can use those files. The Macintosh-style permissions differ in that they can be set for folders (directories) only-not files.

The set of permissions available for PC users differs from the set of permissions available for the Macintosh. Services for Macintosh automatically translates them so that permissions are enforced for both PC and Macintosh users.

The Windows NT Server Administrator account always has full permissions on Services for Macintosh volumes.

Types of Permissions

PC users and administrators use Windows NT permissions. Macintosh users set Macintosh-style permissions on the folders they create.

In Windows NT, new files and new subdirectories inherit permissions from the directory in which they are created.

Macintosh files effectively inherit the permissions set on folders. Even though the Macintosh doesn't have file permissions, any Windows NT permission specified for a file will be recognized by the File Server for Macintosh, even though the Macintosh user won't see any indication in the Finder that these permissions exist. The Macintosh has the following four types of permissions for a folder:

See Files, which lets a user see what files are in the folder and read those files

See Folders, which lets a user see what folders are contained in the folder

Make Changes, which lets a user modify the contents of files in the folder, rename files, move files, create new files, and delete existing files

Cannot Move, Rename, Or Delete, which prohibits these actions on a folder

A Macintosh user cannot give these permissions to multiple users and groups. Instead, permissions can be assigned to three categories of user, shown in the following screen:

Owner, the user who created the folder.

User/Group, similar to the Windows NT Server group, associated with the folder. Every folder on a server can have one group associated with it at any one time. The group can be a special group like users or administrators, or it can be any other group on the server.

Everyone, which includes all other users of the server, including user accounts with guest access.

The Macintosh security scheme is based on the idea that every folder on a server falls into one of three types: private information, accessible only by a single person, the owner of the folder; group information, accessible by a single workgroup; and public information, accessible by everyone.

For example, there can be a folder containing information that all members of a certain group should see, but that only one person can change. The person allowed to change the information should be the owner of the folder and should have See Files, See Folders, and Make Changes permissions. The workgroup that uses the folder should be the group associated with the folder and should have only See Files and See Folders permissions. Because no one else needs to see the folder's contents, the Everyone category should not be selected.

Although a folder's owner will often be a member of the group associated with the folder, this is not required.

With both Macintosh-style and Windows NT Server-style permissions, users' access to folders can be defined differently for each directory and subdirectory within a directory tree. For example, you could give a user See Files, See Folders, and Make Changes permissions for one folder, only the See Files permission for a subfolder of that folder, and no permissions at all for another subfolder.

How File-Level Permissions Are Handled

With Windows NT Server, PC users can assign permissions separately for each file within a directory. The Macintosh, however, does not support file-level permissions. When a file has file-level permissions, those permissions apply to Macintosh users only if the permissions are more restrictive than those assigned for the directory that contains the file.

For example, if a Macintosh user has See Files, See Folders, and Make Changes permissions for a directory (which appears as a folder), the user can read and make changes to files in the directory. However, if that user has only Read permission for any particular file in that directory, the user can only read that file. Because of the Read file-level permission, the user cannot make changes to the file.

Translating Permissions

Services for Macintosh translates permissions so that those set by a PC user are translated into the equivalent Macintosh permissions, and vice versa. When a PC user sets permissions for a directory, or when a Macintosh user sets permissions for a folder, permissions are translated according to the following table.

Directory and File Permissions Translation

Windows NT permissions	Macintosh permissions
Read	See Files, See Folders (or both)
Write, Delete	Make Changes
The following guidelines apply:

When a PC user sets Read permissions on a directory or file, users will have both See Files and See Folders permissions while using a Macintosh.

When a PC user sets Write and Delete permissions on a directory or file, users will have the Make Changes permission while using a Macintosh.

When a Macintosh user sets See Files or See Folders (or both) permissions, the user will have Read permissions when using a PC.

When a Macintosh user sets the Make Changes permission, the user will have the Write and Delete permissions when using a PC.

Note

Permissions set within the Macintosh behave differently than those set from within Windows NT Server, including Macintosh-style permissions. From the Macintosh, a right assigned to everyone overrides any more restrictive rights set on the owner or a group. From Windows NT, permissions assigned to everyone do not override permissions set on the owner or group.

Setting Permissions from a Macintosh or a PC

A folder's owner can set permissions for the folder. Both the folder's owner and the server administrators can also use a PC to set Windows NT permissions for folders on the server. The folder's owner can set permissions for the directory (folder) from a PC because the owner of every directory (folder) has the Windows NT P (Change Permission) permission for that folder.

Administrators can also use File Manager, after Services for Macintosh is started, to set Macintosh-style permissions for any directory within a Macintosh-accessible volume, including the volume root directory.


Volume Passwords
How Services for Macintosh Works	14 of 14

Network Security

Volume Passwords

Services for Macintosh provides an extra level of security through Macintosh-accessible volume passwords. A volume password is a password you assign to a Macintosh-accessible volume when configuring it. Any Macintosh user who wants to use the volume must type the volume password. PC users do not need to know the volume password to access the directory that corresponds to the Macintosh-accessible volume. Volume passwords are case-sensitive.

Volume passwords are optional; when you create a new Macintosh-accessible volume, the default is to have no volume password.

Note

Because of a constraint with the System 6 and 7 Finder, you cannot automatically mount a volume with a volume password at startup or by double-clicking an alias. You also cannot automatically mount a volume if the user originally connected to the volume with Microsoft Authentication.


Planning Your AppleTalk Network
Chapter 3	1 of 15

Planning Your AppleTalk Network

When you plan a network that includes both PCs and Macintoshes, a major consideration is how to plan the physical setup of the network, including the network media. Network media are different types of local area networks, each of which uses different cabling, topology, and network cards. Examples of network media are ethernet, token ring, LocalTalk, and FDDI. If your network has two or more media types, you must find a way to make them work together.

The basic concepts of AppleTalk networking are important to master. Because many of these concepts are not involved in PC networking, you may not be familiar with them. Before you set up Services for Macintosh on a computer running Windows NT Server, it's a good idea to create a plan for your network. For more information about AppleTalk networks, see "AppleTalk Networks" and "Planning Your AppleTalk Internet," later in this chapter. Also refer to the Windows NT Server Concepts and Planning Guidefor information on planning a network.


Planning the Physical Setup
Planning Your AppleTalk Network	2 of 15

Planning the Physical Setup

As you plan how to physically connect your PCs and Macintoshes, the first thing to consider is network media. Each network media type has its own method of cabling and network topology, and each requires different network hardware.

Windows NT Server supports four types of media:

Ethernet

Token ring

LocalTalk

FDDI

Ethernet and token ring are common network media in PC networking. LocalTalk is used in AppleTalk networking. FDDI, although not as common yet, is based on token ring and designed to be used with fiber-optic cabling. Every Macintosh includes hardware and software that enables it to be a client on a LocalTalk network.

Media Speeds

To set up a computer running Windows NT Server to communicate with both PCs and Macintoshes, you may need to install two (or more) network cards in the server: one card (such as ethernet) for communication with the PCs, and another card (such as LocalTalk) for communication with Macintoshes. If the Macintoshes are also using ethernet (or EtherTalk®) cards, you'll only need one network card.

The following section describes how to connect your network.


Example
Planning Your AppleTalk Network	3 of 15

Planning the Physical Setup

Example

Suppose your server and PC clients use ethernet, and your Macintoshes aren't currently attached to any network; they have only their built-in LocalTalk hardware and software. To enable the computers running Windows NT Server and the Macintoshes to communicate, choose one of these methods:

Install a LocalTalk network adapter card on the server, in addition to the ethernet card already installed.

Install ethernet cards on each Macintosh.

Install an ethernet/LocalTalk router.

Solution 1: Install a LocalTalk Card on the Computer Running Windows NT Server

You can install a LocalTalk network adapter card on the computer running Windows NT Server, in addition to an ethernet card. You can then set up the Macintoshes on a LocalTalk network attached to the server's new LocalTalk card. The server will communicate with the PC clients via ethernet and will communicate with the Macintoshes via LocalTalk.

The following illustration shows such a network.

This solution is fairly inexpensive because you need to buy only one additional network adapter card. However, LocalTalk is not as fast as ethernet; consequently, network performance is not as good as it would be if all the clients used ethernet. Because you can have only a limited number of Macintoshes on a LocalTalk network, this solution may not be practical if your network has a large number of Macintoshes.

Solution 2: Install Ethernet Cards on the Macintoshes

You can install ethernet network adapter cards on all the Macintoshes and attach them to your existing ethernet network. The server will use its existing ethernet card to communicate with both PC and Macintosh clients, which can all be attached to a single physical ethernet network. The following illustration shows a network using this solution.

Solution 3: Install an Ethernet/LocalTalk Router

You can install an ethernet/LocalTalk router, which translates data on the network between the two media. (These routers are made by several companies.) Windows NT Server running Services for Macintosh can also act as a router between ethernet and LocalTalk. Windows NT Server, however, must have both an ethernet and LocalTalk card installed in it. (See the Note at the end of this section for more information on using the computer running Windows NT Server as a router.)

By using an ethernet/LocalTalk router, the server can still use its ethernet card, and you can put the Macintosh clients on a LocalTalk network and attach the router to both the ethernet and LocalTalk networks. All data transferred between the server and the Macintoshes passes through the router. To the server, all the Macintoshes appear to be on the ethernet network. The following illustration shows a network that uses an ethernet/LocalTalk router.

To use this ethernet/LocalTalk router, you must be able to bind the AppleTalk protocol on the server to an ethernet card on the server.

This solution is low-cost and useful if you want to make printers on the ethernet available to Macintosh clients. However, performance is degraded by using a router. A network with LocalTalk clients is not as fast as an all-ethernet network.

Note

Because a computer running Windows NT Server can function as a router, it can also function as an ethernet/LocalTalk router, as long as it has both an ethernet network adapter card and a LocalTalk card. To connect one physical network of Macintoshes to several servers, you can install a LocalTalk card on one server, and that server can function as a router, enabling the Macintoshes to reach the other servers on the ethernet network.


Advanced Examples
Planning Your AppleTalk Network	4 of 15

Planning the Physical Setup

Advanced Examples

Depending on which clients you have, the issues you face when deciding how to connect them can be more complex than those discussed previously. For example:

Windows NT Server uses ethernet, but some of your Macintoshes use ethernet and others use LocalTalk.

Solution: You can install a LocalTalk card on the computer running Windows NT Server to communicate with the Macintoshes that use LocalTalk, or you can install ethernet cards on all the Macintoshes, or you can use an ethernet/LocalTalk router.

Windows NT Server uses ethernet, but some of your Macintoshes use ethernet and others use LocalTalk. You also have some Macintoshes that have token-ring network cards.

Solution: Install a token-ring network card on the computer running Windows NT Server to communicate with these Macintoshes, in addition to whatever solution you choose in the previous example for the Macintoshes that use ethernet and LocalTalk.

These examples can be used to install FDDI rings as well.


AppleTalk Networks
Planning Your AppleTalk Network	5 of 15

AppleTalk Networks

Because AppleTalk networks differ from PC networks, you must consider some special concepts and issues when you set up an AppleTalk network.

The first concept you need to understand is the internet. (Note that this is a different concept than the Transport Control Protocol/Internet Protocol [TCP/IP] Internet.) Most large AppleTalk networks are not single physical networks, in which all computers are attached to the same network cabling system. Instead, they are internets, which are multiple smaller physical networks connected by routers. Routers maintain a map of the physical networks on the internet and forward data received from one physical network to other physical networks. Routers are necessary so that computers on different physical networks can communicate with one another. They also reduce network traffic on the internet by isolating the physical networks. In other words, routers only send data that is usable by a network.

Some routers on the network are seed routers. A seed router initializes and broadcasts routing information about one or more physical networks. This information tells routers where to send each packet of data. Each physical network must have one or more seed routers that broadcast the routing information for that network.

Not all routers must be seed routers. Routers that are not seed routers maintain a map of the physical networks on the internet and forward data to the correct physical network. Seed routers perform these functions too, but they also initialize the routing information, such as network numbers and zone lists, for one or more physical network. (See "Determining Seed Router Placement on a Network" later in this chapter.)

A computer running Windows NT Server with Services for Macintosh can function as a seed router or as a nonseed router. If a seed router, it must be the first server you start so that it can initialize the other routers with network information. If a nonseed router, it cannot be started until a seed router has initialized all ports. You can also use dedicated hardware routers (such as those made by Cayman Systems®, Shiva®, Solana, Hayes®, and others) on your network.


Phase 2 AppleTalk Networks
Planning Your AppleTalk Network	6 of 15

AppleTalk Networks

Phase 2 AppleTalk Networks

There are two types of AppleTalk networks: Phase 1 and Phase 2. You must use Phase 2 to run Windows NT Server and Services for Macintosh. (For more information, see Chapter 1, "Introduction to Services for Macintosh.")

Phase 2 includes these features:

Supported media types

Token ring, LocalTalk, ethernet, FDDI.

Network numbers

LocalTalk networks have a single network number; EtherTalk and TokenTalk® networks can be assigned a network range, allowing for more nodes on the network.

AppleTalk zones

Each LocalTalk network must be in a single zone; each EtherTalk and TokenTalk network can have multiple zones, and individual nodes on a network can be configured to be in any one of the network's associated zones.

Number of nodes per network

A node is any type of device on the network. Each client, printer, server, and router is a node on an AppleTalk network.

LocalTalk networks can have as many as 254 nodes (but are actually limited to 32 or fewer nodes because of media capacity); EtherTalk and TokenTalk networks can have as many as 253 nodes for every number in the network range, for a maximum of 16.5 million nodes. (But don't specify this many nodes; network media cannot physically accommodate this large number of nodes.)

Note

The terms ethernet and token ring are used in this book to discuss network media. When discussing the implementation of an AppleTalk network on ethernet or token ring, the respective Apple product names - EtherTalk and TokenTalk - are used. For more information, refer to the Glossary, later in this manual, or to an AppleTalk manual.


Routing Information
Planning Your AppleTalk Network	7 of 15

AppleTalk Networks

Routing Information

Routing information includes:

A network number or network range associated with each physical network.

The zone name or zone list associated with each physical network.

The default zone for the network (if the network has multiple zones).

The network number or network range is the address or range of addresses assigned to the network. By keeping track of network numbers and network ranges, routers can send incoming data to the correct physical network.

A network number is a unique number that identifies a particular AppleTalk physical network. A network number can be any number from 1 through 65,279.

LocalTalk networks can have only a single network number; EtherTalk, TokenTalk and FDDI networks can have network ranges.

A zone is a logical grouping, which simplifies browsing the network for resources, such as servers and printers. It is similar to a domain in Windows NT Server networking. (The only difference between the two is that domains define user accounts, whereas zones do not.) In LocalTalk networks, each physical network can be associated with only one zone. However, for EtherTalk, TokenTalk, or FDDI, you have more flexibility in assigning zones. Each EtherTalk, TokenTalk, or FDDI network can have one or more zones associated with it, and each zone can include servers and printers on one or more physical networks. This way, you can group servers and printers logically into zones so users can easily locate and access the servers and printers, no matter what physical networks they are on.

Each Macintosh client on the network is assigned to a single zone. However, each client can access servers and printers in any zone on the network. Zones make accessing network resources simpler for users. When users use the Chooser to view the network, they see only the resources in a single zone at a time, preventing them from having to navigate through huge numbers of resources on large networks to find the resources that they need. You can put the clients, servers, and printers used by a single group into a single zone, so users will see only the resources they typically use but will still be able to access resources in other zones when required.

A zone list includes all the zones associated with that network. One of these zones is the network's default zone, to which the Macintosh clients on that network are assigned by default. Users can configure the client to be in a different zone, however.


Working with Seed Routers
Planning Your AppleTalk Network	8 of 15

AppleTalk Networks

Working with Seed Routers

When you set up Services for Macintosh, you decide separately for each network to which the computer running Windows NT Server is attached whether it will seed that network. For example, a computer running Windows NT Server attached to three physical AppleTalk networks might serve as a seed router on two of the networks but not on the third.

If you specify that a server will not seed a network (that is, it's a nonseed router), the port will be seeded by another AppleTalk router attached to it.

When you install the server, you need to specify whether it will seed each physical network to which it is attached. For networks that the server will seed, specify the routing information. The computer running Windows NT Server will then function as a seed router, seeding the routing information that you provided.

Using Multiple Seed Routers on a Network

To make your network more reliable in case of system crashes and power outages, you can install multiple seed routers on the same physical network.

When you install multiple seed routers for a particular network, all the seed routers must seed the same information for that network. When the network starts, the first seed router that starts on the network becomes the actual seed router.

When a network starts, if the first seed router to start has different routing information than seed routers that start later, the information established by the first seed router is used. If the seed routers that start subsequently with different information are servers running Windows NT Server, their conflicting information is ignored, and an event is written to Windows NT Server Event Viewer. Other types of routers may behave differently.


Planning Your AppleTalk Internet
Planning Your AppleTalk Network	9 of 15

Planning Your AppleTalk Internet

When you plan your AppleTalk internet, follow these guidelines:

Determine which router will seed each network.

Decide how to assign network numbers and network ranges.

Decide how to assign zones.

Create a router plan and router record.

These guidelines are explained in the following sections.


Determining Seed Router Placement on a Network
Planning Your AppleTalk Network	10 of 15

Planning Your AppleTalk Internet

Determining Seed Router Placement on a Network

When planning a large internet, it is helpful to make a diagram of your AppleTalk internet, including the physical network layout and connecting points in the diagram. The following illustration shows an example of an AppleTalk internet. It includes clients only for visual clarity; you only need to diagram routers and servers. Diagramming the internet will help you determine which router will seed each physical network.

Example

Suppose you have an existing network with six computers running Windows NT Server (as shown in the previous illustration). You must determine which server will seed each network. Refer to the illustration as you read the following plan.

The seed router for ethernet network #1 must be Server 1, Server 2, Server 3, or Server 4.

The seed router for ethernet network #2 must be Server 4 or Server 5.

The seed router for ethernet network #3 must be Server 5 or Server 6.

The seed router for LocalTalk network #2 must be Server 5, because the router on Server 5 is the only one available for this network. Similarly, Server 3 must seed LocalTalk network #1.


Assigning Network Numbers and Network Ranges
Planning Your AppleTalk Network	11 of 15

Planning Your AppleTalk Internet

Assigning Network Numbers and Network Ranges

Follow these guidelines when you decide how to assign network numbers and network ranges:

Use network numbers that leave room for expansion.

For example, LocalTalk #2 in the Router Seeding Plan Example table, later in this chapter, starts at 1280, leaving plenty of growth for LocalTalk #1, which starts at 1024.

For a LocalTalk network, you can assign only a single network number. For each ethernet or token-ring network, you can assign a network range.

Network numbers are essentially arbitrary. The important thing is for them to be unique and to not overlap (if in a range) with other ranges.

If you plan to expand any LocalTalk networks for which you can currently assign only a network number, leave a range of unused numbers above the number you assign. You can use these numbers when you expand your network.

Base your network ranges on the number of nodes you expect to have in the future on each network.

Base the extent of a network range on the number of AppleTalk nodes expected on the physical network. The total number of possible AppleTalk nodes is 253 times the number of network numbers in the range. For example, a network range of 101 through 103 permits 759 nodes (3 * 253 = 759); a network range of 120 to 129 permits 2530 nodes (10 * 253 = 2530) on a network. Leave room for more nodes than you currently have connected.


Assigning Zones
Planning Your AppleTalk Network	12 of 15

Planning Your AppleTalk Internet

Assigning Zones

AppleTalk zones are identified by zone names. Follow these guidelines when you decide how to assign zone names:

Assign a single zone name to each physical LocalTalk network. You can assign one or more zone names to each ethernet and token-ring network. An asterisk (*) cannot be a zone name.

For each ethernet and token-ring network, decide which zone will be the default zone.

The number of zones your internet has depends on the size of the internet you are planning. If your internet is small, a single zone can be adequate. But if you have a single Phase 2 ethernet or token-ring network that spans a large geographic area or contains large numbers of AppleTalk devices (such as printers and servers), use multiple zones to make it easier for users to find the devices they need.


Making a Router Plan
Planning Your AppleTalk Network	13 of 15

Planning Your AppleTalk Internet

Making a Router Plan

After you have diagrammed your network, make a router plan that shows the location and type of each seed router for the network. The following seed router examples are based on the preceding network diagram.

To make a router plan, determine:

The expected number of AppleTalk devices on present and projected ethernet and token-ring networks.

The quantity of network numbers sufficient to satisfy capacity requirements (as many as
n * 253 devices can be supported, where n is the number of network numbers in the range)

Router Seeding Plan Example

Cable ID	Network range	Zone list	Seed device(s)1
Ethernet #1	16-25	Finance2 Accounts Payable Accounts Receivable	Server 1 Server 3
Ethernet #2	32-37	Marketing2 Marketing Exec	Server 5
Ethernet #3	768	Engineering2	Server 6
LocalTalk #1	1024	Finance	Server 3
LocalTalk #2	1280	Marketing	Server 5
1	Seed device information can indicate the server name, the type of dedicated hardware router, or the location, depending on your needs.

2	Indicates the network's default zone.


Creating a Router Record
Planning Your AppleTalk Network	14 of 15

Planning Your AppleTalk Internet

Creating a Router Record

To keep information about your internet for maintenance purposes, create a record from your router seeding plan. Include the following information:

Router location

Physical location

If the router is a computer running Windows NT Server with Services for Macintosh, record the computer name of the server

Router type and version

The physical networks connected to the router, with the following information for each:

Cabling identification

Network media type

Network number(s)

Zone name(s)

Default zone

Whether this router is a seed router for the networks attached to it

Note

Third-party AppleTalk network management products for Macintosh clients can make internet administration easier. For example, the Apple Inter-Poll® network administrator's utility lets you see all AppleTalk devices (including routers) on an internet in real time, observe every Services for Macintosh server, and sort devices by network number, device name, node, and so on. If you install the Apple Responder (part of the Inter-Poll product) on Macintosh clients running System 6.x, you can also view those clients with Inter-Poll. (The Responder is built into System 7.) Farallon™ Computing, Sonic System, and Caravelle also provide network management utilities that track network activity.


Preparing to Set Up Services for Macintosh
Planning Your AppleTalk Network	15 of 15

Preparing to Set Up Services for Macintosh

Before you set up Services for Macintosh on any computer running Windows NT Server, take the router seeding plans and diagrams you have made, and prepare the information you will need when you install each server. For each server, create a table that has the following information:

The computer name and physical location for the server.

For each network attached to the server, record its network ID, network adapter card type, and whether the server will serve as a seed router for the network.

If the server will be a seed router for any network, record the routing information that it will seed for each network, including the network number or network range, the zone name or zone list, and the default zone.

If the server is on an ethernet or token-ring network that has multiple zones, record the zone (or zones) where you want Windows NT Server to appear to Macintosh users.

The following tables show examples, based on the preceding diagram and examples.

Server Planning Example

Windows NT Server computer name: \\server5
Physical location: Room 1350
Cable ID	Adapter	Seed	Routing information	Appears in zone
Ethernet #2	EtherLink® II	Yes	512-517 Marketing¹	Marketing
LocalTalk #2	COPS² LTI ISA	Yes	1280 Marketing¹	Marketing
Windows NT Server computer name: \\server6
Physical location: Engineering Lab
Cable ID	Adapter	Seed	Routing information	Appears in zone
Ethernet #3	EtherLink® II	Yes	768 Engineering¹	Engineering
¹ Indicates the network's default zone. ² Same as the DayStar Digital card.


Setting Up Services for Macintosh
Chapter 4	1 of 9

Setting Up Services for Macintosh

This chapter gives an overview of what happens when you set up Services for Macintosh on a computer running Windows NT Server. It explains how to set up Services for Macintosh directly from the distribution disk and over the network, as well as how to remove it from the server. This chapter also includes instructions for setting up the encrypted password module, also called user authentication module (UAM), that runs on the Macintosh clients connected to the network.

Before you set up Services for Macintosh, become familiar with concepts such as AppleTalk internets, AppleTalk Phase 2, routing and seed routing, network numbers and ranges, and zones. Also, make a plan for your AppleTalk internet. If you aren't familiar with AppleTalk networking concepts, or if you don't yet have an internet plan, read Chapter 3, "Planning Your AppleTalk Network," before proceeding.


Overview
Setting Up Services for Macintosh	2 of 9

Overview

You can set up Services for Macintosh at the same time you install Windows NT Server, or you can set it up later. Either way, you set up, or enable, Services for Macintosh using the Network icon in Control Panel and the Windows NT Server distribution disk.

If you remove Services for Macintosh and later decide to set it up again, you must use the Windows NT Server distribution disk and installation program to copy the required Services for Macintosh files to the server. Removing Services for Macintosh deletes the distribution files (except Macintosh-accessible volumes) instead of disabling them.

Note

You must be an administrator or have administrator permissions to use the Network icon in Control Panel, which is used to set up Services for Macintosh.

When you set up Services for Macintosh, the AppleTalk Protocol, File Server for Macintosh, and Print Server for Macintosh are automatically started, or enabled. An explanation for each of these follows.

The AppleTalk Protocol is the layer of AppleTalk Phase 2 protocols that delivers data to its destination on the network. The AppleTalk Protocol can be configured through the Network icon in Control Panel. Configuration instructions for the AppleTalk Protocol appear in Chapter 5, "Configuring Services for Macintosh."

File Server for Macintosh, also called MacFile, allows you to designate a directory as a Macintosh-accessible volume, ensures Macintosh filenames are legal NTFS names, and handles permissions. When set up, File Server for Macintosh commands appear in Windows NT Server File Manager and Server Manager under the MacFile menu. Instructions for configuring it appear in Chapter 5, "Configuring Services for Macintosh."

Print Server for Macintosh, also called MacPrint, allows all network users to send print jobs to a spooler on the Windows NT Server and continue working, rather than waiting for their print jobs to complete. Windows-based users can also review the print jobs in Print Manager. See Chapter 6, "Setting Up Printers," for more information.

In addition, setting up Services for Macintosh creates an icon in Control Panel, which gives you the same server administration capabilities as the MacFile menu, excluding volume management, for the local computer.


Setting Up from Windows NT Server
Setting Up Services for Macintosh	3 of 9

Setting Up from Windows NT Server

Once Windows NT Server is installed, you use the Network icon in Control Panel and the Windows NT Server distribution disk to set up Services for Macintosh.

To set up Services for Macintosh

1.	From Control Panel, which is in the Main group window, choose Network.

The Network Settings dialog box appears.

2.	Choose the Add Software button.

The Add Network Software dialog box appears.

3.	From the Network Software list, select Services for Macintosh.

4.	Choose the Continue button.

The Windows NT Setup dialog box appears.

5.	Type the path to the Windows NT Server distribution files.

Setup copies all Services for Macintosh files and sets up the Registry.

6.	In the Network Settings dialog box, choose OK.

The AppleTalk Protocol Configuration dialog box appears, where you can select a new zone, different network, or enable AppleTalk routing, if you want. Configure this as you want.

7.	Choose the OK button, or choose Cancel if you don't want to change the configuration.

8.	The Network Setting Change dialog box appears. Choose the Restart Now Button to restart the server. You must restart your computer for the changes to take effect.


Setting Up from the Network
Setting Up Services for Macintosh	4 of 9

Setting Up from Windows NT Server

Setting Up from the Network

Setting up over the network can save time if you need to set up Services for Macintosh on more than one computer running Windows NT Server. Setting up Services for Macintosh over the network is done just as you would any other service-that is, you type the path to the files, which may be a network drive or a universal naming convention (UNC) name such as \\server1\ntfiles.For more information, refer to the Windows NT Server System Guide.


Setting Up for Remote Administration
Setting Up Services for Macintosh	5 of 9

Setting Up from Windows NT Server

Setting Up for Remote Administration

You can set up the administrative tools on any Windows NT computer so that you can administer Services for Macintosh remotely from a Windows NT clients.

Refer to the Windows NT Resource Kit for information on setting up administrative tools on Windows NT computers.


Stopping and Removing Services for Macintosh
Setting Up Services for Macintosh	6 of 9

Stopping and Removing Services for Macintosh

After you have set up Services for Macintosh on a server, you can remove it at any time. For example, you might want to move your Services for Macintosh installation to another server. When you remove Services for Macintosh, all Services for Macintosh files are deleted from the server's hard disk, except some program files that are in use. (The files in use will be reworked when the system is rebooted.)

Before you remove Services for Macintosh, it's recommended that you stop the services using the Devices control in Control Panel.

If the services are running, removing will delete only the registry entries.

To stop the services

1.	From Control Panel, which appears in the Main Group window, choose the Devices icon.

2.	The Devices dialog box appears.

3.	From the Device list, select AppleTalk Protocol.

4.	Choose the Stop button.

The Stopping dialog box appears.

5.	Choose the OK button to stop the AppleTalk Protocol and the Print and File Servers for Macintosh. After the devices have stopped, choose the Close button.

Now you're ready to remove Services for Macintosh.

To remove Services for Macintosh

1.	From Control Panel, choose Network.

The Network Settings dialog box appears.

2.	In the Installed Network Software box, select Services for Macintosh.

3.	Choose the Remove button.

4.	Choose the Yes button to confirm that you want to remove the Services for Macintosh files from the computer running Windows NT Server.

5.	Choose the OK button.

The AppleTalk Protocol and the File and Print Servers for Macintosh will all be deleted. Removing will also make all volumes unavailable to the Macintosh users, but it will not delete them; in other words, the volumes will revert to directories.


Setting Up the Services for Macintosh Client Software
Setting Up Services for Macintosh	7 of 9

Setting Up the Services for Macintosh Client Software

Microsoft authentication is an extension to AppleShare, which provides a more secure logon session to a computer running Windows NT Server. It encrypts passwords and stores them on the computer running Windows NT Server. You can either set up or instruct Macintosh users to set up the authentication file on their Macintoshes via the network.

With Microsoft authentication, users can also specify a domain when they log on or change their passwords. So, if they have an account in several domains, the right one will be used. (To do this, users type domainname\username in the Name box.)

To gain access to the authentication files

1.	From the Macintosh Apple menu, select the Chooser.

The Chooser dialog box appears.

2.	Select the AppleShare icon, and then the AppleTalk zone in which the computer running Windows NT Server resides.

3.	From the list of file servers, select the name of the Windows NT Server.

4.	Choose the OK button.

A sign-in dialog box appears.

5.	Choose the Registered User or Guest option buttons, as appropriate.

6.	Choose the OK button.

A server dialog box appears.

7.	Select the Microsoft UAM Volume.

8.	Choose the OK button.

9.	Close the Chooser dialog box.

To install the authentication files on the Macintosh client

1.	From the Macintosh Desktop, double-click the Microsoft UAM Volume to open it. The Microsoft UAM Volume window appears.

2.	Select the AppleShare Folder and drag it to the System Folder on your hard disk.

Note

If the Macintosh client already has an AppleShare Folder in the System Folder, you will see a message that asks whether you want to overwrite the folder. You should not overwrite it because it may contain other UAMs, such as the NetWare® UAM. If you want to maintain the files in the original AppleShare Folder, simply open the AppleShare Folder in the Microsoft UAM Volume, and drop the MS UAM file into your existing AppleShare Folder in your System Folder.

Now, when the Macintosh user connects to the computer running Windows NT Server, authentication will be offered as shown in the following dialog box:

How this is done depends on the Macintosh system the user is running. If a Macintosh is running System 7.1 or later and the cleartext and guest options are disabled at the server level, the user will only be given one choice-Microsoft Authentication. Earlier systems will show both choices-Microsoft Authentication and cleartext password protection in the form of the Apple standard UAMs, even if the cleartext and guest logon options have been disabled and are unavailable to clients.


Setting Up Buttons on the File Manager Toolbar
Setting Up Services for Macintosh	8 of 9

Setting Up Buttons on the File Manager Toolbar

If you use Services for Macintosh frequently, you may want to customize the File Manager toolbar to include Services for Macintosh buttons. To make room for the Services for Macintosh buttons, you may need to remove separators (spaces between the buttons) or other buttons.

The Services for Macintosh buttons available for setup include the following commands: Create Volume, Remove Volumes, and Permissions, which are available on the MacFile menu in File Manager.

From File Manager, use the Options menu and the Customize Toolbar command to make changes to the Toolbar. For more information about customizing the Toolbar, refer to the Windows NT Server System Guide.


Choosing a Zone After Setup
Setting Up Services for Macintosh	9 of 9

Choosing a Zone After Setup

After setting up Services for Macintosh and rebooting, you can choose a zone for Services for Macintosh. For more information, refer to Chapter 5, "Configuring Services for Macintosh."


Configuring Services for Macintosh
Chapter 5	1 of 5

Configuring Services for Macintosh

The AppleTalk Protocol is the component of Services for Macintosh that can be configured using the Network icon in Control Panel.

AppleTalk Protocol is a stack of protocols that Services for Macintosh uses to route information and configure zones. It works behind the scenes to ensure that computers on the network can talk to one another.


Starting the Configuration
Configuring Services for Macintosh	2 of 5

Starting the Configuration

You start configuration of the AppleTalk Protocol from the Network icon in Windows NT Server Control Panel.

To get started

1.	In Control Panel, choose Network.

The Network Settings dialog box appears.

2.	From the Installed Network Software list, select Services For Macintosh.

3.	Choose the Configure button.

The Services For Macintosh Configuration dialog box appears.


Configuring AppleTalk Protocol
Configuring Services for Macintosh	3 of 5

Configuring AppleTalk Protocol

You use the Services for Macintosh Configuration dialog box to select a default network from a list of adapter cards bound to the AppleTalk Protocol, and to enable routing and seeding of the network, which include configuring zones and setting network ranges.


Choosing a Network and Zone
Configuring Services for Macintosh	4 of 5

Configuring AppleTalk Protocol

Choosing a Network and Zone

Start with the Services for Macintosh Configuration dialog box (see "Starting the Configuration" earlier in this chapter) where you can see the default network and the other network adapters to which the AppleTalk Protocol is bound. You also use this dialog box to select the zone where the services will appear, to specify that the server act as an AppleTalk router, and to choose Advanced options for AppleTalk routing, such as seeding the network. Seeding the network means determining zones and the default network and setting network ranges.

To choose a network and zone

1.	In the Network box, select the network you want.

Note

If the computer running Windows NT Server is to be used as a router, the LocalTalk network cannot be used as the default network.

2.	In the Zone box, select the zone in which you want Services for Macintosh to appear.

This is the zone in which the File Server for Macintosh and Windows NT Server printers will appear when Macintosh users select them in Chooser.

If you select the Enable Routing check box, the computer running Windows NT Server will become an AppleTalk router. This means that if the AppleTalk Protocol is bound to more than one network card, the computer running Windows NT Server will be seen from Macintoshes connected to all the bound networks. Otherwise, the computer running Windows NT Server can be used only from the Macintoshes connected to the default network, unless another router broadcasts the information for the other networks. Also, if you choose the Advanced button, you can specify that the server seeds the network as well.


Seeding the Network
Configuring Services for Macintosh	5 of 5

Configuring AppleTalk Protocol

Seeding the Network

From the list in the Network box, you can select other network adapter cards to which the AppleTalk Protocol is bound. You can also specify that the network be seeded. Seeding means that this computer running Windows NT Server will initialize the network information.

Caution

The seeding information must agree with all routing information on that network and internet. Otherwise, all routers on the internet could fail to function.

To seed the network

1.	From the Services for Macintosh Configuration dialog box, choose Enable Routing and then choose the Advanced button.

The AppleTalk Routing Configuration dialog box appears.

2.	If you want, select another network from the Networks list.

This list contains all network adapter cards to which the AppleTalk Protocol is bound. (To add and remove network adapters, use the Network icon and the Add Adapter and Remove buttons in Control Panel.)

3.	Choose the Seed This Network check box.

This option makes the Zone Information, the present state of the Zone List, and the Network Range options available.

To have the server stop seeding a network

1.	Clear the Seed This Network option button.

2.	Choose the OK button.

Setting the Network Range

Setting the network range is part of seeding a network. Each AppleTalk network in an internet is assigned a range of numbers, and each node is identified to the network by one of those numbers, combined with a dynamically assigned AppleTalk node identification number. Because of this, no two networks on an internet should have overlapping ranges.

The value you specify for a network must range from 1 through 65,279. If you specify a range that overlaps another network range on the computer running Windows NT Server, you'll see a warning message. For more information about ranges, refer to Chapter 3, "Planning Your AppleTalk Network."

To set a network range

1.	In the Start box, provide a number.

2.	In the End box, provide a number.

If the network adapter is for a LocalTalk network, you cannot type a value in the end range.

Setting Zone Information

Setting zone information is part of seeding a network. You can see the current list of zones, add and remove zones, and set the default zone. The default zone is the zone in which all AppleTalk devices will appear if a desired zone has not been specified for the device.

To set zone information, start with the AppleTalk Routing Configuration dialog box. For an explanation of how to get to this dialog box, see "Starting the Configuration" and "Seeding the Network" earlier in this chapter.

To see the current state of the zones on a chosen network

1.	From the Services for Macintosh Configuration dialog box, select a zone from the Zone List.

2.	Choose the Get Zones button.

This gets the current zone information for the current network. If you want to see zones on another network, select one from the Networks list.

To add a zone to the network

1.	In the New Zone box, type the name of the new zone.

2.	Choose the Add button.

The new zone is added to the Zone List.

3.	Choose the OK button.

To remove a zone or zones from the network

1.	In the Zone List box, select a zone or zones.

2.	Choose the Remove button or Remove All button, as appropriate.

The zone or zones are removed from the Zone List. For others on the network to see the change, however, you must restart the AppleTalk Protocol, which is serving as a router.

3.	Choose the OK button.

To set a new default zone for the network

1.	In the Zone List box, select a zone.

2.	Choose the Set Default button.

You see the new default zone highlighted in the Zone list. For others on the network to see the change, however, you must restart the AppleTalk Protocol, which is serving as a router.

3.	Choose the OK button.

Note

For the changes to take effect, you must stop the AppleTalk Protocol and restart it so that the information can be routed on the network.


Setting Up Printers
Chapter 6	1 of 11

Setting Up Printers

Before setting up printers, it's important to understand the distinction between a printer that you create using Print Manager and a printing device, which you connect, or attach, to your computer running Windows NT Server or to the network.

A printing device is the hardware that actually does the printing, such as a Hewlett-Packard® LaserJet®. A printer that you create using Windows NT Server is a software interface between the document and the printing device. You create a printer using Print Manager, and each printer sends jobs to the printing device, according to the specified priority-for example, on a first-come, first-served basis.

These concepts and others are explained more fully in the Windows NT Server Concepts and Planning Guide. You should read that book if this information is new to you.


Services for Macintosh Print Server
Setting Up Printers	2 of 11

Services for Macintosh Print Server

When Services for Macintosh is set up, several AppleTalk services are integrated into Windows NT Server. The print server, called Print Server for Macintosh, is integrated into the Windows NT Server Print Manager. The print server makes printers connected to the computer running Windows NT Server available to Macintosh clients, and it makes AppleTalk PostScript printers (with LaserWriter drivers) available to PC clients.

When Print Manager receives print jobs from the print server, it sends them to a spooler, which is a portion of the hard disk. The spooler then sends the print job to the specified printing device-for example, to a printing device on the AppleTalk network. This enables Macintosh users, as well as PC users, to submit print jobs and continue working on their computers without waiting for the print job to complete.

Print Manager also translates all incoming PostScript files if the print request is to a non-PostScript printer attached to the computer running Windows NT Server. So, a Macintosh client (but not a Windows NT client) can send a PostScript job to any Windows NT Server printer.


Stopping and Restarting the Print Server
Setting Up Printers	3 of 11

Services for Macintosh Print Server

Stopping and Restarting the Print Server

When you set up Services for Macintosh, all services are automatically started, including the print server. You may want to stop and restart the print server if, for example, you must remove a printing device. You stop and restart the Print Server for Macintosh using the Services icon in Control Panel.

To stop and restart Print Server for Macintosh

1.	From Control Panel, choose the Services icon.

The Services dialog box appears.

2.	From the Service list, select Print Server For Macintosh.

3.	Choose the Stop or Start buttons, as appropriate.

To change options at startup, choose the Startup button.

4.	Choose the Close button.


Printing on a Network
Setting Up Printers	4 of 11

Printing on a Network

The following list shows the three scenarios for printing on a network:

PC clients send print requests to printers representing printing devices attached to a computer running Windows NT Server.

Macintosh clients send print requests to printers representing printing devices on an AppleTalk network.

Macintosh and PC clients send print requests to printers representing printing devices attached to a computer running Windows NT Server (for example, to a non-PostScript printing device such as the HP DeskJet® 500) and to printing devices on an AppleTalk network (for example, to a PostScript printing device such as the Apple LaserWriter).

Printing is very easy in each of these scenarios. PC users simply specify printers on a computer running Windows NT Server and send print jobs to them as usual, whether the printing device is attached to the server itself or located elsewhere on the network. Similarly, Macintosh users have the familiar Chooser interface to use for connecting to printers that are set up for both AppleTalk printing devices and those attached to a computer running Windows NT Server.

The first two scenarios are the common setup for networks serving either PC or Macintosh clients, respectively. Setup options for PCs and printers attached to a computer running Windows NT Server are explained in the Windows NT Server Concepts and Planning Guide. Macintosh network and printer options are explained in Macintosh software manuals. The last scenario is explained in this chapter.


Planning the Setup of Printing Devices
Setting Up Printers	5 of 11

Printing on a Network

Planning the Setup of Printing Devices

With Services for Macintosh, installing and setting up printing devices and creating printers is no different than what you'd normally do using Windows NT Server, with one exception-the print server and file server must appear in the same zone. However, there are some performance issues worth considering.

In PC networks printing devices have traditionally attached to a server through serial or parallel ports, whereas printing devices used on Macintosh networks have traditionally attached to the network using a LocalTalk connection. With Services for Macintosh, you can attach a printing device to a computer running Windows NT Server, or put it on the AppleTalk network. Either way, both types of clients can send print jobs to the printing device. (If on AppleTalk, the printer must be a PostScript printer that uses the LaserWriter driver.)

You get the fastest performance by attaching printing devices to the network, rather than to a port. The following attachment options are listed in slowest to fastest order:

1.	The printing device is connected to a serial port attached to the computer running Windows NT Server.

(Some older models of the Apple LaserWriter can be attached only to a serial port, not to a parallel port.)

2.	The printing device is connected to a parallel port attached to the computer running Windows NT Server.

3.	The printing device is connected to the AppleTalk network through LocalTalk, which is the typical Macintosh network attachment.

4.	The printing device is connected to AppleTalk through the token ring or ethernet media.

How you attach printing devices to AppleTalk depends on the type of network media you are using for your AppleTalk network. Most Macintosh-compatible printing devices have LocalTalk connections to AppleTalk. If your network is ethernet or token ring, you may need to do one of the following before adding a printing device to it:

Install a LocalTalk/ethernet or LocalTalk/token-ring router on your network.

Install a LocalTalk card in the server, and connect the printing device to it. The server will act as a router between the ethernet network and the LocalTalk network where the printing device is located.

The type of printing devices with built-in ethernet interfaces offer the best performance. These printing devices attach directly to the network and don't need to be physically close to the computer running Windows NT Server. Also, they print at faster network transmissions speeds than printers that rely on parallel or serial connections.


Creating a Printer on a Computer Running Windows NT Server
Setting Up Printers	6 of 11

Creating a Printer on a Computer Running Windows NT Server

Once you have physically attached a printing device to a computer running Windows NT Server (either directly or on a network), you create a printer that represents it, using Print Manager. You can create more than one printer representing the same printing device.

For example, if you have a printing device in your office, but also share it with others over the network, you might want to create two printers representing the printing device. You can create a printer for yourself that is not shared over the network and a second printer that is shared. Then it's easy to control the use of the shared printer. You can set permissions on the shared printer, ensuring that only members of your department can print to it. Or you can set a low priority for it, ensuring that documents you send to the printer will always print before documents sent by those who share it.

Another common example is to create a printer that spools to a printing device at night, and another printer that spools to the same printing device during the day.

To create a printer, you must be logged on with sufficient permissions. Administrators, Server Operators, and Print Operators can create printers.

To create a printer

1.	From the Main group window, choose the Print Manager icon.

The Print Manager dialog box appears.

2.	From the Printer menu, choose Create Printer.

The Create Printer dialog box appears.

3.	In the Printer Name box, type the name of the printer.

The name can be up to 32 characters long. This name will appear in the title bar of the printer window. By default, it is the name that network users (except MS-DOS users) will see when you share the printer.

4.	In the Driver list, select the printer driver.

If the printer driver does not appear in the list or if you want to update the printer driver, choose Other. Print Manager prompts you to specify the name of the driver and the drive or path where the driver is located. Once you have done so, choose the OK button. Print Manager adds the new driver to the list or replaces the old driver with the new one.

5.	In the Description box, type an optional description.

Network users will see this description when adding the printer to their available printers. Use the description to inform them about the printer. For example, if the printer is available only during certain hours, you could include that information here.

6.	From the Print to list, select the appropriate destination.

If the printing device is physically connected to the computer running Windows NT Server, select the appropriate port. To see a list of AppleTalk printing devices, choose Network Printer at the bottom of the Print to list. Then choose AppleTalk Printing Devices from the Print Destinations dialog box and the OK button. From the Available AppleTalk Printing Devices dialog box, select a zone and a printing device and choose the OK button.

7.	Choose the Share this printer on the network box.

8.	In the Share Name box, specify the printer name that you want MS-DOS clients to see.

9.	In the Location box, type the printing device's location- for example, a building and printer room designation, such as 1/1000.

10.	Choose the OK button.


Setting Up a User Account for Macintosh Print Jobs
Setting Up Printers	7 of 11

Setting Up a User Account for Macintosh Print Jobs

After setting up Services for Macintosh, you should create an account that will be used by all Macintosh clients when printing jobs to captured AppleTalk printing devices or other devices on the computer running Windows NT Server. You should also configure Print Server for Macintosh to use this account.

Once created, the user account (for example, MACUSERS) appears in the list of names that is displayed when you choose Permissions from the Security menu in Print Manager. You can give specific rights to this user account, just as you would any user account, including Print and No Access.

For more information about permissions, see Chapter 8, "Managing the File Server." For information on creating a user account and more specific information for configuring it to run with a service, such as Print Server for Macintosh, see the Windows NT Server System Guide.

To configure the Print Server for Macintosh service to use a user account

1.	From Control Panel, choose the Services icon.

The Services dialog box appears.

2.	Select Print Server For Macintosh.

3.	Choose the Startup button.

The Print Server For Macintosh dialog box appears.

4.	Choose This Account button and type or choose the user account- for example, MACUSERS.

5.	If you want to require a password for Macintosh users of the computer running Windows NT Server, type a password in the Password box and confirm it.

6.	Choose the OK button.


Enabling Clients to Use Printers on the AppleTalk Network
Setting Up Printers	8 of 11

Enabling Clients to Use Printers on the AppleTalk Network

With Services for Macintosh, both PC and Macintosh clients can send print jobs to printing devices or spoolers on the AppleTalk network.

The printing device must appear as a LaserWriter in the Chooser, and there must be a Windows NT print driver for the printing device.

Macintosh clients use printers just as they normally do - through the Chooser. If an AppleTalk printer has been set up through Print Manager, it may be captured so that Macintosh clients cannot access it directly. This means their print jobs go through the computer running Windows NT Server and they are spooled, along with print jobs from PC clients.

You can disable the capture setting. Doing this enables any Macintosh client to print to an AppleTalk printer directly. There are a few problems with this scenario, the most important being that the jobs will not be under the administrator's control.

To release or recapture an AppleTalk printing device

1.	From the Printer menu in Print Manager, choose Properties.

The Printer Properties dialog box appears.

2.	If you want to release a printer, skip to step 4. Otherwise, verify that this printer is using the printing device you want to capture by reviewing and selecting from, if appropriate, the Print to list.

To see a list of AppleTalk printing devices, choose Other at the bottom of the Print to list. Then choose AppleTalk Printing Devices from the Print Destinations dialog box and the OK button. From the Available AppleTalk Printing Devices dialog box, select a zone and a printer, and choose the OK button.

3.	Choose the Settings button.

A dialog box appears, asking if you want to capture this AppleTalk printing device.

4.	Choose Yes or No, as appropriate.

5.	Choose the OK button.

When an AppleTalk printer is released, any Macintosh user on the AppleTalk network can use the device directly.

A printing device on AppleTalk can be captured when Services for Macintosh is set up and a printer is created for it. They must remain captured so that all Macintosh clients send print jobs through the computer running Windows NT Server. If a printing device has been released for some reason, you can recapture it.

You can select another spooler, instead of an actual device. You should use this type of configuration with caution. It is possible to create an endless loop of print spooling with this method.


Advanced Topics
Setting Up Printers	9 of 11

Advanced Topics

Whether printing devices are attached to the computer running Windows NT Server or are located elsewhere on the AppleTalk network, Print Manager displays a list of print jobs for the respective printers you created to represent the devices. Each list, by default, presents jobs in first-come, first-served order. You can change the priority of jobs, however, and specify permissions for the printer and times for print jobs to run. For example, you can do the following:

Set up multiple printers that all send print jobs to a single printing device. You might want to assign the printers a priority number (such as high-priority and low-priority), or assign times for the printer to spool its jobs (such as during business hours or only during the night).

Set up a single printer that sends print jobs to a pool of printing devices. Doing this can make printing more efficient because print jobs are sent to the first available printing device in the pool.

An illustration of the first approach follows:


Creating Multiple Printers for a Single Printing Device
Setting Up Printers	10 of 11

Advanced Topics

Creating Multiple Printers for a Single Printing Device

You might want to create multiple printers, all of which send print jobs to a single printing device. Each printer has a print-priority level associated with it. If you create two printers and associate them with a single printing device, jobs routed to the printer with the highest priority (lowest number) print first.

For PC users, it's a good idea to create a group that corresponds to each printer. For example, users in Group1 might have access rights to a priority-1 printer, users in Group2 might have access rights to a priority-2 printer, and so on. This way, you can prioritize print jobs according to the users submitting their jobs. (Refer to the Windows NT Server System Guide for more information.)

For Macintosh users, however, one user account must be created for all incoming print jobs to the computer running Windows NT Server. Consequently, all Macintosh users sending print jobs through the computer running Windows NT Server will have the same access rights.

To specify priorities for printers sending jobs to a single printing device

1.	If necessary, create the two (or more) printers and share them, using procedures described earlier in this chapter and in the Windows NT Server System Guide.

2.	For each printer, from the Printer menu, choose Properties.

3.	Choose the Details button.

The Printer Details dialog box appears.

4.	In the Priority box, choose the appropriate priority for each printer.

Priority 1 has the highest priority, Priority 2 has the next highest, and so on.

5.	Choose the OK button.

You can also create two printers that postpone the print jobs-for example, one that releases its queued jobs at night and another during daytime hours. You do this by using the Printer Details dialog box to change the hours that each printer is available. For more information about setting up printers, refer to the Windows NT Server System Guide and the Windows NT Server Concepts and Planning Guide.


Creating Printing Pools
Setting Up Printers	11 of 11

Advanced Topics

Creating Printing Pools

When you create a printer, you can associate it with more than one printing device in order to form a printing pool. A printing pool consists of two or more similar printing devices associated with one printer name. To set up a pool, you create a printer and assign it as many output ports as you have identical printing devices. Printing pools have the following characteristics:

All devices in the pool share the same print property settings and act as a single unit. For example, stopping one device pauses them all.

Print destinations can be of the same type or mixed (serial, parallel, and network).

When a job arrives for the printing pool, the spooler on the computer running Windows NT Server checks the destinations to see which device is idle. The first port selected gets checked first, the second port second, and so on. If your pool consists of a different type of port, make sure you select the fastest port first (network, then parallel, and then serial).

A printing pool may contain a mixture of printer interface types, but the printing devices must all use the same printer driver.


Working with Macintosh-Accessible Volumes
Chapter 7	1 of 11

Working with Macintosh-Accessible Volumes

A computer running Windows NT Server with Services for Macintosh can store files so that both PC and Macintosh users can gain access to them. PC users (including users of the MS-DOS, OS/2, Windows, Windows for Workgroups, Windows NT Workstation, and Windows NT Server systems) look for shared files in a shared directory on the computer running Windows NT Server. Macintosh users look for shared files in the same directory; however, they see the directory as a volume, with familiar folders and files.

A Macintosh user shares a file with PC users by storing that file in a Macintosh-accessible volume on the computer running Windows NT Server. Likewise, a Macintosh user can mount a Macintosh-accessible volume on the desktop to use files stored in shared directories by PC users.

This chapter explains how to create a Macintosh-accessible volume so that files can be shared between Macintosh and PC clients.


Creating Volumes
Working with Macintosh-Accessible Volumes	2 of 11

Creating Volumes

All Macintosh-accessible volumes must be created on an NTFS partition or on a CDFS volume. If you specify a CDFS volume, the Macintosh-accessible volume will provide read-only access. (In this case, CDFS volume refers to a hard disk volume.)


Creating a Macintosh-Accessible Volume
Working with Macintosh-Accessible Volumes	3 of 11

Creating a Macintosh-Accessible Volume

Similar to creating a share (shared directory) for PC users, you can designate a directory as a Macintosh-accessible volume. If the directory is to be accessed by PC clients as well as Macintosh clients, make sure you share the directory, using the Share As command on the Disk menu and designate it as a Macintosh-accessible volume. (Refer to the Windows NT Server System Guide for more information on creating shares.) If you don't need to share the files with PC users, you can create a volume on a directory - that is, it doesn't have to be a shared directory.

Note

You cannot give a directory Macintosh-accessible volume status if it is a subdirectory of another directory that has Macintosh-accessible volume status. Refer to Chapter 2, "How Services for Macintosh Works," for more information.

You designate a directory as a Macintosh-accessible volume using the Create Volume command on the MacFile menu. From the Create Volume dialog box, you can quickly create the volume by accepting the default settings, or you can change the options.

To create a Macintosh-accessible volume

1.	From File Manager, select the directory that you want to designate as a Macintosh-accessible volume.

2.	From the MacFile menu, choose Create Volume.

The Create Macintosh-Accessible Volume dialog box appears.

The default setting for each option follows:

Option		Default Setting
Volume name		Same as the directory name. The character limit is 27.
Path		Same as the directory path.
Password/Confirm Password		No password.
This volume is read-only		Off.
Guests can use this volume		On (Yes).
User Limit		Unlimited.
Permissions		Current directory permissions.
Using the default name and path has some advantages when a directory will be available as a share to PC users and as a volume for Macintosh users. Ease of communication between the two clients is simplified if the directory is referred to by the same name.

3.	To accept the default options, choose the OK button. Otherwise, continue to the next step.

4.	In the Volume Name box, type a volume name that Macintosh users will see when they log on.

5.	In the various boxes, specify a new path, password, security options, and user limits.

These options are described later in this chapter, in "Modifying a Macintosh-Accessible Volume."

6.	Choose the Permissions button to set directory permissions for Macintosh users.

The Macintosh-accessible volume automatically inherits the permissions of the corresponding directory, although you may change these. For further explanation of permissions, see "Setting Permissions for Volumes and Folders," later in this chapter.

7.	Choose the OK button.


Creating a Macintosh-Accessible Volume on a CDFS Volume
Working with Macintosh-Accessible Volumes	4 of 11

Creating a Macintosh-Accessible Volume

Creating a Macintosh-Accessible Volume on a CDFS Volume

You follow the same procedure for creating a Macintosh-accessible volume on a CDFS volume as you did for creating one on an NTFS-partitioned drive. The only difference is that the CDFS disk is read-only. So, Services for Macintosh will interpret all security options as See Files and See Folders (read-only).


Creating Folders in a Volume
Working with Macintosh-Accessible Volumes	5 of 11

Creating Folders in a Volume

You can create subdirectories for a Macintosh-accessible volume from the computer running Windows NT Server or folders from Macintosh clients. In either case, the procedure for creating the directories or folders is no different than it is for creating other directories or folders on the respective systems.

On the computer running Windows NT Server, the folders appear in the File Manager's directory tree as subdirectories of the directory. To create another subdirectory, you select the directory in which it will appear, and choose Create Directory from the File menu.

On the Macintosh, you create folders using the New Folder command on the File menu. You can view and use the folders in the Macintosh-accessible volume just as you would any other volume-by using the View menu to see the folders organized by Name, Date, Icon, Size, and so forth.

You cannot, however, designate the subdirectory or folder as another Macintosh-accessible volume when the directory is already designated as a Macintosh-accessible volume. For a quick review, see the illustration in the section "Configuring Macintosh-Accessible Volumes" in Chapter 2.


Setting Permissions for Volumes and Folders
Working with Macintosh-Accessible Volumes	6 of 11

Setting Permissions for Volumes and Folders

Just as you set permissions on shared directories to control which PC users have access to the share, you control who can use Macintosh-accessible volumes by setting permissions. Permissions also control what kind of access is granted to users. For example, permissions dictate which users can make changes to a folder, and which ones can read the content of the folder but not alter it in any way. Permissions for volumes and folders can be set in a number of ways.

From File Manager, you can set Windows NT-style permissions with the Permissions command on the Security menu. (You set permissions on a Macintosh-accessible volume or folder, just as you would on a shared directory.) Or you can use Macintosh-style permissions, available in the Macintosh View Of Directory Permissions dialog box. From File Manager, you can find this dialog boxes in three ways - when you choose Permissions, Create Volumes, or View/Modify Volumes from the MacFile menu.

This section explains how to set Macintosh-style permissions on Macintosh-accessible volumes and folders, using the Macintosh View of Directory Permissions dialog box. Information on setting Windows NT-style permissions is covered in the Windows NT Server System Guide. For a more detailed discussion of Macintosh-style permissions and how they relate to Windows NT permissions, refer to Chapter 2, "How Services for Macintosh Works."

Note

Macintosh files inherit the permissions set on folders; you cannot set permissions on files directly.

To set Macintosh-style permissions on a Macintosh-accessible volume or folder

1.	Using File Manager, select the directory you've designated as a Macintosh-accessible volume or a subdirectory that represents a folder in the volume.

2.	From the MacFile menu, choose Permissions.

Or, from the View/Modify Macintosh-Accessible Volumes dialog box, choose the Permissions button.

The Macintosh View Of Directory Permissions dialog box appears.

3.	For Owner, Primary Group, or Everyone, choose the See Files, See Folders, or Make Changes permissions check boxes.

Use the following table to help you decide which permissions to set.

Directory Permissions

Permission		Description
See Files		Allows the owner, primary group, or everyone to see and open files in this folder
See Folders		Allows the owner, primary group, or everyone to see and open folders in this folder
Make Changes		Allows the owner, primary group, or everyone to add or delete files and folders, and save changes to files in this folder
4.	Beneath the permissions, select the appropriate check boxes, which are described in the following table.

Directory Permissions Check Boxes

Check box		Description
Replace permissions on subdirectories		Copies the permissions you just set to all folders within this volume or folder
Cannot move, rename, or delete		Prevents the volume or folder from being moved, renamed, or deleted by Macintosh users


Changing the Owner or Primary Group
Working with Macintosh-Accessible Volumes	7 of 11

Changing the Owner or Primary Group

While setting permissions on a directory, you can change the owner and primary group to which the permissions apply. The owner is the same as the one you see when choosing Permissions from the Security menu in File Manager. The primary group, however, is unique to Macintosh clients. The owner's primary group is the group the owner works with most, and it should be the group with which the owner has the most resource needs in common. When an owner creates a folder on a computer running Windows NT Server, the owner's primary group is set as the group associated with the folder. The owner (or administrator) can change the primary group associated with the folder from either the computer running Windows NT Server or the Macintosh.

To change the owner of the directory

1.	From the MacFile menu in File Manager, choose Permissions.

The Macintosh View Directory Permissions dialog box appears.

2.	Choose the button to the right of the Owner list box.

The Owner dialog box appears.

3.	From the Names list, select a new owner and choose the Add button.

You can also browse for members of the selected domain (including trusted domains), and search the list of domain users for a specific user you want to select as owner.

4.	Choose the OK button.

To change the primary group of the directory

1.	From the Macintosh View Of Directory Permissions dialog box, choose the button to the right of the Primary Group list box. The Primary Group dialog box appears.

2.	In the Names list, select a group, and choose the Add button.

You can also browse for groups in the selected domain (including trusted domains) and search the list of domain groups for a specific primary group.

Note

In the Owners and Primary Group dialog boxes, you can also specify global groups as an owner, and owners as primary groups.

To change the primary group of an owner (rather than a directory), refer to the User Manager for Domains.


Modifying a Macintosh-Accessible Volume
Working with Macintosh-Accessible Volumes	8 of 11

Modifying a Macintosh-Accessible Volume

You can change the properties of a Macintosh-accessible volume from the MacFile menu in File Manager. Properties include passwords, security options, and user limits, as well as permissions.

To modify the properties of a Macintosh-accessible volume

1.	From the MacFile menu, choose View/Modify Volumes.

The View/Modify Macintosh-Accessible Volume dialog box appears.

2.	Select the Macintosh-accessible volume you want to change.

3.	Choose the Properties button.

The Properties of Macintosh-Accessible Volume dialog box appears.

4.	Make the changes to the options you want, as follows.

Macintosh-Accessible Volume Properties

Option/button		Description
Password		Enter the password for this volume. When Macintosh users try to mount this volume, they will be asked for this password.
Confirm password		Confirm the password you just entered.
This volume is read-only		This volume and all of its contents have read-only access. This option supersedes all directory permissions set with the Permissions button. In other words, if you give this volume read-only access, the permissions of directories with less restrictive access will not be honored.
Guests can use this volume		Guests can have access to this volume. If unchecked, guests do not see this volume.
Unlimited		Number of clients that can simultaneously access this volume is unlimited (limited only by the media).
Allow xxx Users		Number of clients that can simultaneously mount the volume on the respective desktops.
Permissions		Set access permissions on this volume. See "Setting Permissions for Volumes and Folders," earlier in this chapter.


Removing a Macintosh-Accessible Volume
Working with Macintosh-Accessible Volumes	9 of 11

Removing a Macintosh-Accessible Volume

If you want to make a volume unavailable to Macintosh users, you must remove it. Removing the volume does not delete the files contained in the volume, nor does it delete its status as a shared directory if it has been designated as a share for PC users. Removing only removes its status as a Macintosh-accessible volume.

To remove a Macintosh-accessible volume

1.	From File Manager, choose the MacFile menu.

2.	Choose Remove Volumes.

The Remove Macintosh-Accessible Volumes dialog box appears.

3.	Select the volume, or volumes, you want to make inaccessible to Macintosh users.

4.	Choose the OK button.

If Macintosh users are currently connected, you'll see a message that tells you who is using the volume. You can then use the Send Message command on the MacFile menu in Server Manager to send these users a warning that you intend to remove the volume. When no users are signed on, continue with the next step.

Caution

You can continue to remove the volume if users are still using it; however, the users are likely to lose data.

5.	In the confirmation box, choose the Yes button.

If you decide later to make the directory a Macintosh-accessible volume again, you can do that by following the steps in "Creating a Macintosh-Accessible Volume," earlier in this chapter.

To delete the contents of the shared directory, follow the instructions for deleting files in the Windows NT Server System Guide.


Getting Help
Working with Macintosh-Accessible Volumes	10 of 11

Getting Help

Help is available when you are using the MacFile menu in File Manager.

To get Services for Macintosh Help in File Manager

From the MacFile menu, choose Help.

You can also choose the Help button in any dialog box you see after choosing commands from the MacFile menu.


Using macfile to Work with Macintosh-Accessible Volumes
Working with Macintosh-Accessible Volumes	11 of 11

Using macfile to Work with Macintosh-Accessible Volumes

You can accomplish all of the volume configuration (and server administration) discussed in this chapter using the macfile command at the command prompt. The macfile command is provided to allow administrators to automate Services for Macintosh volume, directory, file and server management by using batch programs.

For syntax of the macfile command, type macfile /? at the command prompt. For a complete reference to the macfile command, choose Help from the MacFile menu in File Manager.


Managing the File Server
Chapter 8	1 of 15

Managing the File Server

You use User Manager to establish user accounts (including Macintosh user accounts), and you use Server Manager to set security options for the server and do other server-level tasks. When Services for Macintosh is started, you use the MacFile menu in Server Manager to view the Macintosh users of the server and the Macintosh-accessible volumes. You can also send messages to Macintosh users of Windows NT Server, among other tasks.

Many of the tasks that you can do from Server Manager are available when you choose the MacFile icon in Control Panel. Individual volume options are available in the MacFile menu in File Manager, which are explained in Chapter 7, "Working with Macintosh-Accessible Volumes."

The File Server For Macintosh (MacFile) is available from different locations in Windows NT Server.


Setting Logon Security for Macintosh Users
Managing the File Server	2 of 15

Setting Logon Security for Macintosh Users

You set security options for Macintosh users of Services for Macintosh from the Properties command on the MacFile menu in Server Manager. The options available from the MacFile menu apply to Macintosh-accessible volumes on the computer running Windows NT Server and are described in the following procedure.

(For information on setting security for shared directories, which make files available to PC users, refer to the Windows NT Server System Guide.)

To set security options for all Macintosh-accessible volumes

1.	From the Administrative Tools group, choose Server Manager.

2.	From the MacFile menu, choose Properties.

The MacFile Properties dialog box appears.

3.	Choose the Attributes button.

The MacFile Attributes dialog box appears.

4.	From the Security box, make the following selections as you prefer.

Security Options

Select this option		To do this
Allow Guests to Logon		Permit users who do not have a user account and password to log on to the computer running Windows NT Server from a Macintosh, which is connected to the AppleTalk network.
Allow Workstations to Save Password		Permit Macintosh users to save their passwords on their own workstations. That way, they won't be prompted for it each time they sign on to the computer running Windows NT Server. However, permitting this makes the computer running Windows NT Server less secure.
Require Microsoft Authentication		Specify that Macintosh users must use Microsoft Authentication, rather than the Apple Standard UAM or other UAMs. If this option is chosen, Macintosh users either will not see the other UAM choices, or they will be unavailable for selection.
5.	Choose the OK button.

The security options available from the Attributes dialog box apply to all the Macintosh-accessible volumes on the computer running Windows NT Server. (The individual volume permissions that are available in File Manager from the MacFile menu are explained in Chapter 7, "Working with Macintosh-Accessible Volumes.") For an explanation of Windows NT Server security issues, refer to the Windows NT Server Concepts and Planning Guide.


Changing the Server Name, Logon Message, and Session Limits
Managing the File Server	3 of 15

Changing the Server Name, Logon Message, and Session Limits

You can change the name of the server, which goes into effect when you stop and restart File Server For Macintosh. (This is the name that Macintosh users will see.) You can also create a message that Macintosh users (of System 7.1) see when they log on to the computer running Windows NT Server. And you can specify the number of Macintosh clients that can simultaneously connect to the File Server For Macintosh on the computer running Windows NT Server.

To change the name of the computer running Windows NT Server

1.	From the MacFile menu in Server Manager, choose Properties.

The MacFile Properties dialog box appears.

2.	Choose the Attributes button.

The MacFile Attributes dialog box appears.

3.	Choose the Change button.

4.	In the Server Name For AppleTalk Workstations dialog box, type a new name for the server.

5.	Choose the OK button.

6.	From the Services icon in Control Panel, stop and restart File Server For Macintosh.

To create a logon message for 7.1 System users

1.	From the MacFile menu, choose Properties.

The MacFile Properties dialog box appears.

2.	Choose the Attributes button.

The MacFile Attributes dialog box appears.

3.	In the Logon Message box, type a message that you want Macintosh users to see when they sign on to the computer running Windows NT Server.

You can type four lines of text (the AppleTalk limit).

4.	Choose the OK button.

To set session limits

1.	From the MacFile menu in Server Manager, choose Properties.

The MacFile Properties dialog box appears.

2.	Choose the Attributes button.

The MacFile Attributes dialog box appears.

3.	In the Session box, choose Unlimited or specify a client limit by entering the number you want.

The number you specify is the number of clients that can simultaneously gain access to the File Server For Macintosh. If you choose Unlimited, the number of connections is limited only by the capabilities of the network media. However, performance improves when you limit the number of sessions.

4.	Choose the OK button.


Setting Up User Accounts for Macintosh Users
Managing the File Server	4 of 15

Setting Up User Accounts for Macintosh Users

User accounts are created for Macintosh users just as they are created for other Windows NT Server users. A guest account is automatically created when you install Windows NT Server, and by default both local guests and guests accessing the server through a client on the network, including a Macintosh, are allowed. This means that if users log on without a regular user account and password, they will be logged on as a guest.

Guests have some access to shared resources. Guests can do everything that those with a user account can do except keep a local profile on their computers, lock their computers, and create, delete, and modify local groups on their computers.

The guest account cannot be deleted, but it can be disabled on Windows NT computers. If it is disabled, no network users, including Macintosh users, will be able to log on without a user account and password. To disable only Macintosh guests from the computer running Windows NT Server, follow the instructions in "Setting Logon Security for Macintosh Users," earlier in this chapter. For more information about the guest account, refer to the Windows NT Server Concepts and Planning Guide.


Stopping and Pausing Services
Managing the File Server	5 of 15

Stopping and Pausing Services

When you set up Services for Macintosh, the two services, File Server For Macintosh and Print Server For Macintosh, are automatically started, as is the AppleTalk Protocol. You may need to stop these services at times-for example, stopping Print Server For Macintosh to install a new printer driver. (You cannot pause Print Server For Macintosh.) Other reasons you may want to stop and pause (and then start) the services include the following:

Service		Reason
Print Server For Macintosh (MacPrint)		Stop it to install another printer driver or to configure a printer; or to immediately see the result of deleting, creating, or changing a printer. To remove the Print Server for Macintosh service.
File Server For Macintosh (MacFile)		Stop it to change the server name that Macintosh users will see, and to remove the MacFile Service. Pause it when you want to make changes to the server attributes but want to allow current users to continue working. If this service is paused, no new Macintosh users can log on to the computer running Windows NT Server.
AppleTalk Protocol		Stop it to change router parameters and the default networking zone, and to remove it (which automatically stops the file and print servers).
You can use the Services command on the Computer menu in Server Manager to control the file and print servers. (You can use the Services icon in Control Panel to stop or start Print Server For Macintosh and to stop, start, pause, or continue File Server For Macintosh.)

You use the Devices icon in Control Panel to stop the AppleTalk Protocol and, consequently, both the file and print servers.

To stop, start, pause, or continue services

1.	From Server Manager, select the Computer menu.

2.	Choose the Services command.

The Services dialog box appears.

3.	In the Services dialog box, find the service you want to change and check its status.

4.	Select either the File Server For Macintosh or Print Server For Macintosh.

You cannot pause and continue the Print Server For Macintosh.

5.	Select the Start, Stop, Pause, or Continue buttons as appropriate.

If you want to change the startup options (for example, to specify manual startup), choose the Startup button. For a thorough explanation of this dialog box, refer to the Windows NT Server System Guide.

6.	Choose the Close button.


Checking the Event Log
Managing the File Server	6 of 15

Checking the Event Log

You can check events on the computer running Windows NT Server using Event Viewer, which is available in the Administrative Tools group. If Services for Macintosh is running, you can see events that involved the File or Print Server For Macintosh or the AppleTalk Protocol.

To check AppleTalk and MacFile events

1.	From the Administrative Tools group, choose Event Viewer.

The Event Viewer-System Log window appears.

2.	Review the Source list and look for MacFile, MacSrv, or AppleTalk events you want to monitor.

Use the Event Viewer options for these services just as you would for other Windows NT Server events. For example, to see specific events, choose Filter Events from the View menu. (The Browser service must be started.)

To check printing events

From the Log menu, choose Application.

You see a list of events including those generated by the AppleTalk Print Monitor and MacPrint.

Use the Event Viewer options for these services just as you would for other Windows NT Server events.

For more information about Event Viewer, refer to the Windows NT Server System Guide.


Viewing a List of Macintosh-Accessible Volumes
Managing the File Server	7 of 15

Viewing a List of Macintosh-Accessible Volumes

You view a list of all the volumes that are available to Macintosh users on the computer running Windows NT Server through the MacFile menu in Server Manager. The Volumes command lists all directories that have been designated as Macintosh-accessible volumes and allows you to create and remove individual volumes, just as you can do from the MacFile menu in File Manager.

The Volumes button, which is available when you choose Properties from the MacFile menu, allows you to see what users are connected to individual volumes and disconnect them. For more information, refer to "Disconnecting Macintosh Users and Volumes," later in this chapter.

To view a list of Macintosh-accessible volumes

1.	From the Administrative Tools group, choose Server Manager.

2.	From the View menu, choose MacFile.

This choice limits the list of servers so that you can easily choose the computer running Windows NT Server and Services for Macintosh.

3.	From the MacFile menu, choose Volumes.

The Macintosh-Accessible Volumes dialog box appears.

This dialog box displays a list of Macintosh-accessible volumes on the computer running Windows NT Server. You can create or delete volumes here or change the properties and permissions of the volumes. (Properties and permissions for volumes are explained in Chapter 7, "Working with Macintosh-Accessible Volumes.")

You can also view other information about the Macintosh-accessible volumes on the computer running Windows NT Server, including their paths and the names of users connected to them.

To see volume information

1.	From the Administrative Tools group, choose Server Manager.

2.	From the MacFile menu, choose Properties.

The MacFile Properties dialog box appears.

3.	Choose the Volumes button.

The Macintosh-Accessible Volumes dialog box appears.

4.	Select a Macintosh-accessible volume.

You can see how many times the volume has been mounted by Macintosh users at this time and its directory path on the computer running Windows NT Server. You can also see how long users have been connected to the volume and whether there are open files on the volume.

5.	Choose the Close button.


Viewing Current Users of Volumes
Managing the File Server	8 of 15

Viewing Current Users of Volumes

You can see the current list of users connected to selected Macintosh-accessible volumes.

To view connected users

1.	From the Administrative Tools group, choose Server Manager.

2.	From the MacFile menu, choose Properties.

The MacFile Properties dialog box appears.

3.	Choose the Users button.

The Macintosh Users dialog box appears.

4.	Select a user.

You see the Macintosh-accessible volumes that the user has mounted, the name of the Macintosh computer, how many volume file forks are open, and the amount of time that the user has been connected to the computer running Windows NT Server in hours and minutes. For more information about file forks, refer to the next section.

You can also disconnect a user from all connected volumes or all users from all connected volumes, using the Disconnect and Disconnect All buttons, respectively. For more information, refer to "Disconnecting Macintosh Users and Volumes," later in this chapter.

5.	Choose the Close button.


Viewing Open File Forks
Managing the File Server	9 of 15

Viewing Open File Forks

You may want to view the resources, or file forks, that Macintosh clients are using. (Remember that data is kept in a data fork, and system information in a resource fork.) Viewing open file forks can tell you who has what forks open before you stop the File Server For Macintosh or disconnect a user, for example.

To view open file forks

1.	From the Administrative Tools group, choose Server Manager.

2.	From the MacFile menu, choose Properties.

The MacFile Properties dialog box appears.

3.	From the MacFile Properties dialog box, choose the Files button.

The Files Opened by Macintosh Users dialog box appears.

This dialog box lists all the resource and data forks that are open on Macintosh clients connected to the computer running Windows NT Server. A summary of the options in this dialog box follows.

File Forks Opened by Macintosh Users Dialog Box

File fork option/button		Description
Open File Forks		Summary count of all the open data and resource forks.
Locks (locks prevent multiple users from gaining access to the same fork at the same time)		Total count of all the locks on file forks in Macintosh-accessible volumes.
Opened by		Macintosh user who has opened the file fork.
For		Permissions set (for example, Read/Write)
Locks (individual fork count)		Number of locks on the fork.
Path		Directory path of the file.
Refresh		Update the list box and recalculate counts of forks and locks.
Close Forks		Close the selected file.
Close All Forks		Close all Macintosh-accessible volume forks on the computer running Windows NT Server.
4.	Choose one of the buttons as described in the previous table.

5.	Choose the Close button.


Disconnecting Macintosh Users and Volumes
Managing the File Server	10 of 15

Disconnecting Macintosh Users and Volumes

You disconnect users from volumes when you choose Properties from the MacFile menu in Server Manager or when you choose the MacFile icon in Control Panel. These instructions describe Server Manager approach, but you can use the basic instructions with the MacFile icon in Control Panel as well.

It's a good idea to send a message to users before disconnecting them or volumes that they are using. Otherwise, they may lose data. Refer to the next section for more information.

To disconnect users from Macintosh-accessible volumes

1.	From the Administrative Tools group, choose Server Manager.

2.	From the MacFile menu, choose Properties.

The MacFile Properties dialog box appears.

3.	Use the following table to determine what you want to disconnect.

MacFile Disconnect Options

MacFile Properties dialog box		Disconnect button		Disconnect All button
Users button: When selected, displays the Macintosh Users dialog box with Disconnect and Disconnect All buttons.		Disconnects a selected user from all connected volumes.		Disconnects all users from all connected volumes.
Volumes button: When selected, displays the Macintosh-Accessible Volumes dialog box with Disconnect and Disconnect All buttons.		Disconnects selected users of a selected volume.		Disconnects all users from selected volumes.
4.	Choose the Users button or the Volumes button.

5.	Select the user or volume you want to disconnect from the respective dialog boxes.

6.	Choose the Disconnect or Disconnect All button, as appropriate.

7.	From the confirmation box that appears, choose the Yes button.

Caution

If you disconnect users or volumes, you could cause the loss of data. It's a good idea to send users a message before disconnecting.


Sending Messages to Connected Macintosh Users
Managing the File Server	11 of 15

Sending Messages to Connected Macintosh Users

Services for Macintosh enables you to send messages to Macintosh clients that are connected to the computer running Windows NT Server. For example, it's a good idea to tell Macintosh users that you intend to remove a volume before doing so or that you plan to disconnect users or volumes. Otherwise, they may lose valuable data.

You can send messages to Macintosh users from three places:

MacFile icon in Control Panel (choose the Users button).

MacFile menu in Server Manager

Choose Send Message.

Choose Properties, and then the Users and Send Message buttons.

The following instructions describe the MacFile menu approach; however, the basic instructions apply for the MacFile icon in Control Panel as well.

To send a message to all connected Macintosh users

1.	From the Administrative Tools group box, choose Server Manager.

2.	From the list of computers, select a server that is running Services for Macintosh.

3.	From the MacFile menu, choose Send Message.

The Send Message dialog box appears.

4.	In the Message box, type the message you want to send to Macintosh users.

You can type up to four lines, the AppleTalk limit, for example, "The server is going to be shut down in 10 minutes."

5.	Choose the OK button.

To send a message to individual Macintosh users of the computer running Windows NT Server

1.	From the MacFile menu, choose Properties.

2.	Choose the Users button. The Macintosh Users dialog box appears.

3.	From the Connected Users box, select the user to whom you want to send the message.

4.	Choose the Send Message button.

5.	Select the Selected MacFile user button.

6.	In the Message box, type the message you want to send.

You can type up to four lines.

7.	Choose the OK button.


Setting Extension-Type Associations
Managing the File Server	12 of 15

Setting Extension-Type Associations

With extension-type associations, users of both the PC and the Macintosh version of an application can easily work on the same data file. The extension-type associations provided with Services for Macintosh tell the Finder which MS-DOS filename extensions correspond with which Macintosh file types and file creators. When a file on the server has a filename extension associated with a Macintosh file type and file creator, the Finder displays the appropriate icon for that file when a Macintosh user browses the files available on the server. And if a Macintosh user chooses the file, the appropriate application starts and opens the file.

The extension-type associations that follow are already defined. Others may be added to Services for Macintosh. Refer to the Association command in the MacFile menu (from File Manager) to see a comprehensive list.

PC application/file format		Macintosh application		MS-DOS extension	Macintosh type	Macintosh creator
Adobe® Encapsulated PostScript		Adobe Illustrator® '88		EPS	EPSF	ARTZ
Aldus® PageMaker® for Windows version 2.0, Aldus PageMaker for OS/2 version 2.0		Aldus PageMaker for Macintosh version 2.0		PUB	PUBF	ALD2
Aldus PageMaker for Windows version 3.0 Publication Template Template Template TIFF graphics file		Aldus PageMaker for Macintosh version 3.0 Publication Template Template Template TIFF graphics file		PM3 PT3 TEM TPL TIF	ALB3 ALT3 ALT3 ALT3 TIFF	ALD3 ALD3 ALD3 ALD3 ALD3
Aldus PageMaker for Windows version 4.0 Publication Template Template Template TIFF graphics file		Aldus PageMaker for Macintosh version 4.0 Publication Template Template Template TIFF graphics file		PM4 PT4 TEM TPL TIF	ALB4 ALT4 ALT4 ALT4 TIFF	ALD4 ALD4 ALD4 ALD4 ALD4
Borland® dBASE®		Microsoft FoxBASE®/FoxBASE+® for Macintosh		DBF	F+DB	FOX+
Lotus® 1-2-3® for Windows version 2.0		Lotus 1-2-3 for Macintosh version 1.1		WK3	LWK3	L123
Microsoft Excel for Windows version 3.0, Microsoft Excel for OS/2 version 3.0 Chart Spreadsheet Macro sheet Workspace Add-in macro file Template file		Microsoft Excel for Macintosh version 3.0 Chart Spreadsheet Macro sheet Workspace Add-in macro file Template file		XLC XLS XLM XLW LA XLT	XLC3 XLS3 XLM3 XLW3 XLA SLM3	XCEL XCEL XCEL XCEL XCEL XCEL
Microsoft Excel for Windows version 4.0,Microsoft Excel for OS/2 version 4.0 Chart Spreadsheet Macro sheet Workspace Add-in macro file Template file		Microsoft Excel for Macintosh version 4.0 Chart Spreadsheet Macro sheet Workspace Add-in macro file Template file		XLC XLS XLM XLW XLA XLT	XLC4 XLS4 XLM4 XLW4 XLA SLM3	XCEL XCEL XCEL XCEL XCEL XCEL
Microsoft Multiplan®/SYLK		Microsoft Excel for Macintosh version 3.0		SLK	TEXT	XCEL
Microsoft PowerPoint® version 2.0 Slides		Microsoft PowerPoint for Macintosh version 2.0		PPT	SLD2	PPT2
Microsoft PowerPoint version 3.0 Slides		Microsoft PowerPoint for Macintosh version 3.0		PPT	SLD3	PPT3
Microsoft Project for Windows version 1.x Projects Exchange format Calendars Views Workspaces		Microsoft Project for Macintosh version 1.x Projects Exchange format Calendars Views Workspaces		MPP MPX MPC MPV MPW	MSPF MSPJ MSPJ MSPJ MSPF	MSPJ MSPJ MSPJ MSPJ MSPJ
Microsoft Word for Windows version 2.0 Document Text Document Rich Text Style sheet Glossary		Microsoft Word for Macintosh version 5.1 Document Document Rich Text N/A N/A		DOC WRD RTF STY GLY	WDBN TEXT TEXT TEXT TEXT	MSWD MSWD MSWD MSWD MSWD
N.A./Comma-Separated Values		Microsoft Excel for Macintosh version 4.0		CSV	TEXT	XCEL
N.A./SIT files		Alladin Stuffit		SIT	SIT!	SIT!
N.A./Text (TXT files)		Teachtext		TXT	TEXT	TTXT
PC Program		N.A.		EXE COM CMD BAT	DEXE DEXE DEXE DEXE	LMAN LMAN LMAN LMAN
Symantec Ready!		Symantec MORE		RDY	TEXT	MORE
Unknown File		N.A.		All others	TEXT	LMAN
Visicalc (DIF)		Microsoft Excel for Macintosh version 4.0		DIF	TEXT	XCEL
You can also add extension-type associations. You can add new associations for an application not listed in the preceding table, or you can add extra associations for any of the listed applications. For example, if your company has a custom of saving Microsoft Word documents with a .WRD extension, you could add the following extension:

MS-DOS extension		Macintosh file type		Macintosh file creator
.WRD		WDBN		MSWD
When you add a new extension-type association, it affects only files that are subsequently created on the server, not currently existing files. Moreover, you can associate multiple extensions with a Macintosh file type and creator. However, the reverse is not true. Only one file type and creator can be associated with an extension.

Note

The WKS and WK1 formats allow a single data file to be used by users of Microsoft Excel, Lotus 1-2-3, and Informix® Wingz®. However, you can set up an extension for only one Macintosh application for this format. For example, if you map the WKS and WK1 extensions to the file type and file creator values for Microsoft Excel for Macintosh and then a Macintosh user double-clicks the file's icon, the file will be loaded into Microsoft Excel for Macintosh.

To make new extension-type associations

1.	From the Main group window, choose the File Manager icon.

2.	From the MacFile menu, choose Associate.

The Associate dialog box appears.

3.	In the Files with MS-DOS Extension box, type an extension, or select one from the list.

If the extension is already associated with a file type and file creator, it will be highlighted in the Creator list.

4.	In the Creator box, select a creator and type to which you want to associate this extension.

5.	Choose the Associate button.

The new association is added to the Creator list in the Extension-Type Association dialog box.

To add file creators and types

1.	Choose the Add button.

The Add Document Type dialog box appears.

2.	In the Add Document Type dialog box, type the file creator and type and, optionally, a description.

3.	Choose the OK button.

You'll see the new creator in the Creator list. When you're ready to associate it with an extension, follow the previous instructions for creating an extension-type association.

Note

File creator and type are case-sensitive on the Macintosh and thus must be entered exactly as they appear on the Macintosh.

To edit a description of a file type

1.	In the Creator list box, select a file creator and type.

2.	Choose the Edit button.

3.	In the Edit Document Type dialog box, type the new description.

4.	Choose the OK button.

The new description will appear in the Creator list.

To remove a file type and associations

1.	In the Creator box, select a file creator and type.

2.	Choose the Delete button.

3.	Choose the Yes button to confirm that you want to remove the selected file type and associated extensions.


Backing Up Files on the Server
Managing the File Server	13 of 15

Backing Up Files on the Server

Following the Windows NT Server backup procedure will also back up Macintosh-accessible volumes. First, however, it is a good idea to stop the File Server for Macintosh service, using the Services icon in Control Panel. Stopping the service ensures that all files are backed up. You must stop the File Server for Macintosh before restoring a volume. The use of the Backup tool, which is available in the Windows NT Server Administrative Tools group, is described in the Windows NT Server System Guide.

You can also back up and restore volumes from the Macintosh client, using Macintosh backup software, such as FastBack™, RetroSpect, or Norton Utilities®.

To back up or restore Macintosh-accessible volumes from the Macintosh

1.	Make sure all the Macintosh-accessible volumes you want to back up are not in use by other Macintoshes.

2.	Mount the Macintosh-accessible volumes you want to back up on the Macintosh desktop.

3.	Start a Macintosh backup and restore program from the Macintosh.

Follow the instructions given by your backup software program.


Getting Help
Managing the File Server	14 of 15

Getting Help

Help specific to Services for Macintosh is available in Server Manager and in the MacFile Properties dialog box, which appears when you choose the MacFile icon in Control Panel.

To get Services for Macintosh Help in Server Manager

From the Help menu, choose MacFile.

To get Help when using the MacFile icon in Control Panel

1.	Choose the MacFile icon.

The MacFile Properties dialog box appears.

2.	Choose the Help button.


Using macfile to Administer the Services for Macintosh Server
Managing the File Server	15 of 15

Using macfile to Administer the Services for Macintosh Server

You can accomplish all of the server configurations discussed in this chapter (and volume, file, and directory management) using the macfile command at the command prompt. The macfile command is provided to allow administrators to automate Services for Macintosh volume, directory, file, and server management by using batch programs.

For syntax of the macfile command, type macfile /? at the command prompt. For a complete reference to the macfile command, choose Help from the MacFile menu in File Manager.


Troubleshooting
Chapter 9	1 of 4

Troubleshooting

This chapter provides solutions for problems that may occur on a computer running Windows NT Server with Services for Macintosh installed. This includes problems that both users and administrators may encounter. Network error messages are explained in the Windows NT Server message database, which is available as part of the Help system.


Administrator and User Issues and Solutions
Troubleshooting	2 of 4

Administrator and User Issues and Solutions

When a Macintosh user is unable to gain access to a Services for Macintosh resource, first check the Macintosh - specifically the following:

The Macintosh client is using version 6.0.7 or later of the Macintosh operating system (the system software).

The Macintosh client is using current versions of its network drivers, and these versions are compatible with the version of the operating system on that Macintosh.

To check whether the issue is with the Macintosh, try to access a network entity other than the computer running Windows NT Server or printer; for example, try to access an AppleShare server or a printer that isn't used by Services for Macintosh. If the Macintosh cannot access any network entity, the problem may be with the Macintosh.

A computer running Windows NT Server fails to start, and Event Viewer is filled with AppleTalk error messages.

Check to see if your network has a bridge that is filtering packets. It might be filtering out the server's requests to find a unique address.

See "Other Issues," later in this chapter.

The following are common user problems:

A Macintosh-accessible volume is unavailable to a user.

The volume might be configured as a private volume. A private volume is any volume where the owner, primary group, and/or everyone 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 and/or everyone categories at least one permission for the volume.

If the Macintosh-accessible volume is on a CDFS volume, and it appears in the Chooser but it cannot be selected, the CD-ROM on which it was created may 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.

A Macintosh user's password has expired without notification.

Users will be notified that their passwords have expired only if the MS UAM files are installed on their clients. If they are using the Apple standard UAM, they will only be told 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 Microsoft UAM Volume.

A user has forgotten his or her password.

Assign the user a new password. To do so, use User Manager to reset the password.

A user sees the message that their password is incorrect, even though it was entered correctly.

The user may have two accounts, with different passwords, on separate domains. Have the user enter the domain and then their account name in the Name box when they log on. For example:

Domain1\alex02A

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

Two physical AppleTalk networks have been given the same network numbers. The server 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 the Network icon in Control Panel, to 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. Refer to Chapter 5, "Configuring Services for Macintosh," for more information.

If you find no duplicates, check to 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.

The computer running Windows NT Server and printers intermittently appear and disappear in the Chooser.

Zones and network numbers are no longer in correspondence.

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.

If you haven't changed zone names recently, this situation could occur if an AppleTalk network number is duplicated on your AppleTalk internet.

Cannot find a file or folder.

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 to access the folder.

Cannot save a file with an 8.3 filename from the Macintosh.

A short name may already exist with that name; however, Macintosh users cannot see it.

Give the 8.3 filename a different name.

Cannot find a server.

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, check to see 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, check that the network connector is securely connected to its port. Select the Network icon in Control Panel 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 check 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 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. For more information about router seeding plans and server databases, see Chapter 3, "Planning Your AppleTalk Network."

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.

Make sure AppleTalk is active in the Chooser.

Open Control Panel, and then open the Network icon. Make sure the correct network port is selected.

There might be router problems. Check for the following:

The Macintosh may be running on an AppleTalk Phase 2 Network without the correct Ethernet driver.

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

The Macintosh 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 UAM Volume cannot be found.

When the computer running Windows NT Server was installed, there may have not been adequate disk space to set up the Microsoft UAM Volume. Or the computer running Windows NT Server may not have been installed with an NTFS partition.

In this case, 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.

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

The folder owner must log on to the server, connect to the Macintosh-accessible volume, and select a view (such as View By Icon, View By Name, and so on) 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.

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

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 utility to reset the file type and file creator of the file. Only use this utility if you are experienced with it.

A PC user cannot see the contents of a folder.

The PC user does not have sufficient permissions to view the contents of the folder. Use the computer running Windows NT Server to make sure the user has Read permission, or the folder owner can use a Macintosh to give the PC user both the See Files and See Folders permissions. (A PC user must have both these permissions to get the Windows NT Server Read permission.)

A Macintosh user did not receive a server message.

Only Macintosh clients 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.

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

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, automatically connecting 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 using Microsoft Authentication.

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 Microsoft Authentication to log on to the server, you must mount the volume through the Chooser and then use the alias.


Printing Issues and Solutions
Troubleshooting	3 of 4

Printing Issues and Solutions

The following are common situations involving printers or printing devices:

AppleTalk printers don't show up in the Print Manager's Available AppleTalk Printer's dialog box.

Clicking the AppleTalk Zone name does not display the printers in that zone. You must double-click the Zone name from this dialog box.

Printing error messages consistently appear when the printing device prints documents.

Reset the printing device by turning it off and then on again.

The PostScript error "Offending command" appears at the end of the printed document or elsewhere.

A user or administrator might have canceled the print job while it was spooling. No action is necessary, and you can reprint the file if you want.

A user is spooling to a PSTODIB printing device, and it has PostScript level 2 elements or is a PostScript level 2 document.

Print jobs fail to print.

Check each printing device that prints jobs for these printers. If one of the printing devices is turned off, all printing devices can stop printing.

Macintosh extended characters (such as bullets, smart quotes, and copyright and trademark symbols) are changed into other characters on the LaserWriter II.

Set the communications port for the LaserWriter correctly, referring to the owner's manual for the printing device. If the LaserWriter hasn't been set correctly, there can be a problem printing, regardless of how you set the COM port in Control Panel in Windows NT Server. This problem affects Macintoshes more frequently than PCs because Macintoshes use extended characters more often than other clients do.


Other Issues
Troubleshooting	4 of 4

Other Issues

Filenames - POSIX

Do not use POSIX filenames in the same directory tree that Macintosh users can access through Macintosh-accessible volumes. The POSIX subsystem is case-sensitive (that is, you could create one file called accounts and another called ACCOUNTS and even another called Accounts).

MCA Computers and LocalTalk Cards

Because of a hardware issue, the LocalTalk card should not be set to either IRQL.5 or IRQL.6. Otherwise, Windows NT Server will not reboot on MCA computers.

The interrupt setting used for the Local Talk card should not be shared with any other device.

Reinstalling and Permissions

If you install Windows NT Server on a computer that already has an NTFS partition, or you reinstall Windows NT Server, you cannot designate, or redesignate a directory as a Macintosh-accessible volume. You can avoid this situation by reformatting the NTFS partition or simply avoid using formerly created NTFS directories when creating Macintosh-accessible volumes.

Adding and Removing Trusted Domains

If a domain administrator adds or removes a trusted domain, you need to stop and restart the File Server for Macintosh so that it can register the changes.


Registry Values
Appendix A	1 of 7

Registry Values

Windows NT Server maintains configuration information in a database called the Registry. The database consists of keys and subkeys, where the information, or values, is stored. You can change the values with the Registry Editor, REGEDT32.EXE. (The Registry replaces the .INI files you may have used in previous versions of the Windows environment and LAN Manager.) The Registry and Registry Editor are explained more fully in the Windows NT Server Registry Editor online Help and in the Windows NT Resource Kit.

When Services for Macintosh is set up, additional values are added to the keys and subkeys of the Registry. It's a good idea to keep these keys at their default values. If you must do repair, some of the values that you may need to change are described in this appendix.


Changing Registry Key Values
Registry Values	2 of 7

Changing Registry Key Values

This section provides a brief description of the process for changing key values.

To change key values

1.	From File Manager, choose the drive on which Windows NT Server is installed.

2.	From the Windows NT system root directory (for example, \WINDOWS or \WINNT35), select the SYSTEM32 directory.

3.	Select the REGEDT32.EXE file, and run it (by double-clicking the filename).

4.	Choose the System directory, and then the CurrentControlSet directory.

5.	Choose the Services directory.

6.	Choose the directory corresponding to the service you want to change, either AppleTalk or MacFile. (You should not change entries in the MacPrint or MacSrv service.)

7.	Look at the corresponding section of this appendix to review the values for that service.

8.	When you're ready to make changes, double-click the entry to display the appropriate editor for that data type.


AppleTalk Key Values
Registry Values	3 of 7

AppleTalk Key Values

To change the key values for the AppleTalk stack, choose AppleTalk in step 7 of the preceding section. Values for AppleTalk Adapter and Parameter subkeys follow. (Linkage values should not be changed and are not described.)


Adapter Key Values
Registry Values	4 of 7

AppleTalk Key Values

Adapter Key Values

There is one subkey for each AppleTalk-compatible adapter on the computer. The Registry entries for the Elnkii01 adapter are used as an example.

Entry Name	Data Type	Range of Values
AarpRetries:	REG_DWORD:	0xa
This hexadecimal value specifies the maximum number of AppleTalk address resolution protocol packets to be sent by the AppleTalk Protocol.

The default is 0xa.

DdpCheckSums:	REG_DWORD:	0
This hexadecimal value tells the AppleTalk Protocol whether or not to compute checksums in the DDP layer. If this entry is 1, the AppleTalk Protocol will use sums in the DDP layer.

The default is 0.

DefaultZone:	REG_SZ:	Not applicable
This data-string value contains the default zone for this network if this adapter is seeding the network. If the adapter is seeding the network, the default zone is chosen when you configure Services for Macintosh.

There is no default.

NetworkRangeLowerEnd:		REG_DWORD:	0x1 - 0xfeff 1–65279 (decimal)
This hexadecimal value is the lower network number of the network range if this adapter is seeding the network. If seeding the network, this number is set from the Services For Macintosh dialog box.

There is no default.

NetworkRangeUpperEnd:		REG_DWORD:	0x1 - 0xfeff 1–65279 (decimal)
This hexadecimal value is the upper network number of the network range for this network if this adapter is seeding the network. If seeding, this number is set from the Services For Macintosh Configuration dialog box.

There is no default.

PortName:	REG_SZ:	AdapterName@ComputerName
This data-string value is the name that is used to identify the AppleTalk Protocol running on a particular adapter on a computer.

There is no default.

SeedingNetwork:	REG_DWORD:	0 - 1
This hexadecimal value is used by the AppleTalk Protocol during startup. If Seeding Network is 0, this adapter is not seeding the network, and the AppleTalk Protocol ignores any seeding information for the adapter, if specified. If SeedingNetwork is 1, the AppleTalk Protocol reads in all seeding information and seeds the network, if valid.

The default is 0.

ZoneList:	REG_MULTI_SZ:	(List of zones)
This multistring value is relevant only when the adapter is seeding the network. The network is seeded with this list of zones by the AppleTalk Protocol. Changes can be made using the Services For Macintosh Configuration dialog box.

There is no default.


Parameter Key Values
Registry Values	5 of 7

AppleTalk Key Values

Parameter Key Values

Parameter values set port, zone, and router information.

DefaultPort:	REG_SZ:	Not applicable
This data-string value is the network on which the Services for Macintosh service names are registered. If the AppleTalk Protocol is not routing, only Macintosh clients connected to this network can see the file and print services. During initial installation, the default port is automatically set to the first Ethernet adapter found, or to the first token-ring adapter, or a LocalTalk adapter (in that order). The default port can be changed from the AppleTalk Configuration dialog box.

The default is the first adapter found.

DesiredZone:	REG_SZ:	Not applicable
This data-string value is the zone in which the Services for Macintosh services is present. If this key is not set, Services for Macintosh is present in the default zone for that network. The preferred zone can be set from the AppleTalk Configuration dialog box.

There is no default.

EnableRouter:	REG_DWORD:	0 - 1
This hexadecimal value tells the AppleTalk Protocol if routing needs to be started on this computer. If routing is started, Macintosh clients connected to any of the networks that this computer is on should be able to use the File and Print Servers for Macintosh. This value is critical. Unless absolutely essential, do not set this value to 1. The value can be changed when configuring Services for Macintosh.

The default is 0.


File Server Key Values
Registry Values	6 of 7

File Server Key Values

The key values for the File Server for Macintosh are specified when you choose MacFile, in step 7 of the "Changing Registry Key Values" section, which appears earlier in this appendix. The Parameter keys that can be changed are explained in this section. (You should not change Icon or Extension entries.)


Parameter Key Values
Registry Values	7 of 7

File Server Key Values

Parameter Key Values

These key values specify server options, which can be set from Server Manager. All others are added when changes to the default values occur.

ServerName	REG_SZ:	(Server Name)
This data string value is the name of the computer running Windows NT Server and Services for Macintosh. Use the Windows NT Server name as the default, if you need to add this entry.

There is no default.

ServerOptions	REG_DWORD:	0x7
This hexadecimal value specifies server options that are set in Server Manager. If needed for repair purposes, change Bits 1 through 3; do not change any of the other bits. When on, Bit 1 allows guest logons, Bit 2 allows cleartext passwords, and Bit 3 allows Macintosh users to save passwords on their clients.

The defaults are bit 1, 2, and 3 set to on.

MaxSessions		REG_DWORD:	1 - unlimited
This hexadecimal value is the maximum number of user sessions that the File Server for Macintosh can accommodate.

The default is 0xff 255 (in decimal).

LoginMsg	REG_SZ:	1 - 198 characters
This data-string value specifies the message you want Macintosh users to see when they log on to the Windows NT Server.

There is no default.

PagedMemLimit	REG_DWORD:	0x3e8-0x3e800 1000-256000 (decimal)
This hexadecimal value is the maximum amount of page memory that the File Server for Macintosh will use. Performance of the MacFile service increases with an increase in this value. However, the value should not be set lower than 0x3e8, or 1000 kilobytes (K). It is especially important that you are well acquainted with memory issues before changing this resource parameter. You cannot change this value from Server Manager.

The default is 0x4e20 (20000 in decimal).

NonPagedMemLimit	REG_DWORD	0x100-0x3e80 256-16000 (decimal)
This hexadecimal value is the maximum amount of RAM that is available to the File Server for Macintosh. Increasing it helps performance of the File Server, but decreases performance of other system resources.

The default is 0xfa0 (4000 in decimal).

Volume Key Values

This multistring value specifies information about the Macintosh-accessible volumes on the computer running Windows NT Server. It's recommended that you add Macintosh-accessible volumes from File Manager.

To change the values for a Macintosh-accessible volume

1.	Double click on the name of the Macintosh-accessible volume for which you want to change key values.

2.	In the Data box, change the values, as described next:

MaxUses

This decimal value is the maximum number of simultaneous clients that can be connected to the File Server for Macintosh. The limit is determined by hardware and network media.

Properties

This decimal value (32768) specifies security options. When bit 1 is set to on, the volume is read-only. When bit 16 is set to on, guests can use this volume. The default value (in binary notation) is 1000000000000000 (guests can use this volume).

Password

This value contains the encrypted password. Don't change it. If a user forgets his or her password, you can delete this entry, thus removing a password requirement from the user's account. Then the user can specify a new password at logon.

Path

This value is the path of the root directory of the volume. If a volume has been deleted, the path may still be a valid one; consequently, you should not delete it. If volumes have been deleted from the user interface, you can delete this value.

Type-Creators

These values are a list of all the Macintosh type-creators to which PC-type extensions are associated. It's best to change these from File Manager, through the Associate command in the MacFile menu. If you decide to change these entries in the Registry, the range of values follows:

Creator must have from 1 through 4 characters.

Type must have from 1 through 4 characters.

Description must have from 0 through 29 characters.


How Filenames Are Translated
Appendix B	1 of 6

How Filenames Are Translated

The information in this appendix supplements the information given in Chapter 2, "How Services for Macintosh Works."

Windows NT, Macintosh, and MS-DOS systems each follow different file-naming conventions:

Operating system		File system	Character limit
MS-DOS		FAT	8.3 (8 characters, plus an optional extension, signaled by a period and up to 3 characters)
Macintosh		System software	31 characters
Windows NT		NTFS	256 characters
When a file with a long name (any name over the 8.3 MS-DOS standard) is saved on an NTFS partition, the long name is maintained, and a short name is created so that MS-DOS users can gain access to it if they are given the permissions to do so. For example, if Macintosh users create folders or files on a Services for Macintosh volume and they follow the 31-character limit, they will continue to use the original, long names. However, MS-DOS users will see a shortened version of it. Windows NT system users will see the longer Macintosh filenames because NTFS has a 256-character filename limit.

Even though NTFS translates long names to short names, it's a good idea for users to name shared files following the 8.3 convention, used by the FAT file system in MS-DOS. This simplifies file identification for users working on different platforms. This appendix explains how file translations work on Windows NT Server running Services for Macintosh. For more information, refer to your Windows NT Server System Guide.


Naming Differences
How Filenames Are Translated	2 of 6

Naming Differences

In general, the FAT file naming system, which is used on MS-DOS systems, is more restrictive than the Macintosh system. The two systems differ in the following ways:

Macintosh filenames and folder names can have as many as 31 characters and include blank spaces. FAT filenames and directory names can have as many as eight characters, followed by an optional extension (signaled by a period and up to three additional characters), and they cannot include blank spaces.

Macintosh filenames and folder names can include any Macintosh character except a colon (:). MS-DOS filenames and directory names have more exceptions, including the following:

(except the period signaling the extension) / [ ] ; = " \ : | , *

Both Macintosh and MS-DOS filenames and folder names (or directory names) can include extended characters; however, the Macintosh and MS-DOS extended character sets are different.

FAT filenames and directory names are acceptable as Macintosh filenames and folder names, unless they contain extended characters not found in the Macintosh character set. In this case, Macintosh users will see substituted characters.


Overview of Macintosh-to-8.3 Translation
How Filenames Are Translated	3 of 6

Overview of Macintosh-to-8.3 Translation

When a file is created on a Macintosh and saved on a computer running Windows NT Server, the File Server for Macintosh first checks it for illegal NTFS characters. Then NTFS takes over the file translation process.


What File Server for Macintosh Does
How Filenames Are Translated	4 of 6

Overview of Macintosh-to-8.3 Translation

What File Server for Macintosh Does

When a Macintosh filename is saved on a computer running Windows NT Server, the File Server for Macintosh component of Services for Macintosh does the following:

If required, the File Server for Macintosh changes illegal NTFS characters to the available range of Unicode™ characters, which are then mapped to the ANSI default character - a question mark (?). Illegal NTFS characters include:

" / \ * ? < > | :


What NTFS Does
How Filenames Are Translated	5 of 6

Overview of Macintosh-to-8.3 Translation

What NTFS Does

When NTFS receives a legal NTFS name from the File Server for Macintosh, it translates the name as follows:

Macintosh names that are already valid MS-DOS names stay the same - that is, no new short name is needed, and the long name and short name are the same. For example, SAMPLE.ART remains SAMPLE.ART.

The long name, not including its extension, is truncated to six characters, followed by a tilde (~) and a unique number, for a total of eight characters.

The last period, if any, in the long name signals the extension, which is retained.

In detail, here is what the File Server for Macintosh and Windows NT Server do to translate a valid long filename to a short name that MS-DOS users can see.

1.	NTFS then shortens a long name to the first six characters of the Macintosh name, followed by a tilde (~) and a unique number. For example, the Macintosh long name Project Overview is translated to Projec~1.

2.	If the short name is a duplicate of another name (long or short), NTFS automatically modifies the short name of the new file or folder by truncating the name to six characters and adding a tilde (~) and number until it creates a unique name.

For example, suppose a Macintosh user creates a file called Regional Data-East Coast. NTFS renames that file REGION~1. Next, the user creates a file named Regional Data-West Coast. That file becomes REGION~2. A third file, Regional Data-Europe, becomes REGION~3.

3.	If the original name has an extension (signaled by the last period in the name), it is retained. For example, Project Overview.Jan.txt becomes Projec~1.txt.

Note

If a Macintosh user gives a file or a folder a valid MS-DOS name, making translation to a short name unnecessary, the user may see a message that states that the name already exists, and the user must choose a new name. For example, this message appears if the user creates a file named SALES.DAT when another file in the folder already has that name.


How Extended Characters Are Mapped
How Filenames Are Translated	6 of 6

How Extended Characters Are Mapped

If Macintosh extended characters are used in filenames or folder names that are saved to the computer running Windows NT Server by Macintosh users, the File Server for Macintosh translates these extended characters to the equivalent Unicode characters so that PC users can see them.

If MS-DOS extended characters are used in filenames or directory names that are saved to the computer running Windows NT Server by PC users, the File Server for Macintosh also translates these extended characters to the equivalent Macintosh ANSI characters so that Macintosh users can see them.