The above paragraph is about AppleSHARE over IP (ASIP), not IP over AppleTALK (MacIP).
I know what you mean when you say AppleShare over IP (ASIP), but others may not. What you mean to say is AppleTalk over TCP/IP. AppleTalk is the protocol name (sort of, each implementation - LocalTalk, EtherTalk, TokenTalk, etc - has it's own particular protocol which is a subset of AppleTalk in general.) Please be more careful in your use of the term ASIP (AppleShare IP). ASIP is NOT AppleShare over IP. ASIP is a product name: AppleShare IP. AppleShare IP is a fantastic server platform if you have a Mac. It lets you do FTP, HTTP, AFP, SMB, email, and print serving. If you install the optional MacDNS, you can run an entire intranet with domain name servers and everything right from a PowerMac.
FWIW, File Sharing in OS 9 incorporates OpenDoor Networks' ShareWay IP Personal. ShareWay IP Personal works similarly to an ASIP server in that it allows AppleTalk traffic to be encapsulated in TCP/IP traffic (AFP - for example, this following link uses TCP/IP to talk to an AppleShare server much like how an "http://"; link uses HTTP to talk to a web server <afp://idisk.mac.com> - if you are on OS 8.5 or later, this should open in the Network Browser app). However, ShareWay IP Personal (and by corollary OS 9's File Sharing via TCP/IP) is by no means as mature or feature rich as ASIP. I'm a user of both. I have maintained several ASIP servers (versions 5 and 6.x) and have been fantastically impressed by ASIP for it's ease of use and powerful features. I also use ShareWay IP Personal on a daily basis. ShareWay IP Personal works, but it's not as slick as ASIP by any means.
Please do not confuse the two.
As for AppleShare Client (the AppleShare icon you pick in the Chooser) being able to connect to an AppleShare IP server (AppleTalk over TCP/IP), this is nothing new. If you have a relatively recent version of OpenTransport (so that your AppleShare Client - independently downloadable from Apple, btw - works with the AppleTalk server), you can do this on System 7.5 or earlier. AppleShare is only indirectly tied to the OS version. However, it wasn't until recently (OpenTransport 2.x?) that AppleShare automatically attempts to connect to your AppleTalk server using TCP/IP FIRST before switching back to whichever is the appropriate AppleTalk protocol (usually EtherTalk). AppleTalk over TCP/IP is noticeably faster than EtherTalk.
Well, OS 8.1 certainly lets me use AppleTalk for TCP/IP *iff* I have a MacIP server configured.
You don't need a MacIP server, but it can help. If you set everything manually it will work without a server. And MacIP works on OT and Classic back to 7.0 or before.
You do need a MacIP server if you want to encapsulate IP packets in AppleTalk packets. There is no other way to do this, especially if you want to hook into a larger IP network like the Internet. (Note that this is not the same as using AppleShare Client to access an AppleShare IP Server.) Since the poster was talking about doing just this, it is misleading to say that a MacIP server (either from Apple, Sustainable SoftWorks(?), or Vicom) is not needed. A MacIP server is absolutely needed to use MacIP. A MacIP server is NOT needed to use AppleTalk over TCP/IP. The two are reciprocals of each other. MacIP puts IP packets in AppleTalk (usually LocalTalk) packets whereas AppleTalk over IP puts AppleTalk packets in TCP/IP packets. MacIP is very old technology now, and has limited uses in the age of ethernet. However, for some situations (as with Macs that only have serial networking), it is the only way to get a computer online.
I also use IPNetRouter and LocalTalk Bridge. My Duo 230 and a couple Quadras use MacIP to get to the Internet, while LocalTalk Bridge (running on the IPNetRouter box) allows all my Macs to see each other, regardless of which networking protocol they speak. Works fine.
Check out IPNetRouter here: <http://www.sustworks.com/site/prod_ipr_overview.html>
A bit of advice: Don't plan on actually using your LocalTalk Bridge for anything other than being a LocalTalk Bridge. LocalTalk traffic tends to make the Mac running the bridge intolerably slow for anything else being as it is very CPU intensive. Indeed, if you have the right setup, a Shiva (now dead, bought by Dayna then Intel?) or Cayman dedicated box is probably the best solution.
Peace, Drew
--
Author of ClassicStumbler email: <[EMAIL PROTECTED]> web: <http://www.alksoft.com/>
Want to know if your neighbor has Wi-Fi? Find out with ClassicStumbler 1.6! "Now with REAL cheese!" <http://www.alksoft.com/classicstumbler.html>
-- PowerBooks is sponsored by <http://lowendmac.com/> and...
Small Dog Electronics http://www.smalldog.com | Enter To Win A | -- Canon PowerShot Digital Cameras start at $299 | Free iBook! |
Support Low End Mac <http://lowendmac.com/lists/support.html>
PowerBooks list info: <http://lowendmac.com/lists/powerbooks.shtml> --> AOL users, remove "mailto:"; Send list messages to: <mailto:[EMAIL PROTECTED]> To unsubscribe, email: <mailto:[EMAIL PROTECTED]> For digest mode, email: <mailto:[EMAIL PROTECTED]> Subscription questions: <mailto:[EMAIL PROTECTED]> Archive: <http://www.mail-archive.com/powerbooks%40mail.maclaunch.com/>
Using a Mac? Free email & more at Applelinks! http://www.applelinks.com
