>From -
Subject: Re: [e-smith-devinfo] Windows 2000 Domain Controller issues
From: "Greg J. Zartman" <[EMAIL PROTECTED]>
To: Spencer 'Fahrenheit' Fornaciari <[EMAIL PROTECTED]>
In-Reply-To: <001c01c1470f$70617040$4242a8c0@enragedgamer>
References: <001c01c1470f$70617040$4242a8c0@enragedgamer>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.12 (Preview Release)
Date: 27 Sep 2001 08:11:17 -0400
Message-Id: <1001592678.5047.39.camel@laptop>
Mime-Version: 1.0
X-Evolution-Account: [EMAIL PROTECTED]
X-Evolution-Source:
X-Evolution: 00000004-0010
Spencer,
Setting up Samba as a PDC a little tricky the first time, but once you
do it once, tt's a SNAP.
For the most part, Mitel has done a pretty good job of providing Samba
config. parameters, in built in the built in templates, to get you going
with a Samba PDC.
First, get in the server-manager and select Workgroup under the
Configuration section. Make sure you have your workgroup name and
server name input and Domain Master is set to Yes (Note: I'm assuming
your samba PDC is going to function as the WINS server. If this isn't
the case, then you'll need to setup some custom templates to let samba
know what you are doing. Let me know and I'll show you how to do this)
Save your changes and reboot your machine. After your server reboots,
go back to the server manager and view the messages log file. Scroll
down to log entries to coincide with your boot up time and look for nmbd
deamon entries. What you want to see is "Samba server {your server
name} is now a master browser for workgroup {your workgroup name} on
subnet....." If you see this, you are nearly there.
Next, goto your windows box and see if you can browse the server in
Network Neighborhood. IF you can't see it, the problem is likely with
the windows machine. Things that will prevent browsing of a Samba
machine include:
1. Using other network protocols other than TCP/IP: IF this is the
case, remove them for now. Once you get Samba working, you can play
around with adding them back in.
2. Another WINS server on your subnet: If you do have two, you need to
decide on which one to use. To make your life ALOT easier, I'd try as
hard as possible to use SAMBA as the WINS.
3. The setting "disable Netbios over TCP/IP" being selected under your
WINS settings on the client machine: You need to have Enable NetBios
over TCP/IP selected.
If none of the above solves the problem, then the problem is a more
basic network issue (i.e., network communications).
So, now you should see your SME server in network neighborhood. You are
now ready to add machines to domain. Before you do this, you'll need to
make a custom template to add the "add user script" parameter to your
smb.conf. Follow Dan Brown's Howto that details the process for doing
this (make sure that it is the howto that specifies the following add
user script line: add user script = /usr/bin/adduser -d /dev/null -g
100 -s /bin/false -M %u. He has two howtos out there.)
If you changed anything in the way of config parameters, reboot for good
measure.
Next, log into a client machine as the administrator. Once in as the
administrator, right click on my computer, then Network Identification,
then properties. Verify you NetBios mahine name, then in the domain
field input your samba domain name and hit OK. When asked to input a
username and password to join the domain, you MUST input root as the
username and your SME server root password as the password(using the
username admin and the server pasword won't work). In a minute or two,
you should recieve a message that says "Welcome to you domain."
I hope the helps. Let me know how things go.
Regards,
Greg J. Zartman
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
