 |
turning off appletalk routing
CNS is encouraging groups and departments to turn off AppleTalk routing in their areas before the September 1st due date.
Turning off AppleTalk before the due date allows departments to receive undivided attention form the AppleTalk Routing Retirement group during the transition. On September 1st, AppleTalk
will be turned off campus wide, and there will not be time to resolve any issues that may result.
Departments that have already turned off AppleTalk routing are:
- Graduate School of Business
- Computer Science
- Chemistry (1 zone spread over 3 subnets)
- School of Education (4 zones, 1 subnet)
The feedback that CNS has received from these departments has been that turning off AppleTalk has not significantly affected the way they operate.
If you would like to speak with members of these departments about their experiences, please submit a HelpSU request. We can then forward contact information to you.
|
|
case study, school of education
To observe the effects of turning off AppleTalk routing, a set of computers and a laser printer were set up on the various
School of Education AppleTalk zones. File Sharing via AppleTalk was enabled on the computers and Desktop Printers were created for the test printer. These systems were left running when
AppleTalk routing was turned off. The effects we saw were as follows:
- The message "Access to your AppleTalk network has been interrupted." This was seen on all of the Classic Macs.
- Machines with file sharing connections to AppleTalk servers outside the local subnet experienced the error message. "Your file server's connection has unexpectedly closed down." This is expected. Once AppleTalk routing is turned off, AppleTalk servers outside the local subnet will become inaccessible. You will need to connect using TCP/IP.
- A machine on the CERAS zone had a disk mounted on a test server set up in the Education zone. Even after AppleTalk routing was turned off, the mounted file server volume was still available. Neither client nor server required rebooting. Bother were running versions of MacOS 8.
- AFS mounting doesn't work now with Classic macs and reports the message "Failed to mount volume home of from server AuthServer#@netserver zone. Macintosh OS error: -5016." Again, this is expected, because AFS mounting under Classic MacOS uses AppleTalk. Users who wish to access AFS directories will need to migrate to OS X and use the AFS mounting features of MacLeland 2.
- Printers remained accessible even if there were originally on different subnets. Users could print to "chosen" printers even after AppleTalk routing was turned off without rebooting either the printer or the computer.
- After AppleTalk routing was disabled, all file servers and printers now appeared in the same "Default" zone in the Chooser.
- We found that Windows 2K servers sometimes needed to be rebooted after AppleTalk routing was disabled. Once rebooted, volumes on these systems were available to local computers via AppleTalk.
Our experience during these tests indicated that the transition was fairly painless. Most systems continued to be able to access local file servers and printers via AppleTalk with no
need for rebooting, rechoosing printers, etc.
|
|
|
