Fedora Core 4 Smba unable to connect to the PDC
 

i have had a read of most of the Samba releated issues on this website, and implemented most of the fixes, but i am still having a problem,

I have 10 WinXP SP2 desktop Pc's and 1 Fedora Core 4 PC attached with an ethernet network. Each PC has a statically assigned IP Address 192.168.x.x and each machine can Ping each other machine (possible irrelevent however i thought i would share that the network is functioning)

On the Windows PC, if i go to network neighborhood and view all network, i can see the fedora PC, and the shares i setup in smb.conf and if i double click, i can login using the login ID from the linux Pc. So to that point i guess that Samaba is working fine, and is able to communicate between winXP and Linux..

I want to setup Samba as a PDC, so i followed the instructions and created the /etc/samba/smb.conf (see below) and went to the windows PC, i thne entered Regedit and assigned the RequireSignorSeal = 0 and signsecurechannel = 0 I thn opened gpedit.msc and enabled Do not check for user ownership of Roaming Profile Folders...

On the linux pc i entered smbpasswd -a root and entered the password letmein

Back to WinXP

I then went to the system area, changed from Workgroup to domain, entered the domain name, and as expected XP wants a top level login to attach to the domain, so i entered

root
letmein

And after several seconds the PC came back with User not found error message...

So i read some more, and possible i needed to do

smbpasswd -a -m root

This however came back with a message

Failed to initialise SAM_ACCOUNT for user root$ does this user exist in the Unix password database?

the Samba version is Samba 3.0 which comes with the FC4 DVD.. some other stuff worth noting...

When i run a testparm on the /etc/samba/smb.conf it comes back with

Unknown parameter encountered: "domain admin group"
Ignoring unknown parameter "domain admin group"

Now most of the smb.conf files i have seen on this site have the line
domain admin group = root david

the

smbpasswd file has a line in it

root:0:50FCB33E62052231AAD3B435B51404EE:CABA2D3F6756E7F729F969D849D6241F:[U ]:LCT-43042D2F:

so i guess thats ok..


So i guess my question is.. Samba obviously works, because i can access the linux shars from a WinXP machine. So what is the PDC authorisation login looking for? the most fustrating part is that i have had this working before...





/etc/samba/smb.conf file

[global]
netbios name = Rasami_ICT
workgroup = RASAMI
encrypt passwords = yes

domain master = yes
local master = yes
preferred master = yes
os level = 65

security = user
domain logons = yes
logon path = \\%L\profiles\%u\%m
logon script = logon.bat
logon drive = h:

time server = yes

domain admin group = root david

add user script = /usr/bin/userdadd -d /dev/null -g 100 -s /bin/false -M %u
username map = /etc/samba/smbusers

[net-logon]
path = /usr/local/samba/lib/netlogon
writeable = no
browseable = no

[profiles]
path = /home/samba-ntprof
browseable = no
writeable = yes
create mask = 0600
directory mask = 0700

[homes]
writeable = yes
browseable = no
guest ok = no
map archive = yes



Output from Testparm

[global]
workgroup = RASAMI
netbios name = RASAMI_ICT
username map = /etc/samba/smbusers
time server = Yes
add user script = /usr/bin/userdadd -d /dev/null -g 100 -s /bin/false -M %u
logon script = logon.bat
logon path = \\%L\profiles\%u\%m
logon drive = h:
domain logons = Yes
os level = 65
preferred master = Yes
domain master = Yes

[net-logon]
path = /usr/local/samba/lib/netlogon
browseable = No

[profiles]
path = /home/samba-ntprof
read only = No
create mask = 0600
directory mask = 0700
browseable = No

[homes]
read only = No
browseable = No

1.)
smbpasswd -a -m root
generates a machine-account (the real name is now root$, not root), so delete the "root" line in the smbpasswd file and try

smbpasswd -a root


2.)
the name of the netlogon-share usually is [netlogon], not [net-logon]

deleted, renamed no joy,

could anyone explain to me what SHOULD happen, when the Windows XP workstation tries to contact the SMB PDC.. then maybe i can run Ethereal, and see what is actually happening?

I finally solved this in the typical linux way, candle wax and redbull, and a loss of hair..

I couldn't figure out where i was going wrong, and today i solved this problem...

for some reason i needed to add the machine name, the command line kept coming up with errors, so i reached for Webmin (fantastic software, best of breed)

And downloaded a mod for it, Samba Machine which appeared to do the trick, I added the machine names and we were cooking with Gas...

Some other commands which may also have had an effect were

useradd -g root -d /dev/null -s /dev/null administrator

and followed by

smbpasswd -a root

I had already done the last one..

Samba 3 didn't need any of the XP registry hacks it worked first time out...

So there you go, add the machine name, make sure root is a recongised user and now i'm off to figure out about Samba and LDAP and the best way to manage 140 students on a network..

http://www.emta.net/almateria/HAND/nicedaysticker2.JPG