Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Snow Leopard means no more Appletalk

This article alleges that the release of Snow Leopard will end support for Appletalk.

Like WDS, it seems Appletalk is a protocol that Apple wishes would just go away on its own. Unfortunately I use it for two of my printers. When Apple discontinues the few lines of code that drive Appletalk, they'll have to add to a landfill's population.

I am not hopeful that anything the user community can do will save this unfortunate victim of progress, but it's worth a try:

http://www.apple.com/feedback/macosx.html

Powerbooks  iMacs  iPods  Airports  Appletalk printers , Mac OS X (10.4.11),  24 years Apple!  "it's" means "it is"  "lose" is a verb  "loose" isn't

Posted on Jul 7, 2009 6:51 AM

Reply
194 replies

Dec 11, 2009 8:10 AM in response to Grant Bennet-Alder

The link I posted above has gone bad. This is the essence of it:

Ping can help you -- either the Mac OS X version in Network Utility or the Terminal version (or OS 9 MacPing). Set up a ping to the LAST address on your local network, with two or more pings, and it acts as a Brodcast Ping and will show all connected Ethernet Addresses. Add or remove the mystery device and Ping again. The difference is the mystery device's Ethernet Address.

Example:
You use 192.168.0.xxx as your local address range, with a subnet mask of 255.255.255.0.
A ping or two to 192.168.0.255 gets all attached devices to respond and show their addresses.

Dec 11, 2009 6:57 PM in response to Grant Bennet-Alder

Thanks!!! You have answered all my questions and I truly appreciate it! I did not investigate the IP for the 8500 because I figured it was going to be a similar problem as the 630 but now I see it is not. I will fire up the printer utility and investigate the IP for the 8500, as well as look into a print server for the 630. I very much appreciate your generosity.

Dec 28, 2009 2:40 PM in response to John Galt

It works! I have a Laserwriter 16/600 and I used a System 9 to fix this problem.

Use the Apple Printer Utility 2.2 in System 9
it allows you to change the IP address of the printer

select «Communication Configuration» tab,
select «TCP/IP» tab, enter «192.168.1.150» in the box beside Printer’s IP Address
and press the button «Set Defaults» at the top of the page.

Now go back to Snow Leopard and add a new printer with this IP address
(Line Printer Daemon – LPD worked for me)
and with the Apple printer driver corresponding to your printer.

Enjoy your old printer again!

Jan 4, 2010 6:57 PM in response to ishiiboy

It's been a long, long day trying to figure this out. I have a completely reliable, well built HP Laserjet 5MP which can connect with either parallel or (current) AppleTalk via AsanteTalk box to ethernet running to AirPort Extreme.

So, the question is... Is it at all possible to configure the AirPort to speak with AsanteTalk box or is any solution involving AppleTalk/Asante box now out the window?

If so, seems a USB to parallel cable is the next logical solution.

Jan 5, 2010 5:02 AM in response to Jason West1

So, the question is... Is it at all possible to configure the AirPort to speak with AsanteTalk box or is any solution involving AppleTalk/Asante box now out the window?


Any solution that requires 10.6 to talk DIRECTLY to the AsanteTalk ...
... is out the window. Correct.

To continue using the AsanteTalk, you would need to use an intermediary computer running an older version of Mac OS X. The older computer would talk directly to the printer through the AsanteTalk and then share the printer back to the 10.6 Mac(s).

Jan 21, 2010 6:10 PM in response to Jason West1

Well, let me clarify my previous comment saying that it "works". It sometimes works. Simple files such as Word documents are not a problem. Adobe Illustrator files with semi-complex images will NOT print. The printer times out on what I consider fairly simple files (which it used to print in a minute or two).

I've tried connecting the USB to parallel directly to the MacPro and my Airport but it doesn't make a difference. My guess is that data is getting bottlenecked in the USB to Parallel conversion. It is not a cheap cable (about $30) and I don't know whether a different brand will make a difference.

This has been a VERY frustrating experience and it appears there's quite a few people going through the same thing. I've been using an Apple since 1982 and this has been a very non-Apple experience.

If anyone has more advice on a solution or a specific brand of cable that works the feedback would be appreciated.

Feb 1, 2010 10:34 PM in response to davlab

How did you know your 16/600 IP address?? I've been trying for weeks off and on to find mine. I had just about concluded that since my LW is connected with an old Apple Ethernet Twisted-Pair Transceiver to my LAN that somehow it didn't have an IP number (I'm nearly clueless on networking). Anyhoe I haven't been able to find my LW IP address and cannot therefore follow your instructions successfully. Trying several guesses as to the final .xxx didn't yield anything workable. I can see that if I did have a good address, it would probably bring on the printer just as you describe. Somebody please give me instructions on how to find (and maybe even manually set?) the printer IP address. I would be eternally greatful. John Hixson

Feb 2, 2010 5:38 AM in response to John Hixson

since my LW is connected with an old Apple Ethernet Twisted-Pair Transceiver to my LAN that somehow it didn't have an IP number ...


The twisted-pair transceiver attaches it to the Ethernet Highway. It does not necessarily make it become an active participant using IP protocol (and give it an IP Address) since you can also be talking AppleTalk-over-Ethernet on that same Ethernet Highway, which does not require the printer to have an IP Address.

The best way to assign an IP Address is using Apple Printer Utility, which can run in "Classic".

If you suspect your printer already has an IP Address, you can use the "Ping" function in Network Utility to ping the last address in your subnet (for a 192.168.0.1 Router with 255.255.255.0 Subnet Mask, the last address is 192.168.0.255) the last address is a "broadcast" address, and if you send two or more pings, all devices should answer. Run the test with and without the printer connected, and the difference should be the printer IP Address.

Sometimes powering up the printer with its cable connected will force it to get an IP Address from your Router.

Feb 3, 2010 12:24 PM in response to Grant Bennet-Alder

Well, OK, partial success anyway! I went back and tried Atchisan's instructions of 12/28 on this forum topic. (Except where he says to "Set Defaults" after entering the 16/600 IP address I want, if I did that the address went back to 0.0.0.0; so I did not use the "Set Defaults" button but used the "Update Info" button instead. The printer seemed to retain its manually assigned address 192.168.2.150.
thereafter.) After finishing this I was able to add the printer to my 10.6.2 MBP using LPD protocol, 192.168.2.150 address, a better than default name, and its own unique driver. However, it still would not print a test doc, giving me a perpetual "printer is busy" error message instead.

So I poked around for a while until I discovered by accident (in the Apple Printer Utility of OS 9 thanks to an old 7600 I've still got) that the 16/600 has to have its ethernet port TCP/IP mode "turned on" and that there is a small switch on its back panel that's involved in this process. Anyway after I got that straightened out, I was able to print again from Snow Leopard.

With regard to pinging the 16/600 now shows up just as you suggested. It did not before, nor would I have expected it to as the address I found on it before changing was 0.0.0.0.

Thanks for the help. John Hixson

Snow Leopard means no more Appletalk

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.