Macintosh clients can use a number of different protocols to discover an Access Connect server, depending on what operating system is being used and how the administrator configures the server. Select the network protocols you want the server to use to register with—AppleTalk, Bonjour, Zidget/HTTP, or SLP— by placing a check in the appropriate checkboxes. The protocols available for discovering file, print, and DFS resources can be configured independently.
The Server name appears in the login window whenever a Macintosh user connects to the server. This name also appears in the Mac OS X Connect to Server dialog and on earlier Mac OS systems in the Chooser and the Network Browser when Macintosh users browse the network. You may change the name; use uppercase and lowercase text.
The AppleTalk protocol is primarily used by the Mac OS 9 Chooser. When AppleTalk is selected, Mac OS 9 users can see volumes and print queues in the Chooser without specifying the IP address, and Mac OS X users can see them in Connect to Server and Add Printer dialogs. To register the server on AppleTalk, the protocol must be installed on the Windows server. Windows XP, Vista, and Windows 2008 Servers do not include AppleTalk support.
Bonjour allows Mac OS X users to see volumes in the Connect to Server dialog and print queues in the Print Center.
The Access Connect Zidget is a replacement for AppleTalk and Bonjour service discovery that works across subnets without your having to configure your router. The Zidget uses XML over HTTP to retrieve a list of Access Connect servers and their Print Queues from a Master Access Connect server.
By default this master server is named ExtremeZIPServerList. If there is a DNS entry in the default domain for ExtremeZIPServerList, then Macintosh clients ask that server for a list of all the Access Connect servers on the network. They then query each server individually for its default zone or location and any print queues that it hosts.
Because the Access Connect Zidget uses standard HTML and XML, the administrators can use this protocol to create their own web interfaces as well. More details about how to do this can be found in the Zidget section of the manual.
Enter the port used for client server communication between the server and Zidget and Print Accounting.
Note: Even if you turn off Zidget/HTTP Access Connect still uses this port to support the legacy Access Connect Print Components and Print Accounting. Only the new features are disabled.
Zidget supports connecting to a single master server to discover the other Access Connect servers on the network. By default this is set to ExtremeZIPServerList. It is recommended that you keep this setting and create a CNAME record in DNS pointing to the host name of your master server. You can change it to any server name listed in the DNS.
This field specifies the location of the server. It is similar to an AppleTalk zone, but allows for multi-level hierarchies. The location is also the default location of print queues on the server, but you can assign a different location on a queue by queue basis. Zidget groups the AFP Server and print queue display based on location. If you want to have a hierarchy of locations, such as 1100 N. Glebe RD, Arlington, Virginia, enter the locations separated by colons (“Virginia:Arlington:1100 N. Glebe RD”).
The optional description for the server. Zidget displays this description when the user selects a file server.
With SLP, Mac OS 9 users can see volumes and print queues in the Network Browser. Type the name of the SLP scope (or Neighborhood) in which you want the file server to appear when Mac OS 9 clients use the Network Browser. Type a host name, which is the name of the server provided to Macintosh clients when they use the Network Browser.
This option allows Access Connect to publish its existence using a Microsoft Service Connection Point (SCP). This technology is used to locate and contact other Access Connect servers in your Active Directory.