Thread
Need help connecting PowerBook 230 to a LAN and to the Web
Hi! I'm new to this forum, and new to old Macintosh machines, but not new to networking and computers. I was recently given the following equipment, and now I have a challenge for you:
Apple PowerBook 230
Duo Dock
AsanteTalk Ethernet to LocalTalk Bridge
All of the equipment works, as far as I can tell. Right now I have the PowerBook in the Duo Dock, a LocalTalk cable connecting the Duo Dock's "printer" port to the AsanteTalk device, and a standard ethernet cable connecting the AsanteTalk device to my 10/100 mbps LAN (which has a variety of Linux and Windows machines on it).
That's where I am. Here are some things I'd like to be able to do, if possible:
1. Print from the PowerBook in its dock to a printer on my LAN. Note that the printers on my LAN have no idea what a Macintosh is, or what LocalTalk is... they expect to be printed to by Linux or Windows machines.
2. Transfer files between the PowerBook and Linux or Windows computers on my LAN
3. Install browser software on the PowerBook and somehow connect it to the Internet, so it can be used to browse the Web.
Are any of these things possible?
Any suggestions?
Please forgive that I really, really don't know anything about Macs. I really, really wanted one back in the early 1990's but couldn't afford one. So I became a Windows and eventually a Linux enthusiast. But it would be really cool to get this cute little Apple machine doing real stuff!
Dave
Apple PowerBook 230
Duo Dock
AsanteTalk Ethernet to LocalTalk Bridge
All of the equipment works, as far as I can tell. Right now I have the PowerBook in the Duo Dock, a LocalTalk cable connecting the Duo Dock's "printer" port to the AsanteTalk device, and a standard ethernet cable connecting the AsanteTalk device to my 10/100 mbps LAN (which has a variety of Linux and Windows machines on it).
That's where I am. Here are some things I'd like to be able to do, if possible:
1. Print from the PowerBook in its dock to a printer on my LAN. Note that the printers on my LAN have no idea what a Macintosh is, or what LocalTalk is... they expect to be printed to by Linux or Windows machines.
2. Transfer files between the PowerBook and Linux or Windows computers on my LAN
3. Install browser software on the PowerBook and somehow connect it to the Internet, so it can be used to browse the Web.
Are any of these things possible?
Any suggestions?
Please forgive that I really, really don't know anything about Macs. I really, really wanted one back in the early 1990's but couldn't afford one. So I became a Windows and eventually a Linux enthusiast. But it would be really cool to get this cute little Apple machine doing real stuff!
Dave
What kind of Linux machine?
The quickest start with be
(a) install "netatalk" on the Linux box and used "papd" for printing. You could use ghostprint to pretend to the Mac that you are really a networked laserwriter. You would also be able to configure an AppleShare server on the Linux box. The Linux kernel needs AF_APPLETALK support enabled.
( B) workout how to use the localtalk/ethernet bridge, they can be pedantic, best results seem to be if you power up that device last.
© getting TCP going on the Mac would be the hardest, as you need a Mac-IP gateway running somewhere. I run one on my NetBSD gateway box which does the packing and unpacking of IP packets from DDP.
Hopefully that helps.
The quickest start with be
(a) install "netatalk" on the Linux box and used "papd" for printing. You could use ghostprint to pretend to the Mac that you are really a networked laserwriter. You would also be able to configure an AppleShare server on the Linux box. The Linux kernel needs AF_APPLETALK support enabled.
( B) workout how to use the localtalk/ethernet bridge, they can be pedantic, best results seem to be if you power up that device last.
© getting TCP going on the Mac would be the hardest, as you need a Mac-IP gateway running somewhere. I run one on my NetBSD gateway box which does the packing and unpacking of IP packets from DDP.
Hopefully that helps.
Once you do get the thing networked, here are some suggestions for suitable browsers. As you might suspect, your choices are somewhat limited. Don't expect modern webpages to render well. 
A fast, text-only browser is wannabe68k. I have used it on my Duos on dialup.
If you must browse with pictures, then consider netscape (versions 2 and 3). It will function, for suitably generous definitions of "function." Perhaps even version 4 will run, but its large memory footprint will pose a challenge.
The oldest functioning version of iCab presumably will also run on a 230, as long as you're running system 7.5 or above. I've never tried this myself, however, so I do not know for certain.
A fast, text-only browser is wannabe68k. I have used it on my Duos on dialup.
If you must browse with pictures, then consider netscape (versions 2 and 3). It will function, for suitably generous definitions of "function." Perhaps even version 4 will run, but its large memory footprint will pose a challenge.
The oldest functioning version of iCab presumably will also run on a 230, as long as you're running system 7.5 or above. I've never tried this myself, however, so I do not know for certain.
ISTR that the Asante bridges must speak to a 10MB hub and not a 10/100.
My PowerBook 230 is running "System 7.1". I have no idea how or where to find "System 7.5". I don't have any system floppy disks or anything like that for the PowerBook. What is "iCab"?
Even browsing through my LAN's connection to the internet from the PowerBook 230 without pictures would be an accomplishment! Right now I have *no way at all* to move files between the PowerBook and other computers, except possibly by use of the PowerBook's analog modem.
On my Linux machines I am running ubuntu 8.10, variously 32-bit and 64-bit. I will look into the "netatalk" and "papd" programs.
I wonder if there is a "Mac-IP gateway" that will run on ubuntu?
Even browsing through my LAN's connection to the internet from the PowerBook 230 without pictures would be an accomplishment! Right now I have *no way at all* to move files between the PowerBook and other computers, except possibly by use of the PowerBook's analog modem.
On my Linux machines I am running ubuntu 8.10, variously 32-bit and 64-bit. I will look into the "netatalk" and "papd" programs.
I wonder if there is a "Mac-IP gateway" that will run on ubuntu?
I'm not sure why the AsanteTalk bridge would need to talk to a 10 mbps hub instead of to the 10/100 mbps switch I currently have it connected to, but I'll give the idea a test. I have lots of old 10 mbps-only equipment around here.
Depends how keen you are to try and compile my code.
I'm certainly willing to attempt compilation of code, but if the compilation is to be on the PowerBook 230 running System 7.1, I may need some help figuring out how to do it. Forgive my ignorance, porter, but what code have you written?
My recent compilation experience is primarily with Microsoft C, Visual Basic, and Visual C++ running on Windows. I have done some compilation on Linux machines also, but mostly following "cookbook" instructions when doing so.
This week I hope to find time to install and get netatalk running.
My recent compilation experience is primarily with Microsoft C, Visual Basic, and Visual C++ running on Windows. I have done some compilation on Linux machines also, but mostly following "cookbook" instructions when doing so.
This week I hope to find time to install and get netatalk running.
It's a Mac-IP gateway that runs on a netatalk enabled UNIX host. It's a C daemon that uses AF_APPLETALK sockets to talk DDP, then uses a secondary process to translate those IP packets to the UNIX host. I run mine on NetBSD, it compiles on Linux, but has not been tested.
What's wrong with Netatalk?Depends how keen you are to try and compile my code.
As for transferring files: You have a Duo Dock - therefore you have SCSI (for external SCSI drives - like a ZIP for example, and a matching parallel or USB ZIP for a PC) and a floppy drive - the Mac can read PC-formatted floppies. If you download compressed files on the PC and put the compressed file on a floppy, then uncompress them on the Mac, you should be fine.
Netatalk provides AFP and PAP over DDP.
My gateway provides MacIP over DDP, using Netatalk's NBP.
I unfortunately do not possess any cables that connect to the SCSI port on the Duo Dock. I have some SCSI CD-ROM drives, hard disks, and even a few tape drives, but all SCSI cables I have are for the "Centronics"-style or IBM-style SCSI connectors.
I am encouraged to read that the Macintosh can read "PC-formatted" (1.44MB?) 3.5" floppy disks... I didn't know this was possible.
I presume from porter's last post that I will need to get netatalk working before I attempt to add his gateway. I hope to work on this soon.
I am encouraged to read that the Macintosh can read "PC-formatted" (1.44MB?) 3.5" floppy disks... I didn't know this was possible.
I presume from porter's last post that I will need to get netatalk working before I attempt to add his gateway. I hope to work on this soon.
Yes, I use netatalk's name binding daemon, on IRIX I use KTalk and Darwin/MacOSX/AUX I use the native OS nbp. Alas on AUX there is no simple way of programmatically getting IP packets in and out of the UNIX box itself.
I hope this thread doesn't turn into "how to setup netatalk", but I must admit after perusing the "manual" for the program and playing around a bit without success I am unsure what to do. On my Linux box (ubuntu 8.10 64-bit) I have netatalk installed. lsmod shows the "appletalk" module loaded. The Linux box is connected to a 10/100 switch alongside my AsanteTalk module, which in turn is connected via a mini-DIN8 cable to the "printer" port on the Duo Dock. The "link integrity" LED on the AsanteTalk is glowing green, and the switch "sees" the link to it as well.
The printer I would like to allow the PowerBook 230 (System 7.1) in the Duo Dock print to is on the same subnet of the LAN as the above two devices. The Linux box can print to it, of course. When I invoke "Chooser" on the PowerBook, and then click on "AppleShare" I am shown an empty box in which to "select a file server", and below that a radiobutton indicating that AppleTalk is Active.
I do not know how to:
- tell netatalk to share the printer that it knows how to print to with a LocalTalk network
- determine if netatalk is even aware of the AsanteTalk box and its attached LocalTalk network
- tell the PowerBook to try to print to a printer on the LocalTalk network, or even that a printer exists on it
The other options I seen in Chooser are:
AppleTalk ImageWriter
ImageWriter
LaserWriter
LQ AppleTalk ImageWriter
LQ ImageWriter
Personal LaserWriter SC
Personal LW LS
StyleWriter
Each of them leads to a similar blank list in which I am to "select an AppleTalk ImageWriter" or something similar.
My guess is that I need to somehow configure netatalk to advertise the availability of a printer to the LocalTalk network as if it was some kind of printer that the PowerBook knows how to print to. I further guess that I need to put a line or two into atalkd.conf and/or papd.conf, but I am clueless about what lines I need. I know the details of the printer I would like to share:
Brother DCP-9040CN color laser printer
lpd://192.168.1.213
Brother offers drivers for MacOS X on its website, for what that is worth.
The printer I would like to allow the PowerBook 230 (System 7.1) in the Duo Dock print to is on the same subnet of the LAN as the above two devices. The Linux box can print to it, of course. When I invoke "Chooser" on the PowerBook, and then click on "AppleShare" I am shown an empty box in which to "select a file server", and below that a radiobutton indicating that AppleTalk is Active.
I do not know how to:
- tell netatalk to share the printer that it knows how to print to with a LocalTalk network
- determine if netatalk is even aware of the AsanteTalk box and its attached LocalTalk network
- tell the PowerBook to try to print to a printer on the LocalTalk network, or even that a printer exists on it
The other options I seen in Chooser are:
AppleTalk ImageWriter
ImageWriter
LaserWriter
LQ AppleTalk ImageWriter
LQ ImageWriter
Personal LaserWriter SC
Personal LW LS
StyleWriter
Each of them leads to a similar blank list in which I am to "select an AppleTalk ImageWriter" or something similar.
My guess is that I need to somehow configure netatalk to advertise the availability of a printer to the LocalTalk network as if it was some kind of printer that the PowerBook knows how to print to. I further guess that I need to put a line or two into atalkd.conf and/or papd.conf, but I am clueless about what lines I need. I know the details of the printer I would like to share:
Brother DCP-9040CN color laser printer
lpd://192.168.1.213
Brother offers drivers for MacOS X on its website, for what that is worth.
First step with netatalk is "is it running?" It starts with a daemon
eg on my box this is
which is normally self configuring.
The first program to see what else is on the appletalk network is
This will probe the network to see what names have been registered.
eg, mine, with nothing else running on the net says
The ADSP is my ADSP terminal server so you can log onto the gateway using the "ADSP Tool". IPADDRESS and IPGATEWAY are my macipd ready for duty. The last two are registered by netatalk itself, here on the echo socket.
You need to go through a configuration phase with any file sharing to say what you want shared.
eg on my box this is
Code:
/usr/pkg/libexec/netatalk/atalkdThe first program to see what else is on the appletalk network is
Code:
/usr/pkg/bin/nbplkupeg, mine, with nothing else running on the net says
Code:
$ nbplkup
gateway:ADSP 65280.94:128
10.1.3.1:IPADDRESS 65280.94:72
10.1.3.1:IPGATEWAY 65280.94:72
gateway:netatalk 65280.94:4
gateway:Workstation 65280.94:4You need to go through a configuration phase with any file sharing to say what you want shared.
At present my netatalk configuration files (atalkd.conf and papd.conf) contain nothing but commented-out lines. When I execute the commands atalkd and nbplkup on my Linux box, this is what I get:
dave@quad:/$ atalkd
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/$ nbplkup
quad:AFPServer 65280.8:128
quad:netatalk 65280.8:4
quad:Workstation 65280.8:4
dave@quad:/$
dave@quad:/$ atalkd
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/$ nbplkup
quad:AFPServer 65280.8:128
quad:netatalk 65280.8:4
quad:Workstation 65280.8:4
dave@quad:/$
Sounds like it's up and ready for business, unless your running atalkd killed the one that is already running.
If you go to the Chooser on a mac and select file server it should at least list "quad".
Does "netstat -a" list the appletalk sockets?
Eg on my NetBSD box I get
Code:
Active ATALK connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
ddp 0 0 65280.94.128 *.*.*
ddp 0 0 65280.94.72 *.*.*
ddp 0 0 65280.94.1 *.*.*
ddp 0 0 65280.94.2 *.*.*
ddp 0 0 65280.94.4 *.*.*
ddp 0 0 65280.94.6 *.*.*
ddp 0 0 *.*.1 *.*.*
ddp 0 0 *.*.2 *.*.*
ddp 0 0 *.*.4 *.*.*
ddp 0 0 *.*.6 *.*.*
Well, Chooser still shows me nothing. I also do not see the appletalk sockets:
dave@quad:/home$ netstat -i
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 51182 60 0 0 33413 0 0 0 BMRU
lo 16436 0 851 0 0 0 851 0 0 0 LRU
dave@quad:/home$ netstat -a | grep ddp
dave@quad:/home$ netstat -a | grep DDP
dave@quad:/home$ netstat -a | grep ATALK
dave@quad:/home$ atalkd
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/home$
Possibly I should add the line "eth0" to my atalkd.conf file?
dave@quad:/home$ netstat -i
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 51182 60 0 0 33413 0 0 0 BMRU
lo 16436 0 851 0 0 0 851 0 0 0 LRU
dave@quad:/home$ netstat -a | grep ddp
dave@quad:/home$ netstat -a | grep DDP
dave@quad:/home$ netstat -a | grep ATALK
dave@quad:/home$ atalkd
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/home$
Possibly I should add the line "eth0" to my atalkd.conf file?
"atalkd" is the netatalk daemon so should only be run once, and it should keep going.
If you only have one network interface atalk should work things out, how many do you have?
Also, if you have other macs on the network, running "nbplkup" should show up those other macs.
Here is "nbplkup" run from my gateway, and sees another netatalk box..
Code:
$ nbplkup
gateway:ADSP 65280.94:128
10.1.3.1:IPADDRESS 65280.94:72
10.1.3.1:IPGATEWAY 65280.94:72
gateway:netatalk 65280.94:4
gateway:Workstation 65280.94:4
saxon:AFPServer 65280.152:128
saxon:netatalk 65280.152:4
saxon:Workstation 65280.152:4"saxon" is Ubuntu, neither ifconfig or netstat show ddp sockets.
Whereas on NetBSD you get
Code:
rtk1: flags=8843 mtu 1500
media: Ethernet autoselect (none)
status: active
......
atalk 65280.94 range 1-65534 phase 2 broadcast 65280.94
I'm beginning to wonder if the problem is either in the AsanteTalk device or in the PowerBook or Duo Dock.
I added "eth0" to my atalkd.conf file and restarted my Linux box. Now I get:
dave@quad:/etc/netatalk$ atalkd
eth0: Operation not permitted
Can't configure multicast.
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/etc/netatalk$ nbplkup
quad:AFPServer 65280.108:128
quad:netatalk 65280.108:4
quad:Workstation 65280.108:4
dave@quad:/etc/netatalk$ aecho quad:Workstation
22 bytes from 65280.108: aep_seq=0. time=0. ms
22 bytes from 65280.108: aep_seq=1. time=0. ms
22 bytes from 65280.108: aep_seq=2. time=0. ms
^C
----65280.108 AEP Statistics----
3 packets sent, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
dave@quad:/etc/netatalk$
Can you help me figure out how to diagnose the LocalTalk portion of my system?
I added "eth0" to my atalkd.conf file and restarted my Linux box. Now I get:
dave@quad:/etc/netatalk$ atalkd
eth0: Operation not permitted
Can't configure multicast.
eth0: multicast may not work correctly.
eth0: disabled.
atalkd: zero interfaces, exiting.
dave@quad:/etc/netatalk$ nbplkup
quad:AFPServer 65280.108:128
quad:netatalk 65280.108:4
quad:Workstation 65280.108:4
dave@quad:/etc/netatalk$ aecho quad:Workstation
22 bytes from 65280.108: aep_seq=0. time=0. ms
22 bytes from 65280.108: aep_seq=1. time=0. ms
22 bytes from 65280.108: aep_seq=2. time=0. ms
^C
----65280.108 AEP Statistics----
3 packets sent, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
dave@quad:/etc/netatalk$
Can you help me figure out how to diagnose the LocalTalk portion of my system?
I have no other Macs on my network, and netatalk is only installed on this one Linux machine (quad).
The best bet is to....
Make sure you are using proper LocalTalk cabling to the AsanteTalk box, not just a serial/printer cable.
Switch off the AsanteTalk box.
Start the linux box with netatalk.
Start the mac with LocalTalk/AppleTalk enabled on the printerport
Then once the machine has started up, powerup the AsanteTalk box.
Try nbplkup from the linux box.
Go the the control panel and select AppleTalk or Network depending on if you are OpenTransport or classic and see if that says anything different.
I've had varying success with the AsanteTalk box, it seems to work best when there is an appletalk router already on the network.
If you already have a Mac with ethernet, the control panel "LocalTalk Bridge" seems to work better than the AsanteTalk box.
Here is a good example:
Which shows
(a) Macintosh Classic running System 6 on 40000.16
( B) Compaq running W2K server on 41384.136
© gateway running NetBSD on 40215.94
(d) AsanteTalk on 40000.15
Note MacTCP running with gateway as server, and classic allocated an address.
Code:
$ nbplkup
gateway:ADSP 40215.94:128
10.1.3.1:IPADDRESS 40215.94:72
10.1.3.1:IPGATEWAY 40215.94:72
gateway:netatalk 40215.94:4
gateway:Workstation 40215.94:4
EVO:DceDspRpc DynEpt 638.1 41384.136:136
EVO:DceDspRpc DynEpt 114.1 41384.136:129
EVO:DceDspRpc Endpoint Mapper 41384.136:130
EVO:AFPServer 41384.136:131
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Prt 44318.148:2
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Rtr 43497.215:2
Asant?Talk 94AFE828:AsantTalk 40000.15:252
10.1.3.2:IPADDRESS 40000.16:72
porter:Macintosh Classic 40000.16:253(a) Macintosh Classic running System 6 on 40000.16
( B) Compaq running W2K server on 41384.136
© gateway running NetBSD on 40215.94
(d) AsanteTalk on 40000.15
Note MacTCP running with gateway as server, and classic allocated an address.
I have an interesting catch-22.
I can't use AsanteTalk unless I have an AppleTalk seed/router on the ethernet. I'm using my win2k box to do that.
I can use MacTCP from Classic thru AsanteTalk to NetBSD to my MacIP gateway. (tested with Browser6 of course).
But my Ubuntu box refuses to start netatalk when the win2k box is up claiming
when I start atalkd.
Now you may be able to start atalkd on the Linux box as a seed on the network to get the AsanteTalk box to grab an address in a reasonable range. Perhaps I should try that.
I can't use AsanteTalk unless I have an AppleTalk seed/router on the ethernet. I'm using my win2k box to do that.
I can use MacTCP from Classic thru AsanteTalk to NetBSD to my MacIP gateway. (tested with Browser6 of course).
But my Ubuntu box refuses to start netatalk when the win2k box is up claiming
Code:
Jan 28 19:18:43 saxon kernel: [ 992.358470] Too many routes/iface.Now you may be able to start atalkd on the Linux box as a seed on the network to get the AsanteTalk box to grab an address in a reasonable range. Perhaps I should try that.
I shutdown the win2k box and the gateway.
Okay, now I have started up the Linux box first then started up the classic with the AsanteTalk.
I get a weird looking output from nbplkup on linux...
Note, the classic can now see the Linux box in the Chooser.
When I startup the NetBSD one I get
Which looks alot nicer, and classic can still see Linux box in Chooser.
Now when I fireup the win2k box with the seed the Linux box disappears from the Chooser, and nbplkup fails with
Now we can see that the AsanteTalk box has correctly switched address now the network has been seeded. The NetBSD box didn't, and the Linux box has collapsed in a heap.
I'm happily able to mount the win2k share from the Chooser.
However now the MacTCP gateway is broken until I reset the gateway box.
So, gateway is reset...
And bingo the MacIP gateway works...
Upshot is I think the Ubuntu netatalk is shagged.
Okay, now I have started up the Linux box first then started up the classic with the AsanteTalk.
I get a weird looking output from nbplkup on linux...
Code:
root@saxon:/etc/init.d# nbplkup
saxon:AFPServer 65280.249:128
saxon:netatalk 65280.249:4
saxon:Workstation 65280.249:4
AsantéTalk 94AFE828: porter:Macintosh Classic 65397.152:253When I startup the NetBSD one I get
Code:
bash-3.00# nbplkup
gateway:ADSP 65280.94:128
10.1.3.1:IPADDRESS 65280.94:72
10.1.3.1:IPGATEWAY 65280.94:72
gateway:netatalk 65280.94:4
gateway:Workstation 65280.94:4
saxon:AFPServer 65280.249:128
saxon:netatalk 65280.249:4
saxon:Workstation 65280.249:4
porter:Macintosh Classic 65397.152:253
Asant?Talk 94AFE828:AsantTalk 65397.151:252Now when I fireup the win2k box with the seed the Linux box disappears from the Chooser, and nbplkup fails with
Code:
nbp_lookup: Cannot assign requested address
Code:
bash-3.00# nbplkup
gateway:ADSP 65280.94:128
10.1.3.1:IPADDRESS 65280.94:72
10.1.3.1:IPGATEWAY 65280.94:72
gateway:netatalk 65280.94:4
gateway:Workstation 65280.94:4
EVO:DceDspRpc DynEpt 114.1 41384.136:129
EVO:DceDspRpc Endpoint Mapper 41384.136:130
EVO:AFPServer 41384.136:131
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Prt 44318.148:2
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Rtr 43497.215:2
porter:Macintosh Classic 40000.112:253
Asant?Talk 94AFE828:AsantTalk 40000.111:252However now the MacTCP gateway is broken until I reset the gateway box.
So, gateway is reset...
Code:
bash-3.00# nbplkup
gateway:ADSP 43797.94:128
10.1.3.1:IPADDRESS 43797.94:72
10.1.3.1:IPGATEWAY 43797.94:72
gateway:netatalk 43797.94:4
gateway:Workstation 43797.94:4
EVO:DceDspRpc DynEpt 614.1 41384.136:136
EVO:DceDspRpc DynEpt 114.1 41384.136:129
EVO:DceDspRpc Endpoint Mapper 41384.136:130
EVO:AFPServer 41384.136:131
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Prt 44318.148:2
083D86B6F0E990040330A5CA083D@EVO:Microsoft¨ Windows 2000ª Rtr 43497.215:2
porter:Macintosh Classic 40000.112:253
Asant?Talk 94AFE828:AsantTalk 40000.111:252
Code:
Asant?Talk 94AFE828:AsantTalk 40000.111:252
porter:Macintosh Classic 40000.112:253
10.1.3.2:IPADDRESS 40000.112:72Qualification: .... when another network seed is used.
See comments below, interspersed in a message porter sent earlier... my text is hopefully in italics.
The best bet is to....
Make sure you are using proper LocalTalk cabling to the AsanteTalk box, not just a serial/printer cable.
I have only one mini-DIN8 cable. I hope it is the correct type. It was given to me along with the PowerBook, and had been used to connect the PowerBook to a LaserWriter printer in the past. I could check continuity of the cable with an ohmmeter, but I suspect it is OK. Note I do not have "terminating resistors" on either the PowerBook end or the AsanteTalk end of this cable, in case that likely matters.
Switch off the AsanteTalk box.
Done
Start the linux box with netatalk.
Done
Start the mac with LocalTalk/AppleTalk enabled on the printerport
Here's where I may need help confirming I have this step done correctly. When I power on the PowerBook, and then click Control Panels | Network, I see only one item, an icon labeled "LocalTalk Built-In". Clicking on this icon does nothing. When I open Chooser, and then click on "AppleShare", on the right hand side of the window I see: "Select a file server:" above a blank rectangle, above an OK button, above a pair of radiobuttons... "AppleTalk" is "Active".
Then once the machine has started up, powerup the AsanteTalk box.
When the AsanteTalk device is powered up, the PWR and Li (link) LEDs immediately turn green, and the TX and RX LEDs begin flashing irregularly, as if the AsanteTalk is communicating with something.
Try nbplkup from the linux box.
nbplkup returns exactly the same response as it did before I powered on the AsanteTalk device:
dave@quad:/$ nbplkup
quad:AFPServer 65280.108:128
quad:netatalk 65280.108:4
quad:Workstation 65280.108:4
dave@quad:/$
Go the the control panel and select AppleTalk or Network depending on if you are OpenTransport or classic and see if that says anything different.
Clicking on Control Panels | Network produces the same result as it did before I turned on the AsanteTalk device. I do not see an icon in Control Panels called "AppleTalk".
I've had varying success with the AsanteTalk box, it seems to work best when there is an appletalk router already on the network.
Sadly, I do not have such a thing, unless that's what my Linux box is providing.
If you already have a Mac with ethernet, the control panel "LocalTalk Bridge" seems to work better than the AsanteTalk box.
I do not have any other Macintosh computers, either with or without ethernet. I also do not have any LocalTalk printers.
The best bet is to....
Make sure you are using proper LocalTalk cabling to the AsanteTalk box, not just a serial/printer cable.
I have only one mini-DIN8 cable. I hope it is the correct type. It was given to me along with the PowerBook, and had been used to connect the PowerBook to a LaserWriter printer in the past. I could check continuity of the cable with an ohmmeter, but I suspect it is OK. Note I do not have "terminating resistors" on either the PowerBook end or the AsanteTalk end of this cable, in case that likely matters.
Switch off the AsanteTalk box.
Done
Start the linux box with netatalk.
Done
Start the mac with LocalTalk/AppleTalk enabled on the printerport
Here's where I may need help confirming I have this step done correctly. When I power on the PowerBook, and then click Control Panels | Network, I see only one item, an icon labeled "LocalTalk Built-In". Clicking on this icon does nothing. When I open Chooser, and then click on "AppleShare", on the right hand side of the window I see: "Select a file server:" above a blank rectangle, above an OK button, above a pair of radiobuttons... "AppleTalk" is "Active".
Then once the machine has started up, powerup the AsanteTalk box.
When the AsanteTalk device is powered up, the PWR and Li (link) LEDs immediately turn green, and the TX and RX LEDs begin flashing irregularly, as if the AsanteTalk is communicating with something.
Try nbplkup from the linux box.
nbplkup returns exactly the same response as it did before I powered on the AsanteTalk device:
dave@quad:/$ nbplkup
quad:AFPServer 65280.108:128
quad:netatalk 65280.108:4
quad:Workstation 65280.108:4
dave@quad:/$
Go the the control panel and select AppleTalk or Network depending on if you are OpenTransport or classic and see if that says anything different.
Clicking on Control Panels | Network produces the same result as it did before I turned on the AsanteTalk device. I do not see an icon in Control Panels called "AppleTalk".
I've had varying success with the AsanteTalk box, it seems to work best when there is an appletalk router already on the network.
Sadly, I do not have such a thing, unless that's what my Linux box is providing.
If you already have a Mac with ethernet, the control panel "LocalTalk Bridge" seems to work better than the AsanteTalk box.
I do not have any other Macintosh computers, either with or without ethernet. I also do not have any LocalTalk printers.
Do you think it would help for me to try to upgrade the OS on the PowerBook 230 from "System 7.1" to something newer?
Then it might be an idea to get one, no? IIRC, the Dock has the Honda HDI-50 square Powerbook style SCSI port.
Another option is to mount a bare SCSI drive internally in the Dock - there is space for one. Format it using the Duo, pull it, transfer to a SCSI-equipped PC with MacDrive or some other HFS/HFS+ read/write software on it, drag the files you want over, pull it, remount it in the Dock.
Some Duo Docks came with built-in Ethernet, but it may be a socket type that is unfamiliar to you, called AAUI. Symbol: If there is one, you need an Apple AAUI to Cat-5 adapter to use it.
There are also two Nubus expansion card slots in the Dock, and Nubus ethernet cards are readily available on evilbay, as are the Powerbook SCSI cables and AAUI adapters.
Other than that, see first line of sig below.
It does have to be a pair of LocalTalk connector boxes with localtalk cabling between them, and ideally terminators on each end. A serial cable alas does not work. The little boxes contain an isolating transformer and turn the cabling into a bus.
Try changing your atalk.conf to say something like
Code:
eth0 -phase 2 -seed -net 20000-30000 -addr 20000.10
Code:
man atalkd