unable to start micasad and afptcpd services

[junaid_s84]

It appears like there is an issue with eDirectory on your set up. The fact that it did not show the tree name suggests that the ldap query to fetch the tree name failed. Are other OES services running normally on your box? To answer your other queries:

- Why doesn't it go into the afp config when afp is installed?
If AFP was chosen to install as part of the OES install then AFP configuration is listed and allows you to modify the configuration.

- Why doesn't it add a yast module?
In YaST if you've chosen to install the novell-afptcpd module it auto-selects the yast2-novell-afp module for install.

- Why have I had to manually configure Casa?
It's not required to manually configure CASA. If the AFP configuration goes through fine, it takes care of storing proxy user credentials in CASA.

- Why when I run yast2 or yast afp-novell does it prompt me for a blank tree and servername that can't be defined?
Like I mentioned before it could be an issue with the eDir. Can you post the log entries of /var/log/YaST2/y2log ?

- Is there another way to configure afp?
You need to do the following to configure AFP:
1) create a proxy user (this is a normal eDirectory user with rights to read AFP users password)
2) ensure AFP users are assigned to a universal password policy
3) add the proxy user (created in step 1) as a reader of passwords to the password policies attached to AFP users
4) run the command:
$ casaforafp
this will prompt you for user credentials. provide the credentials of the AFP proxy user (created in step 1). this steps stores your proxy user credentials in CASA
5) edit the /etc/opt/novell/afptcpd/afpdircxt.conf
file and store the context of AFP users here. For instance, if cn=afpuser.o=mycompany is an AFP user, store o=mycompany in afpdircxt.conf

run AFP: rcnovell-afptcpd start
if you still see issues post the contents of: /var/log/afptcpd/afptcp.log

Junaid