|
Home > Archive > Netware Webserver > April 2007 > can't get into my web pages any more :-(
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
can't get into my web pages any more :-(
|
|
| Peter Clinch 2007-03-22, 7:12 am |
| Hi, I'm running NW 6.5 with SP5
Don't often do much with the server, it just sits there and works and
it's nearly a year since I had to anything but change backup tapes, so
apologies if this is a bit Dumb...
Server went down on Monday from a power outage, coming back up all seems
more or less as it should be, but I can't connect to the usual web pages
it (should be) serving any more. Something must be running web-wise, as
I can connect to http://my.server:8008 for admin, and that's all there
as expected, but http://my.server just tells me it can't connect.
I've stopped and started Apache2 (ap2webdn and ap2webup), but still no
sign of the web pages...
Only changes I made to the basic setup were changing DocumentRoot in
httpd.conf, and where it's pointing to is there...
Any ideas, or a step by step troubleshoot guide to point me at?
Previous work on this is very limited, as it used to just work when the
server came up.
Thanks, Pete.
--
Peter Clinch Medical Physics IT Officer
Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
net p.j.clinch@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
| |
| martins_uk 2007-03-22, 1:12 pm |
| On Mar 22, 10:25 am, Peter Clinch <p.j.cli...@dundee.ac.uk> wrote:
> Hi, I'm running NW 6.5 withSP5
>
> Don't often do much with the server, it just sits there and works and
> it's nearly a year since I had to anything but change backup tapes, so
> apologies if this is a bit Dumb...
>
> Server went down on Monday from a power outage, coming back up all seems
> more or less as it should be, but I can't connect to the usual web pages
> it (should be) serving any more. Something must be running web-wise, as
> I can connect tohttp://my.server:8008for admin, and that's all there
> as expected, buthttp://my.serverjust tells me it can't connect.
>
> I've stopped and started Apache2 (ap2webdn and ap2webup), but still no
> sign of the web pages...
>
> Only changes I made to the basic setup were changing DocumentRoot in
> httpd.conf, and where it's pointing to is there...
>
> Any ideas, or a step by step troubleshoot guide to point me at?
> Previous work on this is very limited, as it used to just work when the
> server came up.
>
> Thanks, Pete.
> --
> Peter Clinch Medical Physics IT Officer
> Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
> Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
> net p.j.cli...@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
Pete,
You might have a problem with your certificates. Take a look at Novell
TID 3209228. Make sure you run tckeygen after recreating any certs
with pkidiag, and before restarting the server.
Martin
| |
| Peter Clinch 2007-03-22, 1:12 pm |
| martins_uk wrote:
> You might have a problem with your certificates. Take a look at Novell
> TID 3209228. Make sure you run tckeygen after recreating any certs
> with pkidiag, and before restarting the server.
Thanks for the pointer...
It says to log in as Admin... do I need admin rights to *everything*, or
just my bit of the tree including this server? (I have the latter, not
the former, but I can borow the former if I ask nicely.)
Running PKIDIAG as suggested as my local admin user, and doing 4, 5, 6
and 0, I end up seeing :
Step 6 Creating IP and DNS certificates if necessary.
--> Number of server IP addresses = 1
--> The default IP address is [my IP address]
PROBLEM: The KMO SSL Certificate IP has expired.
--> The KMO SSL CertificateIP's IP address is [my IP address].0=.[tree].
----> The IP addresses match.
Step 6 failed -608.
Doesn't look too clever! any suggestions please?
ta, Pete.
--
Peter Clinch Medical Physics IT Officer
Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
net p.j.clinch@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
| |
| martins_uk 2007-03-22, 1:12 pm |
| On Mar 22, 2:48 pm, Peter Clinch <p.j.cli...@dundee.ac.uk> wrote:
> ande...@nomail.to.me wrote:
>
> See other reply for fun with PKIDIAG
>
> Startup.err is an empty file, so no clues in there.
>
> Though Apache2.NLM appears to load (with a green [ OK ] when I call
> ap2webup), it doesn't seem to be in the Loaded Modules list on the
> Monitor, and ap2webdn notes that APACHE2 is NOT loaded when I call that.
>
> thanks for the input,
> Pete.
> --
> Peter Clinch Medical Physics IT Officer
> Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
> Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
> net p.j.cli...@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
Pete,
Well, at least pkidiag confirms that your certificates have expired,
so we need to get them fixed, then run tckeygen, to (hopefully) fix
all your webby stuff.
Ensure that your servers are all time and DS sync'd. Also make sure
that your server can see the CA server for the tree.
You should only need admin rights to the container in which the server
resides, but if you can get hold of the tree admin account then try
logging into pkidiag with that.
You might also want to download the latest pkidiag.nlm from Novell's
download pages (dated 15/02/2007).
Martin
| |
| Peter Clinch 2007-03-23, 7:11 am |
| martins_uk wrote:
> Well, at least pkidiag confirms that your certificates have expired,
> so we need to get them fixed, then run tckeygen, to (hopefully) fix
> all your webby stuff.
>
> Ensure that your servers are all time and DS sync'd. Also make sure
> that your server can see the CA server for the tree.
>
> You should only need admin rights to the container in which the server
> resides, but if you can get hold of the tree admin account then try
> logging into pkidiag with that.
>
> You might also want to download the latest pkidiag.nlm from Novell's
> download pages (dated 15/02/2007).
Thanks for that, I'll download the latest version and fiddle over the
weekend when I can take things up and down without getting folk miffed,
and report back after that...
cheers, Pete.
--
Peter Clinch Medical Physics IT Officer
Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
net p.j.clinch@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
| |
| Peter Clinch 2007-03-24, 1:11 pm |
| martins_uk wrote:
> Well, at least pkidiag confirms that your certificates have expired,
> so we need to get them fixed, then run tckeygen, to (hopefully) fix
> all your webby stuff.
Having entered tckeygen at the console prompt, I rebooted but when it
came back up, pretty much as before: PKIDIAG (the latest one) still says
the same thing's borken as before. Still get Step 6 failed -603
attemtping the PKIDIAG.
> Ensure that your servers are all time and DS sync'd. Also make sure
> that your server can see the CA server for the tree.
Working from DSRepair, it seems to be time synced, and a full unattended
repair of the DS reports nothing amiss. I'm afraid I need acronym help
with "CA server" :-(
> You should only need admin rights to the container in which the server
> resides, but if you can get hold of the tree admin account then try
> logging into pkidiag with that.
Didn't manage to borrow the Boss password before the weekend, so I just
did it with my local container admin pwd, though as above, no joy.
Bah!
Pete.
--
Peter Clinch Medical Physics IT Officer
Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
net p.j.clinch@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
| |
| martins_uk 2007-03-25, 1:11 pm |
| On Mar 24, 2:29 pm, Peter Clinch <p.j.cli...@dundee.ac.uk> wrote:
> martins_uk wrote:
>
> Having entered tckeygen at the console prompt, I rebooted but when it
> came back up, pretty much as before: PKIDIAG (the latest one) still says
> the same thing's borken as before. Still get Step 6 failed -603
> attemtping the PKIDIAG.
>
If thats an error "-603" (your earlier post reported error "-608"),
then it could be a rights issue. You need to get hold of an admin
account with sufficient rights to the server object (tree admin should
do nicely). You then need to get pkidiag to successfully recreate the
certs, then run tckeygen, then restart the server.
>
> Working from DSRepair, it seems to be time synced, and a full unattended
> repair of the DS reports nothing amiss. I'm afraid I need acronym help
> with "CA server" :-(
>
The CA server is the certificate authority server for your tree. It
issues certs for the other servers in the tree.
>
> Didn't manage to borrow the Boss password before the weekend, so I just
> did it with my local container admin pwd, though as above, no joy.
>
As above, it sounds as though your local admin account has some rights
restrictions. Get hold of the tree admin account, or get the people
who manage the tree to run pkidiag on your server for you.
> Bah!
>
> Pete.
> --
> Peter Clinch Medical Physics IT Officer
> Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
> Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
> net p.j.cli...@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
| |
| Peter Clinch 2007-03-26, 7:21 am |
| martins_uk wrote:
> If thats an error "-603" (your earlier post reported error "-608"),
> then it could be a rights issue. You need to get hold of an admin
> account with sufficient rights to the server object (tree admin should
> do nicely). You then need to get pkidiag to successfully recreate the
> certs, then run tckeygen, then restart the server.
Thanks again for the input, I'll borrow the God account and see how it
goes, and report back. System has a major core upgrade Weds. morning so
everything will have to come down then anyway, which would seem to be a
good opportunity without interrupting folk...
Ta, Pete.
--
Peter Clinch Medical Physics IT Officer
Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
net p.j.clinch@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
| |
| Peter Clinch 2007-03-27, 7:11 am |
| martins_uk wrote:
> If thats an error "-603" (your earlier post reported error "-608"),
> then it could be a rights issue. You need to get hold of an admin
> account with sufficient rights to the server object (tree admin should
> do nicely). You then need to get pkidiag to successfully recreate the
> certs, then run tckeygen, then restart the server.
Borrowed the top level Admin account to run PKIDIAG, but still no joy :-(
In diagnostic mode it reports 2 fixable problems, showing as:
Step 6 Creating IP and DNS certificates if necessary.
--> Number of Server IP addresses = 1
--> The default IP address is 10.252.39.10
PROBLEM: The KMO SSL certificate has expired.
--> The KMO SSL CertificateIP's IP address is 10.252.39.10.0=.DTH.
----> The IP addresses match.
--> Run in Fixing mode to correct this problem(s).
--> Number of Server DNS names for the IP address 10.252.39.10 = 1
--> The server's default DNS name is:
mpd2.tuht.scot.nhs.uk
PROBLEM: The KMO SSL certificateDNS's DNS has expired.
--> The KMO SSL CertificateDNS's DNS name is mpd2.tuht.scot.nhs.uk.0=DTH.
----> The DNS names match.
--> Run in Fixing mode to correct this problem(s).
Step 6 succeeded
Running again, coming into Fix mode this time (in pkidiag, keying, 4, 5,
6, 0 as per Novell TID 3209228)
Step 6 Creating IP and DNS certificates if necessary.
--> Number of Server IP addresses = 1
--> The default IP address is 10.252.39.10
PROBLEM: The KMO SSL certificate has expired.
--> The KMO SSL CertificateIP's IP address is 10.252.39.10.0=.DTH.
----> The IP addresses match.
Step 6 failed -603.
Any further ideas?
Thanks, Pete.
--
Peter Clinch Medical Physics IT Officer
Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
net p.j.clinch@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
| |
| martins_uk 2007-03-28, 7:11 am |
| On Mar 27, 10:37 am, Peter Clinch <p.j.cli...@dundee.ac.uk> wrote:
> martins_uk wrote:
>
> Borrowed the top level Admin account to run PKIDIAG, but still no joy :-(
>
> In diagnostic mode it reports 2 fixable problems, showing as:
>
> Step 6 Creating IP and DNS certificates if necessary.
> --> Number of Server IP addresses = 1
> --> The default IP address is 10.252.39.10
> PROBLEM: The KMO SSL certificate has expired.
> --> The KMO SSL CertificateIP's IP address is 10.252.39.10.0=.DTH.
> ----> The IP addresses match.
> --> Run in Fixing mode to correct this problem(s).
> --> Number of Server DNS names for the IP address 10.252.39.10 = 1
> --> The server's default DNS name is:
> mpd2.tuht.scot.nhs.uk
> PROBLEM: The KMO SSL certificateDNS's DNS has expired.
> --> The KMO SSL CertificateDNS's DNS name is mpd2.tuht.scot.nhs.uk.0=DTH.
> ----> The DNS names match.
> --> Run in Fixing mode to correct this problem(s).
> Step 6 succeeded
>
> Running again, coming into Fix mode this time (in pkidiag, keying, 4, 5,
> 6, 0 as per Novell TID 3209228)
>
> Step 6 Creating IP and DNS certificates if necessary.
> --> Number of Server IP addresses = 1
> --> The default IP address is 10.252.39.10
> PROBLEM: The KMO SSL certificate has expired.
> --> The KMO SSL CertificateIP's IP address is 10.252.39.10.0=.DTH.
> ----> The IP addresses match.
> Step 6 failed -603.
>
> Any further ideas?
>
> Thanks, Pete.
> --
> Peter Clinch Medical Physics IT Officer
> Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
> Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
> net p.j.cli...@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
Pete,
Does sys:\etc\certserv\repair.log give any more info? Did any of the
earlier steps fail or show errors?
Martin
| |
| Peter Clinch 2007-03-28, 7:11 am |
| martins_uk wrote:
> Does sys:\etc\certserv\repair.log give any more info? Did any of the
> earlier steps fail or show errors?
Not really... all looks as if it's happy right up until that -603 exit.
Last couple of attempts, one diagnostic only, one in fix mode shown
below, cut and pasted from the log file. I've tried the various
combinations of options 5 and 6 in pkidiag but basically the same result :-(
(as before, many thanks for you input on this...)
---------------------------------------------------------------------------
PKIDiag 2.78 -- (compiled Feb 01 2007 17:06:17).
(Check the end of the log for the last repair results)
Current Time: Tue Mar 27 10:13:06 2007
User logged-in as: admin.dth.
Diagnostics only mode
--> Server Name = 'MPD2'
---------------------------------------------------------------------------
Step 1 Verifying the Server's link to the SAS Service Object.
Server 'MPD2.MPD.LABS.Ninewells.DTH' points to SAS Service object
'SAS Service - MPD2.MPD.LABS.Ninewells.DTH'
Step 1 succeeded.
Step 2 Verifying the SAS Service Object
SAS Service object 'SAS Service - MPD2.MPD.LABS.Ninewells.DTH' is
backlinked to server 'MPD2.MPD.LABS.Ninewells.DTH'.
Step 2 succeeded.
Step 3 Verifying the links to the KMOs
Reading the links for SAS Service object 'SAS Service -
MPD2.MPD.LABS.Ninewells.DTH'.
--->KMO IP AG 10\.252\.39\.10 - MPD2.MPD.LABS.Ninewells.DTH is linked.
--->KMO SSL CertificateIP - MPD2.MPD.LABS.Ninewells.DTH is linked.
--->KMO DNS AG MPD2 - MPD2.MPD.LABS.Ninewells.DTH is linked.
--->KMO SSL CertificateDNS - MPD2.MPD.LABS.Ninewells.DTH is linked.
--->KMO DNS AG mpd2\.tuht\.scot\.nhs\.uk - MPD2.MPD.LABS.Ninewells.DTH
is linked.
Step 3 succeeded.
Step 4 Verifying the KMOs
---> Testing KMO 'DNS AG mpd2\.tuht\.scot\.nhs\.uk -
MPD2.MPD.LABS.Ninewells.DTH'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.
---> Testing KMO 'SSL CertificateDNS - MPD2.MPD.LABS.Ninewells.DTH'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.
---> Testing KMO 'DNS AG MPD2 - MPD2.MPD.LABS.Ninewells.DTH'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.
---> Testing KMO 'SSL CertificateIP - MPD2.MPD.LABS.Ninewells.DTH'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.
---> Testing KMO 'IP AG 10\.252\.39\.10 - MPD2.MPD.LABS.Ninewells.DTH'.
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 -
MPD2.MPD.LABS.Ninewells.DTH'.
KMO 'IP AG 10\.252\.39\.10 - MPD2.MPD.LABS.Ninewells.DTH' is linked.
KMO 'SSL CertificateIP - MPD2.MPD.LABS.Ninewells.DTH' is linked.
KMO 'DNS AG MPD2 - MPD2.MPD.LABS.Ninewells.DTH' is linked.
KMO 'SSL CertificateDNS - MPD2.MPD.LABS.Ninewells.DTH' is linked.
KMO 'DNS AG mpd2\.tuht\.scot\.nhs\.uk - MPD2.MPD.LABS.Ninewells.DTH' is
linked.
Step 5 succeeded.
Step 6 Creating IP and DNS Certificates if necessary.
--> Number of Server IP addresses = 1
--> The default IP address is: 10.252.39.10
PROBLEM: The KMO SSL CertificateIP has expired.
--> The KMO SSL CertificateIP's IP Address is: 10.252.39.10.O=.DTH.
----> The IP addresses match.
--> Run in Fixing mode to correct this problem(s).
--> Number of Server DNS names for the IP address 10.252.39.10 = 1
--> The server's default DNS name is:
mpd2.tuht.scot.nhs.uk
PROBLEM: The KMO SSL CertificateDNS has expired.
--> The KMO SSL CertificateDNS's DNS name is: mpd2.tuht.scot.nhs.uk.O=.DTH.
----> The DNS names match.
--> Run in Fixing mode to correct this problem(s).
Step 6 succeeded.
Note: Occasionally multiple problems will be solved with a single fix.
Fixable problems found: 2
Problems fixed: 0
Un-fixable problems found: 0
---------------------------------------------------------------------------
PKIDiag 2.78 -- (compiled Feb 01 2007 17:06:17).
(Check the end of the log for the last repair results)
Current Time: Tue Mar 27 10:30:00 2007
User logged-in as: admin.dth.
Fixing mode
Rename and create mode
Always Re-key
--> Server Name = 'MPD2'
---------------------------------------------------------------------------
Step 1 Verifying the Server's link to the SAS Service Object.
Server 'MPD2.MPD.LABS.Ninewells.DTH' points to SAS Service object
'SAS Service - MPD2.MPD.LABS.Ninewells.DTH'
Step 1 succeeded.
Step 2 Verifying the SAS Service Object
SAS Service object 'SAS Service - MPD2.MPD.LABS.Ninewells.DTH' is
backlinked to server 'MPD2.MPD.LABS.Ninewells.DTH'.
Step 2 succeeded.
Step 3 Verifying the links to the KMOs
Reading the links for SAS Service object 'SAS Service -
MPD2.MPD.LABS.Ninewells.DTH'.
--->KMO IP AG 10\.252\.39\.10 - MPD2.MPD.LABS.Ninewells.DTH is linked.
--->KMO SSL CertificateIP - MPD2.MPD.LABS.Ninewells.DTH is linked.
--->KMO DNS AG MPD2 - MPD2.MPD.LABS.Ninewells.DTH is linked.
--->KMO SSL CertificateDNS - MPD2.MPD.LABS.Ninewells.DTH is linked.
--->KMO DNS AG mpd2\.tuht\.scot\.nhs\.uk - MPD2.MPD.LABS.Ninewells.DTH
is linked.
Step 3 succeeded.
Step 4 Verifying the KMOs
---> Testing KMO 'DNS AG mpd2\.tuht\.scot\.nhs\.uk -
MPD2.MPD.LABS.Ninewells.DTH'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.
---> Testing KMO 'SSL CertificateDNS - MPD2.MPD.LABS.Ninewells.DTH'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.
---> Testing KMO 'DNS AG MPD2 - MPD2.MPD.LABS.Ninewells.DTH'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.
---> Testing KMO 'SSL CertificateIP - MPD2.MPD.LABS.Ninewells.DTH'.
Rights check -- OK.
Back link -- OK.
Private Key -- OK.
---> Testing KMO 'IP AG 10\.252\.39\.10 - MPD2.MPD.LABS.Ninewells.DTH'.
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 -
MPD2.MPD.LABS.Ninewells.DTH'.
KMO 'IP AG 10\.252\.39\.10 - MPD2.MPD.LABS.Ninewells.DTH' is linked.
KMO 'SSL CertificateIP - MPD2.MPD.LABS.Ninewells.DTH' is linked.
KMO 'DNS AG MPD2 - MPD2.MPD.LABS.Ninewells.DTH' is linked.
KMO 'SSL CertificateDNS - MPD2.MPD.LABS.Ninewells.DTH' is linked.
KMO 'DNS AG mpd2\.tuht\.scot\.nhs\.uk - MPD2.MPD.LABS.Ninewells.DTH' is
linked.
Step 5 succeeded.
Step 6 Creating IP and DNS Certificates if necessary.
--> Number of Server IP addresses = 1
--> The default IP address is: 10.252.39.10
PROBLEM: The KMO SSL CertificateIP has expired.
--> The KMO SSL CertificateIP's IP Address is: 10.252.39.10.O=.DTH.
----> The IP addresses match.
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
--
Peter Clinch Medical Physics IT Officer
Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
net p.j.clinch@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
| |
| martins_uk 2007-03-29, 1:11 pm |
| Pete,
Can you try running pkidiag with just options 4, 6, 0. ie. no option
5 . ie. Option 5) should be set to "Rename and create new KMO". Option
4) should be set to "Fix mode". Option 6) should be "Always rename and
create".
There may be a problem with the existing KMO's. The above settings
will rename the old ones and create new ones. This always works for us
anyway.
Good luck,
Martin
| |
| Peter Clinch 2007-03-30, 7:11 am |
| martins_uk wrote:
> Can you try running pkidiag with just options 4, 6, 0. ie. no option
> 5 . ie. Option 5) should be set to "Rename and create new KMO". Option
> 4) should be set to "Fix mode". Option 6) should be "Always rename and
> create".
>
> There may be a problem with the existing KMO's. The above settings
> will rename the old ones and create new ones. This always works for us
> anyway.
Same problem :-(
Bother.
I'm off on holiday for a wee while so it'll have to wait (we currently
use the webserver as a php testbed, planned for a Real Use in the coming
year). In the meantime I've escalated it to the site admin and see if
she can get anywhere with it...
I'll report back with any progress (or further lack thereof) when I get
back.
In the meantime, many thanks for trying!
Pete.
--
Peter Clinch Medical Physics IT Officer
Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
net p.j.clinch@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
| |
| Peter Clinch 2007-04-11, 7:12 am |
| Peter Clinch wrote:
<snip tale of woe>
It turned out the problem was at a higher level than just my server,
with slightly wider problems over the directory. The top level admin
managed to rebuild my certificates (it was indeed those that stopped
things working) and everything is happy now.
Thanks for input to this, I learned quite a bit about PKI reading around
it after the suggestions here, and it's all working now :-)
Pete.
--
Peter Clinch Medical Physics IT Officer
Tel 44 1382 660111 ext. 33637 Univ. of Dundee, Ninewells Hospital
Fax 44 1382 640177 Dundee DD1 9SY Scotland UK
net p.j.clinch@dundee.ac.uk http://www.dundee.ac.uk/~pjclinch/
|
|
|
|
|