Subscribe to Windows IT Pro
November 01, 1996 12:00 AM

Services for Macintosh

Windows IT Pro
InstantDoc ID #2817
Rating: (0)
NT 4.0 adds some new twists to a familiar component

Windows NT Server's Services for Macintosh integrates Macs with NT. Most enterprises have a few Macs that run applications ranging from graphics and illustration packages to word processing and relational databases. Services for Macintosh turns your NT server into a file-and-print server for those Macs: You can store Mac documents on your NT server and print them to an AppleTalk printer or server-attached printer via NT's print queues. To ease the integration of your AppleTalk and NT networks, Services for Macintosh also provides AppleTalk routing and Microsoft's encrypted authentication service.

Unfortunately, NT 4.0 does not provide a single interface for managing Services for Macintosh. Using a combination of Server Manager, File Manager (yes, it's still in NT 4.0), the Network Control Panel applet, a MacFile Control Panel applet, and optionally a command-line utility, you can configure all aspects of Services for Macintosh. File Manager is the only GUI utility where you can set Mac file associations. By default, the Start Menu does not reference File Manager when you install NT Server 4.0. To access File Manager, click Run from the Start Menu, enter winfile, and click OK. If you've already installed Services for Macintosh, you see a new menu option, MacFile, in File Manager, as in Screen 1. From this menu, you can configure aspects of the file system that Services for Macintosh uses.

From these utilities, you can install and configure Services for Macintosh and AppleTalk routing (Network Control Panel), create new Mac-accessible volumes (Server Manager and File Manager), set Mac application-specific file associations (File Manager), and see which Mac users are connected to your server and what files they have open (MacFile Control Panel applet). The MacFile Control Panel applet also lets you set some general service options for Services for Macintosh, such as which authentication method to use, how many users can connect to the server, and what name the server appears as on your Mac client's Chooser.

Let's examine the features of Services for Macintosh, how to install and configure file-and-print services (including AppleTalk routing and Microsoft authentication), and how to connect to an NT server from your Mac. I'll also review some rules about Mac file naming on NT servers, and how to keep it from getting ugly.

Services for Macintosh Features
Services for Macintosh provides file-and-print services to your Mac clients. With these services installed, your NT 4.0 server emulates an AppleShare server. To your Macs, your NT server is an AppleShare server. When you install Services for Macintosh, you see two new services in the Services Control Panel: File Server for Macintosh, which provides file services, and Print Server for Macintosh, which handles print serving functions to the Mac.

To provide Mac file services, you use Server Manager or File Manager to create Mac-accessible volumes on your NT server's hard drives. These volumes are NT folders that must exist on an NT File System (NTFS) partition that is accessible to both PC and Mac clients. Because Macs use different file permissions for AppleShare resources, Services for Macintosh includes options in both Server Manager and File Manager to manage these volumes and assign Mac-specific file permissions to NTFS files and folders.

Two configuration options support Mac printing services. The first is to use NT Server's printer utilities to capture a networked, AppleTalk-based Postscript printer. This option lets you spool print jobs from the NT Server print spooler. Most Macs run a local print spooler, so you need to disable this feature on your clients if you want NT Server to capture your AppleTalk printers.

The second print option lets you connect any printer to the serial or parallel ports of your NT Server. You can use this configuration to share the printer with both PC and Mac clients. If the printer doesn't use Postscript, the Macintosh Print Server will convert the job to the printing language the printer supports.

Installing File-and-Print Services
Anyone who's ever had to install and configure Novell NetWare for Macintosh NetWare loadable modules (NLM-an NLM is equivalent to an NT service) with its cryptic load commands, will love the speed at which you can get Services for Macintosh running on NT Server 4.0. All the GUI-based utilities are self-explanatory and include good context-sensitive Help.

In just a few steps, you can install Services for Macintosh, including configuring AppleTalk Phase 2 routing. From the Control Panel, select Services, and click Add. Scroll down the list, highlight Services for Macintosh, and click OK. When the system prompts you for the location of your NT Server distribution files, enter the location and click Continue.

After NT copies the appropriate distribution files, click Close in the Network dialog. The system updates the network bindings and prompts you to enter the default zone and routing information for the default network adapter installed on your server. Screen 2 shows the dialog for configuring this information. If you have multiple adapters installed, you need to configure each one for AppleTalk routing. If your NT Server connects to a network that has an AppleTalk router already defined, the system automatically locates the default zone for that network adapter. When you finish configuring Services for Macintosh, click OK and restart your server so the changes can take effect.

Related Content:

ARTICLE TOOLS

Comments
  • Bart Stidham
    13 years ago
    Aug 12, 1999

    I still think AppleTalk is an effective protocol, so I’m troubled to see bad advice in publications purporting to give good advice. Apple has made many mistakes over the years and perhaps one of the biggest is not publishing better notes on how to easily administer AppleTalk.

    AppleTalk is perhaps the most user-friendly protocol ever created. However, to make it so, you must ensure that all routers are properly configured and follow several (rarely written) rules.

    One rule concerns the dynamic nature of AppleTalk. You must configure AppleTalk on a given LAN segment with at least three times as many AppleTalk addresses as AppleTalk devices. Otherwise, the result is AppleTalk broadcast storms as Macs try to find an available or unused AppleTalk address.

    In November’s “Services for Macintosh,” Darren Mar-Elia states, “When designing a large AppleTalk network, use as small a range as possible on each segment to conserve network address space.” Because any network can use the entire allowable AppleTalk address range of 1 through 65,279, this advice is very bad: The penalties for are high for using too small an address range.

    --Bart Stidham,

    The Latin School of Chicago



    Thanks for your letter, but I have to disagree. I suspect you’re referring to a situation like the following: A new workstation comes up on a 250-node subnet and requests a node number. In this case, the new node picks a number and sends a broadcast on the local subnet to determine whether the number is available. The new node may have to go through 250 guesses before it finds a free number.

    On most high-speed media (e.g., Token Ring, FDDI, and even Ethernet), this process would not generate much concern. Even so, this kind of traffic does not constitute a broadcast storm.

    A broadcast storm is generally defined as a node broadcasting packets that require a response from many or all nodes. Remember that the node number discovery process is one broadcast packet out and one unicast packet in response.

    I can see a situation where 250 nodes all start at once, resulting in heavy network activity and probably protocol timeouts, but this situation is true of any networking protocol and is generally not recommended.

    Additionally, because of the underlying contention issues of the MAC-layer technology, most networks today have far fewer than 250 nodes on a given segment. A smaller segment is usually recommended, especially with AppleTalk, which tends to generate more background traffic for routing functions, name binding, and so forth. I’ve never seen or heard of broadcast storms as a result of small network ranges.

    One advantage to smaller network ranges is an easier time troubleshooting network problems with a protocol analyzer. If you’ve ever had to put a sniffer on an AppleTalk network, you know that tracking packet activity from nodes spread across wide network ranges can be difficult. For example, if you trace packets from network 20 and network 21, you don’t necessarily know whether they come from the same segment or are on two distinct ranges (e.g., 19 through 20 and 21 through 23).

    Again, thanks for the input. Let me know your thoughts on this.

    --Darren Mar-Elia

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.