[WinMac] Windows, Macs, & Zones

Ethan C. Banks(ebanks[at]pcci.edu)
Fri, 16 Oct 1998 09:24:10 -0500

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Next message: Ethan C. Banks: "[WinMac] SUMMARY: E-Mail System Research"
Previous message: Tim Scoff: "Re: [WinMac] Microsoft UAM?"
In reply to: Ari Davidow: "[WinMac] Microsoft UAM?"

> -----Original Message-----
> From: winmac@xerxes.frit.utexas.edu
> [mailto:winmac@xerxes.frit.utexas.edu]On Behalf Of Larry A. Wanget
> Sent: Thursday, October 15, 1998 7:58 PM
> To: The Windows-MacOS cooperation list
> Subject: Re: [WinMac] IP conflict with itself?
>
>
> Also, we had the impression that Macs and PCs follow different networking
> concept. Macs are connected with the Macs grouped in zones (I believe this
> is the recommended way), while PCs are connected in a large-single zone.
> Are these rules still apply ? Any body knows what are the consequences if
> they are not followed in a mixed network (100+ devices).

Larry, this is a protocol issue, not a platform issue. AppleTalk networks
provide logical groupings of Macs, LaserWriters, and other AppleTalk-savvy
devices into zones. Any machine that has a loaded AppleTalk stack can (in
fact will have to) be a member of an AppleTalk zone. My NT Server running
Services for Macintosh shows up in an AppleTalk zone.

In my experience, AppleTalk zones are a unique animal among network
protocols. There is nothing similar to AT zones in TCP/IP for instance.
Remember that an AppleTalk zone is merely a logical grouping that transcends
any AT routing you may be doing. You can seed any AppleTalk zone on any
segment you wish, and AT devices in different routed segments can appear in
the same logical zone in the Chooser.

There are no "consequences" if you have a mixed network of Macs & PCs where
the Macs are using AppleTalk and participating in zones and the PCs are
using TCP/IP or some other protocol. Nor is there a zone problem if you are
running COPSTalk, Services for Macintosh, or PC MacLAN on your Windows box.

In the Windows world, the Network Neighborhood model with workgroups and/or
domains does not operate in any way approximating what an AT zone is really
doing. The end results are similar, but arrived at in completely different
ways. Network Neighborhood is really just a server maintained list (which
may or may not be accurate) that you retrieve, whereas in the Chooser, your
Mac actually broadcasts via the AT protocol on the network for everyone in
the selected zone to respond. The Chooser only works over AppleTalk because
its functionality is protocol-based, whereas the Network Neighborhood list
will work over really any protocol that handles Microsoft's SMB (TCP/IP,
IPX, and NetBEUI all handle this).

________________________________________________
Ethan C. Banks - Network Engineer
Pensacola Christian College & Related Ministries

* Windows-MacOS Cooperation List *
* FAQ: <http://www.darryl.com/winmacfaq/> *
* Archives: <http://www.darryl.com/winmac/> *
* Subscribe: <mailto:winmac-on@xerxes.frit.utexas.edu> *
* Subscribe Digest: <mailto:winmac-digest@xerxes.frit.utexas.edu> *
* Unsubscribe: <mailto:winmac-off@xerxes.frit.utexas.edu> *

Next message: Ethan C. Banks: "[WinMac] SUMMARY: E-Mail System Research"
Previous message: Tim Scoff: "Re: [WinMac] Microsoft UAM?"
In reply to: Ari Davidow: "[WinMac] Microsoft UAM?"

This archive was generated by hypermail 2.0b2 on Fri Oct 16 1998 - 07:26:25 PDT