I've installed a new NW65SP8 server into an existing tree. In the same
context as this server there are another 2 NW65SP7 servers and 1 OES2
Linux server. The new server does not have a replica of an eDir partition.

After install, Apache would not load and I found that there was a
problem with the certificates. I tried to run PKIDIAG to fix the issue
but I'm getting error -603 in step 6. Below is the PKIDIAG log (I've
removed references to old certs and other servers).

Using C1 I can create a test cert for the server that is the CA so the
CA seems to work OK.

I can't find any TIDs on this (relating to winsock error/not able to
detect IP address). Any help resolving this is greatly appreciated.

Lou

PKIDiag 2.78 -- (compiled Jul 18 2005 17:19:11).
(Check the end of the log for the last repair results)
Current Time: Fri May 15 15:41:28 2009
User logged-in as: admin.xxxxxivil.
Fixing mode
Rename and create mode
Rename and create when necessary

--> Server Name = 'GARFIELD'
---------------------------------------------------------------------------

Step 1 Verifying the Server's link to the SAS Service Object.
Server 'GARFIELD.xxxxxivil' points to SAS Service object 'SAS
Service - GARFIELD.xxxxxivil'
Step 1 succeeded.

Step 2 Verifying the SAS Service Object
SAS Service object 'SAS Service - GARFIELD.xxxxxivil' is backlinked
to server 'GARFIELD.xxxxxivil'.
Step 2 succeeded.

Step 3 Verifying the links to the KMOs
Reading the links for SAS Service object 'SAS Service -
GARFIELD.xxxxxivil'.
--->KMO IP AG 192\.168\.0\.100 - GARFIELD.xxxxxivil is linked.
--->KMO SSL CertificateIP - GARFIELD.xxxxxivil is linked.
--->KMO DNS AG garfield\.xxxxxivil\.com\.au - GARFIELD.xxxxxivil is linked.
--->KMO SSL CertificateDNS - GARFIELD.xxxxxivil is linked.
Step 3 succeeded.

Step 4 Verifying the KMOs
---> Testing KMO 'SSL CertificateDNS - GARFIELD.xxxxxivil'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.

---> Testing KMO 'DNS AG garfield\.xxxxxivil\.com\.au - GARFIELD.xxxxxivil'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.

---> Testing KMO 'SSL CertificateIP - GARFIELD.xxxxxivil'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.

---> Testing KMO 'IP AG 192\.168\.0\.100 - GARFIELD.xxxxxivil'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.
Step 4 succeeded.

Step 5 Re-verifying the links to the KMOs
Reading the links for SAS Service object 'SAS Service -
GARFIELD.xxxxxivil'.
KMO 'IP AG 192\.168\.0\.100 - GARFIELD.xxxxxivil' is linked.
KMO 'SSL CertificateIP - GARFIELD.xxxxxivil' is linked.
KMO 'DNS AG garfield\.xxxxxivil\.com\.au - GARFIELD.xxxxxivil' is linked.
KMO 'SSL CertificateDNS - GARFIELD.xxxxxivil' is linked.
Step 5 succeeded.

Step 6 Creating IP and DNS Certificates if necessary.
WARNING: We are not able to determine the IP address of this Server.

This is probably due to either a winsock defect or a IP/DNS
misconfiguration.
There are known defects with winsock support.
Please update to the latest service pack.

PROBLEM: A SSL CertificateIP does not exist
Step 6 failed -603.


Note: Occasionally multiple problems will be solved with a single fix.

Fixable problems found: 1
Problems fixed: 0
Un-fixable problems found: 0