RE: New drive mapping question

Joe,

A Windows domain is technically related to a TCP/IP domain.  It does have
a name and would have at least on Windows server running as a domain
controller.  It is also possible to network a bunch of Windows computers
in a peer-to-peer workgroup, which would also have a name.

Whether a domain or a workgroup, computers in the same named network will
share information regarding shared drives and printers.  This is the name
that should be reflected in the NetServer configuration and allows OS/400
to both see and be seen by other computers on the network.

I'm not sure why someone would want a Windows domain if they weren't
running Windows.  The peer-to-peer stuff works very well for a limited
number of users in a trusted network.

Regards,
Andy Nolen-Parkhouse

> This is the part I don't get.  What the heck is a Windows domain and
> how do
> you create one?  Do you have to have a box running a special (server)
> version of Windows to be the domain server?  Or can a W2K workstation
> be a
> domain server?  Can a Linux box be a domain server?  Can an AS/400
> (with no
> integrated PC card) be a domain server?
> 
> I'm soooo confused.
> 
> Joe