Connecting SADMS to Windows 2003 Small Business Server

Hi Everyone

I’m playing around with the idea of building a linux based replication server on my company’s domain, which is run by a Windows 2003 Small Business Server DC. When trying to add the Linux machine to the domain, through SADMS 2.0.12, I get the following error:

S A D M S 2.0.12
Samba as Active Directory Member Server


+fix bugs/incompatibilities
disable avahi-daemon automatic startup
+customize krb5.conf
install new krb5.conf to /etc
+get current samba version for smb.conf syntax
samba minor version is 1
+samba config switches
use wins server
include sample shares
+customize smb.conf
install new smb.conf to /etc/samba
install new to /etc/samba
+creating sample data folder in /data shared as data
+ping kdc shserver1
+sync clocks with kdc
local time was: 2008-09-03 15:14.15
synchronizing with shserver1
net time is now:2008-09-03 15:14.16
local time is now:2008-09-03 15:14.16
+get Kerberos ticket-granting ticket for principal administrator@SHARRISON.LOCAL
got ticket-granting ticket for principal krbtgt/SHARRISON.LOCAL@SHARRISON.LOCAL
+get current samba version for join domain syntax
samba minor version is 1
+join domain to Computers
join failed and returned 255
[7>] with error
log extract
Sep 3 15:14:06 linux-anac sadms: sadms start
Sep 3 15:14:20 linux-anac sadms: sadms finish error 7 join domain

returned error code 7
command line was <./ ‘windomain.local’ ‘winDC’ ‘WinDC’ ‘windomain.local’ ‘linux-anac’ ‘Computers’ ‘administrator’ ‘*****’ ‘Domain Users’ ‘’ ‘WinDC’>

where WinDC = my Windows DC, and windomain = my Windows domain (obviously, I know).

Here is the contents of /etc/nsswitch.conf


An example Name Service Switch config file. This file should be

sorted with the most-used services at the beginning.

The entry ‘[NOTFOUND=return]’ means that the search for an

entry should stop if the search in the previous entry turned

up nothing. Note that if the search failed due to some other reason

(like no NIS server responding) then the search continues with the

next entry.

Legal entries are:

compat Use compatibility setup

nisplus Use NIS+ (NIS version 3)

nis Use NIS (NIS version 2), also called YP

dns Use DNS (Domain Name Service)

files Use the local files

[NOTFOUND=return] Stop searching if not found so far

For more information, please read the nsswitch.conf.5 manual page.

passwd: files nis

shadow: files nis

group: files nis

passwd: compat winbind
group: compat winbind

hosts: files mdns4_minimal [NOTFOUND=return] dns

hosts: dns files
networks: files dns

services: files
protocols: files
rpc: files
ethers: files
netmasks: files
netgroup: files nis
publickey: files

bootparams: files
automount: files nis
aliases: files

Any suggestions are welcome, although I suspect it may be simply because of the frustrating limitations of SBS domains. It has created a computer account for the Linux box in AD, though.