Gerry Maddock wrote: [whcih is better] An NT Domain Controller and Wins Server, | or Samba ????? | What I'm actually looking into this is for storing Winblows profiles | on one server, browsing routed networks, etc... I'm a Unix bigot, so I tend to reccomend making the Windows clients member of an ordinary Unix-style domain using Samba as a combined authentication, print and file server, and managing the samba server as just another server in a vax-free vaxcluster of servers (;-)) Windows domains are cool, but they start you down the path to many individual servers and many many windows admins. [We used to have 5 Win and OS/2 SMB servers: I replaced them with one Unix box when the PC guy quit due to overwork] --dave -- David Collier-Brown, | Always do right. This will gratify some people 185 Ellerslie Ave., | and astonish the rest. -- Mark Twain Willowdale, Ontario | //www.oreilly.com/catalog/samba/author.html Work: (905) 415-2849 Home: (416) 223-8968 Email: davecb@canada.sun.com
I currently have had Samba running on our network as a file and
print server and have had no major problems at all. I know Samba is
capable of becoming a Wins Server and a Domain controller. I was looking
into this, and was wondering who else is running Samba in this
configuration. If you are running it in this configuration:
How do you like it: ( does it run well, what are the pros and cons of
it, any hardware issues such as RAM, disk space per user, any changes to
the speed of the network, etc..)???
I know it's Linux and probably prefers Linux to Winblows, as I do, but
What do you think works better: An NT Domain Controller and Wins Server,
or Samba ?????
What I'm actually looking into this is for storing Winblows profiles
on one server, browsing routed networks, etc...