AppleTalk support statement
The AppleTalk network protocol was a simple and effective language for small-scale networks. It has been used for file and print services, as well as inter-application communication, since the eighties. However, its usefulness can be outweighed today by other factors on large networks like RIT’s.
In evaluating continued support of AppleTalk routing on the campus network since 2003, ITS has come to the conclusion that the summer of 2006 is the appropriate time to phase out AppleTalk routing.
As of July 24, 2006, AppleTalk routing will no longer be available on the RIT campus network. This does not disable or prevent the use of AppleTalk, but it does prevent the traffic from going across network segment boundaries or traversing the RIT backbone. ITS will also end all troubleshooting support for AppleTalk at this time.
What does this mean? For the current generation of computers and devices that might have relied upon AppleTalk in the past, this change should not be an issue. Apple Mac OS X, which was released in 2001, has definitely broken with the AppleTalk tradition and no longer even enables the AppleTalk protocol by default. Even classic Mac OS also relied less heavily on AppleTalk by the time of Mac OS 8 and 9. Printers, print servers, and even applications such as FileMaker Pro have all been able to tap into the power of Internet protocols for many years. ITS has been assisting customers in the move beyond AppleTalk for much of this decade.
Therefore, we do advise anyone still needing to use AppleTalk to contact us for alternatives. (See below for how to determine if you are using AppleTalk.) Almost all file, print, and application services have some Internet-ready, IP-based, substitute. In fact, you’re probably already using them. In many cases, they improve on what was available through the use of AppleTalk. IP-based alternatives are generally faster than their AppleTalk equivalents. They rely on Internet standards for broader reach and compatibility.
Implications of the end of AppleTalk routing
Some implications of this change:
- Legacy operating systems and devices that only support AppleTalk should be replaced if at all possible. If they cannot be replaced, they need to be placed on the RIT network with forethought.
- As long as any two legacy AppleTalk devices are within the same network segment, AppleTalk communications between them will still work. However, after July 24, 2006, the addresses change because AppleTalk zones will no longer be present.
- There will no longer be a way to use two AppleTalk-only devices between campus buildings, and in many cases, between hallways within buildings.
- If you are browsing for AppleTalk resources, you will no longer see zones, such as the “GEM Bldg Zone” or “JE Booth Bldg Zone.”
- You will not be able to connect with AppleTalk resources that were previously in a different zone, unless you can switch to an IP-based protocol.
- Devices that were within your own AppleTalk zone may also be inaccessible, because multiple network segments were often combined into one zone.
Since 2003, AppleTalk has only been activated by request for subnets where there was a demonstrated need (with no reasonable IP-based alternatives) for this network service. AppleTalk was never routed on the RIT residential network, dial-in services, Virtual Private Network (VPN), or the wireless network.
How do I know if I’m connecting using AppleTalk?
The following instructions assume you are using Mac OS X.
File servers
To check each file server share point connection:
- Single-click on the icon of a file server share point on your Desktop to highlight it.
- Choose “Get Info” from the File menu. The “Get Info” window appears.
- Examine the “Server” field in the “Get Info” window. If it contains:
- a URL that begins with “afp://,” then you are using AFP over IP, not AppleTalk
- a URL that begins with “cifs://,” then you are using SMB/CIFS (a protocol most commonly used on Microsoft Windows), not AppleTalk
- anything else—especially an AppleTalk zone name such as “Bausch & Lomb Bldg Zone”—then you may be using AppleTalk.
- a URL that begins with “afp://,” then you are using AFP over IP, not AppleTalk
Repeat the steps for each file share point you access.
If you have any file share points using AppleTalk connections, you may:
- refer to our instructions on how to Connect to a file server with Mac OS X
- contact us for assistance.
Printer queues
To check each printer queue defined in the "Printer Setup Utility application":
- Launch the Printer Setup Utility. It is found in your “Utilities” folder, and can also be opened from the “Print & Fax” pane in the System Preferences application.
- Highlight a printer queue in the list.
- Click the “Get Info” button in the toolbar. A “Printer Info” window opens.
- Examine the “Printer Info” window so see if the “Location” field displays the name of an AppleTalk zone, such as the “FE Gannett Bldg Zone.” If it does, this printer queue uses AppleTalk, and will need to be switched to an IP-based protocol.
If you have any printer queues using AppleTalk connections, you may:
- refer to our instructions on how to Connect to a printer with Mac OS X
- contact us for assistance.
Application sharing
In the unlikely event you are using AppleTalk-based application sharing, please contact us. We cannot provide any rules to determine whether you are using AppleTalk for this or not, but the good news is that it was rare even under classic Mac OS.
The most common usage of this in the past was with the FileMaker Pro database application. FileMaker has offered IP-based application sharing for many versions. (Refer to our Share FileMaker Pro databases page.)