I'm trying to create a test server for testing DSfW in a separate test
tree. This is to be the only server in the tree.

Unfortunately so far I haven't been able to perform a successful
installation. I'm following the procedure described in Novell DSfW
Administration Guide about "Installing the First DSfW Server in a New
eDirectory Tree" as well as the advice given in TID7002172 "Preparing for
Domain Services for Windows Install".

So I install a standard SLES10 SP2 box with only "Linux Base system" and
"Documentation" patterns, update it through the channel and then install
OES2 SP1 as add-on product, selecting the DSfW pattern. I go through the
installation settings and reach the screen where eDirectory is being
configured, the last item on the list being DSfW configuration. That
churns along for several minutes and then reports a failure. The log that
it leaves behind (ndsdcinit.log, 185 kB) ends with this:

>>> Restarting services

Shutting down name server BIND - Warning: novell-named not running! ..done
Shutting down Name Service Cache Daemon..done
Shutting down Domain Services Daemon..done
Shutting down Kerberos Password Change Server..done
Shutting down Kerberos KDC..done
Shutting down RPC Endpoint Mapper Service..done
/bin/sh: /etc/init.d/nmb: No such file or directory
Shutting down Samba WINBIND daemon Warning: daemon not running. ..done
/bin/sh: /etc/init.d/smb: No such file or directory
make: *** [nds_restart_services] Error 127

Wed Feb 4 17:54:53 EET 2009
End of DSfW installation and provisioning

As far as I can tell, there are no other erros before that in the log.

From that point on it's all downhill. All the next steps in configuring
OES services fail because Administrator can't be authenticated. There are
a lot of messages in y2log like this one:

2009-02-04 18:38:14 <3> oes(6544) [bash] ShellCommand.cc(shellcommand):78
ERROR : Administrator "cn=Administrator.cn=Users.dc=test.dc=internal "
could not be authenticated. Verify that you have entered the correct password.
2009-02-04 18:38:14 <3> oes(6544) [bash] ShellCommand.cc(shellcommand):78
Authentication failed.
2009-02-04 18:38:14 <3> oes(6544) [bash] ShellCommand.cc(shellcommand):78

Finally the installation reaches the end, claiming to be "successful" ;)
After rebooting the server I discovered that local DNS daemon is not
running. I started it (rcnovell-named start) manually and ran 'xadcntrl
reload' which seemed to be successful except complaining about missing
rcsmbd and rcnmbd.

After that, most of the checks described in TID7001884 "Verify a Domain
Services for Windows Install" actually work, except:

# /opt/novell/xad/bin/kinit Administrator@test.internal
kinit(v5): KDC has no support for encryption type while getting initial

# # rpcclient -k localhost -c dsroledominfo
Error connecting to (Connection refused)
cli_start_connection: failed to connect to LOCALHOST<20> (
Cannot connect to server. Error was NT_STATUS_CONNECTION_REFUSED

Out of my four testserver installs in last two days this last one is the
most successful, but it still feels decidedly unhealthy.

I wonder if the missing 'smb' and 'nmb' scripts indicate that at some
point I should have included Samba and didn't?
Anyone here with a working DSfW server, do you have /etc/init.d/smb and
/etc/init.d/nmb on your server? Where do they come from?


.... Windws is ine for bckgroun comunicaions - Bll Gats, 192