Product

Platform

Operating system

Error

Symptoms

Cause

Solution

In order for file servers and tertiary nodes to work with Prinergy, accounts, permissions, and Appletalk, networking settings must be set correctly. These are all adminstrative tasks that should be performed by the customer. There is no Prinergy software installed on these nodes. This effectively isolates us from servicing these nodes.

Of course we would provide support for initial installation efforts. But after installation, if the file server or tertiary is not under a support contract, a reasonable effort should still be taken to help the customer troubleshoot the problem (half to one hour) but clearly state that this would be a billable call.

Do not dial in to the customer's site to reconfigure the node.

Checklist:

1. Add/check Araxi Service logon account to file servers and tertiaries.

This account is automatically created by the Prinergy installer on primary and secondary servers, but not on file servers or tertiaries. It must be added manually. This account must be on all servers that participate with Prinergy and it must have administrative rights.

Reference: Prinergy System Administration Guide 03-4116A Version 1.0 in section 3-11

2. Set/check the default Appletalk zone.

From the Network Control Panel on the Services tab, double-click Services for Macintosh. In the AppleTalk Protocol Properties window, on the General tab, set the default zone. All servers (primaries, secondaries, and tertiaries) should be in the same Appletalk zone if possible.

In some instances the Windows registry does not match what is specified in the Control Panel. To be certain you should check the entry manually.

a) From the Windows Start menu, select Run.

b) In the Open field, type "Regedt32", and click OK.

c) Select the HKEY_LOCAL_MACHINE window and browse to: \\System\Currentcontrolset\Services\AppleTalk\DesiredZone.

3. Set/check the AppleTalk server name.

Windows NT allows you to to configure the AppleTalk server name to be different than the NetBIOS server name. By default these are the same but in some cases you might want them to be different. Keep the name the same where possible.

A quick way to check - Is the server listed in the Macintosh chooser the same as the NT name?

How do I change the AppleTalk server name?

a) Log in as an Administrator.

b) Launch Server Manager from the Administrative Tools programs group. If the server is in a domain, a list of servers will be displayed.

c) From the computer menu, select Select Domain.

d) In the Domain field, type \\<servername> where servername is the local system. Only the local server will be displayed.

e) From the MacFile menu, select Properties.

f) Click on the Attributes button.

g) In MacFile Attributes of <servername> window, the server name for the Appletalk workstation is displayed.

h) Click the Change button and enter the new server name.

4. Edit/check the SFMhosts file on the primary server.

This file maps Services For Macintosh (SFM) server names to NT server names.

Use of this file is conceptually similar to the TCP/IP /etc/hosts file.

If the AppleTalk server name is the same and the NetBIOS name, you do not need to modify this file.

The file is located in %ARAXI_HOME%\etc\sfmhosts.

Format of each entry in the [/etc/sfmhosts] section:

"zone:sfmservername"="ntservername"

The zone name should ALWAYS be specified to avoid ambiguity.

Enclosing quotes are not strictly necessary. They are stripped if a matching begin/end pair is found.

If there are no zones enter "*".

i.e. "*:sfmservername"="ntservername"

5. Remove/recreate the Macintosh share.

The Macintosh share might have a corrupt index. Delete and recreate the share.

You can also force NT to recreate the Mac index manually without deleting and recreating the share. See the link in the See Also section, below.

Permanent fix:

See also

Files not visible from the Mac are visible from NT Explorer

Keywords

networking

Technical contact(s)

Simon Chen

Submitted by

Simon Chen

Date submitted

22 Mar 2000