Well, it would be really nice if the appcon would follow up original post....maybe he/she fixed and doesn't need us...<:LINEBREAK:>Anyway, there's a misconception about AppleTalk....You can have AppleTalk connect via modem while TCP/IP uses ethernet, etc.<:LINEBREAK:>AppleTalk runs on a separate network layer from TCP/IP....<:LINEBREAK:>Sooo, you can turn AppleTalk OFF and still connect to a network if AppleTalk is not needed...and it is not needed for a connection to the internet!<:LINEBREAK:>There's nothing "different" about Mac networking in this regard. With the latest versions of Open Transport, the Mac TCP/IP stack is quite robust.<:LINEBREAK:>Remember, each network protocol you have loaded lets you decide how you connect...in the Windows world, you use "bindings" tab in the network device control panel to route a protocol through a specific device.<:LINEBREAK:>The Mac way lets you save multiple TCP/IP configurations, multiple AppleTalk configs, multiple Remote Access (or PPP) connections as well. Oh, and you can switch them on the fly without rebooting....<:LINEBREAK:>Once you get to know these control panels, you will find that they are very flexible and straightforward.<:LINEBREAK:>I have never had problems with networking on a Mac, provided I stick with AppleTalk and TCP/IP...and every Linux distro supports netatalk...if you have an NT server, well, that's another story...services are available, but you may have to tell your administrator that they exist...Microsoft servers require a bunch of NT service packs in order to keep everything current, and NT services for Macintosh are a low priority for them.