Frequently Asked Questions

The following FAQ provides answers to common concerns; additional resources for assessment guidelines, migration paths and options, further information regarding this discontinuation. If your concerns or questions are not answered by this document, you may contact appletalk@mit.edu for further assistance.

1) How will this change affect? Should I be concerned?

Discontinuation of AppleTalk routing on MITnet will affect anyone who is using networked applications and services dependent on the AppleTalk protocol and AppleTalk routing across AppleTalk zones at MIT.

Typically, this change will affect users on Apple Macintosh platforms who utilize file sharing and printing services on servers and printers outside of their subnet (building) via AppleTalk, but this impact will not be limited to them. Windows NT 4 and Windows 2000 users who utilize printing services on printers outside their subnet (building) via AppleTalk will similarly be unable to continue doing the same.

Naturally, the providers of these file sharing and printing services, some of who may be on non-Apple Macintosh platforms such as Windows NT 4 and Solaris, will also be affected. Thus, there are migration concerns on both the user and system administrator fronts.

2) What will change? What will I see differently?

After AppleTalk routing has been discontinued, AppleTalk zones will no longer be visible to network browsing applications. For example, under Classic MacOS (v8.x - 9.x), these are the Chooser or Network Browser applications used to connect to file servers and setup printers.

You will continue to be able to see and browse file servers and printers within the same local AppleTalk zone, i.e. on the same physical subnet in your building. However, using the AppleTalk protocol to connect to these devices will no longer be supported by Information Systems.

You will not lose the ability to access the same file sharing and printing services regardless of where they are on MITnet, assuming these devices are configured or migrated to allow access using the TCP/IP protocol by their system administrators, as necessary. You may lose the ability to use graphical interfaces to browse available servers and printers, but will be able to continue using file sharing and printing, albeit through slightly different methods to log on or to configure them.

System administrators maintaining/supporting file sharing, printing and other services that support only the AppleTalk protocol (and especially those who have users who need to access them across other subnets/buildings), such as Services for Macintosh on Windows NT 4, will need to migrate to TCP/IP based solutions.

3) What areas of the campus or MITnet will be affected?

Discontinuation of AppleTalk routing will affect all of MITnet, including all current AppleTalk zones, subnets and buildings. After the phase-out commences in September of 2002 and as it proceeds, updated information on discontinued service and affected areas will be posted to these pages.

4) When will the discontinuation happen? What is the cut-off date?

As indicated earlier in these pages, the phase-out will begin in September 2002, with a target cut-off date of December 31, 2002 when AppleTalk routing will no longer be available on MITnet.

5) How will the discontinuation occur? Will we be notified?

The discontinuation will be conducted in three phases as delineated earlier in these pages. The process will begin with the discontinuation of new AppleTalk zone creation on MITnet, followed by gradual disabling of AppleTalk routing across the campus leading to the final cut-off date on December 31, 2002.

6) Why is this being done?

The need to discontinue AppleTalk routing on MITnet is based on a combination of changing industry trends which both limit the availability of AppleTalk capable hardware--hardware otherwise crucially needed to maintain and enhance the campus network--and show steadily decreasing support for AppleTalk in the enterprise. More detailed explanation of the reasoning behind this decision has been delineated earlier in this document and a variety of peer institutions that have already completed similar projects are available in the "Similar projects at other universities section".

7) Does your Department support a FileMaker Pro database or Meeting Maker service?

Those Departments who share a FileMaker Pro database with more than one person, should confirm that access to their server is done via TCP/IP and not AppleTalk methods.

Departments who offer a Meeting Maker service, should please ensure that users are accessing the service via TCP/IP or TCP and not AppleTalk.