Environment
Novell Open Enterprise Server 2SP2 (OES 2SP2)
Novell Open Enterprise Server 2SP2 (OES 2SP2)
Domain Services for Windows
DSFW
Novell Open Enterprise Server 2SP2 (OES 2SP2)
Domain Services for Windows
DSFW
Situation
What services are necessary for Domain Services for Windows and what order are they to be stopped and started?
Resolution
The easiest way to show the status of each service is to use the 'xadcntrl status' command. You should first see the Tree Name. Here is an example:
dsfwserver:~ # xadcntrl status
Tree Name: DSFW-TREE
Server Name: .CN=dsfwserver.OU=novell.dc=mydomain.dc=com.T=DSFW-TREE.
Binary Version: 20217.06
Root Most Entry Depth: 0
Product Version: eDirectory for Linux v8.8 SP4 [DS]
Checking for nameserver BIND
number of zones: 2
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/1000
tcp clients: 0/100
server is up and running
zone details are dumped at /var/opt/novell/log/named/named_zones.info
running
Checking for Name Service Cache Daemon: running
Checking for RPC Endpoint Mapper Service running
Checking for Kerberos KDC Service running
Checking for Kerberos Password Change Server running
Checking for Domain Services Daemon running
Checking for Samba NMB daemon running
Checking for Samba WINBIND daemon running
Checking for Samba SMB daemon running
Here is a list of each individual daemon and how to verify they are running the manual way:
ps -eaf | grep ndsd | grep -v grep
ps -eaf | grep novell-name | grep -v grep
ps -eaf | grep nscd | grep -v grep
ps -eaf | grep rpcd | grep -v grep
ps -eaf | grep xad-krb5kdc | grep -v grep
ps -eaf | grep xad-kpasswdd | grep -v grep
ps -eaf | grep xadsd | grep -v grep
ps -eaf | grep nmb | grep -v grep
ps -eaf | grep winbind | grep -v grep
ps -eaf | grep smb | grep -v grep
winbind is usally the daemon that will stop if their is an issue.
START ORDER:
Use the 'xadcntrl start' or 'xadcntrl reload' to start/reload all the dsfw services.
To start the individual services use the 'rcservice start' command (ex. rcndsd start). Here is the correct order to start each service. To stop the services manually do it in reverse order:
ndsd
novell-named
nscd
rpcd
xad-krb5kdc
xad-kpasswdd
xadsd
nmb
winbind
smb
Samba has to be last else rpcclient will fail with a NT_STATUS_LOGIN_FAILURE.
dsfwserver:~ # xadcntrl status
Tree Name: DSFW-TREE
Server Name: .CN=dsfwserver.OU=novell.dc=mydomain.dc=com.T=DSFW-TREE.
Binary Version: 20217.06
Root Most Entry Depth: 0
Product Version: eDirectory for Linux v8.8 SP4 [DS]
Checking for nameserver BIND
number of zones: 2
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/1000
tcp clients: 0/100
server is up and running
zone details are dumped at /var/opt/novell/log/named/named_zones.info
running
Checking for Name Service Cache Daemon: running
Checking for RPC Endpoint Mapper Service running
Checking for Kerberos KDC Service running
Checking for Kerberos Password Change Server running
Checking for Domain Services Daemon running
Checking for Samba NMB daemon running
Checking for Samba WINBIND daemon running
Checking for Samba SMB daemon running
Here is a list of each individual daemon and how to verify they are running the manual way:
ps -eaf | grep ndsd | grep -v grep
ps -eaf | grep novell-name | grep -v grep
ps -eaf | grep nscd | grep -v grep
ps -eaf | grep rpcd | grep -v grep
ps -eaf | grep xad-krb5kdc | grep -v grep
ps -eaf | grep xad-kpasswdd | grep -v grep
ps -eaf | grep xadsd | grep -v grep
ps -eaf | grep nmb | grep -v grep
ps -eaf | grep winbind | grep -v grep
ps -eaf | grep smb | grep -v grep
winbind is usally the daemon that will stop if their is an issue.
START ORDER:
Use the 'xadcntrl start' or 'xadcntrl reload' to start/reload all the dsfw services.
To start the individual services use the 'rcservice start' command (ex. rcndsd start). Here is the correct order to start each service. To stop the services manually do it in reverse order:
ndsd
novell-named
nscd
rpcd
xad-krb5kdc
xad-kpasswdd
xadsd
nmb
winbind
smb
Samba has to be last else rpcclient will fail with a NT_STATUS_LOGIN_FAILURE.