IIS 5.1 getting a certificate for a 2000 certificate server

ok. . . I am working on setting up a secure web site, but my web server is running on my XP machine. I have certificate server installed on in 2K server, and I was wondering what I had to do to get a certificate to work.

Windows Networking 2246 This topic was started by ,


data/avatar/default/avatar04.webp

10 Posts
Location -
Joined 2000-11-17
ok...I am working on setting up a secure web site, but my web server is running on my XP machine. I have certificate server installed on in 2K server, and I was wondering what I had to do to get a certificate to work. I followed the steps from microsoft that tells me how to do it on IIS 5. The steps were the same for the XP machine, but is there and incompatiblitly issus with IIS 5.1 and certificates. It keeps telling me that the certificate I try to install does not match the pending request. Does anyone know of a way to get this to work? I do not have an internal DNS running, but my web server does have a www address associated with it....could this be causing the problem?

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar40.webp

7 Posts
Location -
Joined 2003-12-22
If the server reports that there are no pending requests, one of the following may be the problem:
 
- The Certsrv page is being accessed by using a different URL than the
one that was used to submit the request. For example, the request was
submitted by using http://Computer_Name/Certsrv, and you are trying to
view the pending requests by using http://IP_Address/Certsrv.
 
- The client browser has cookies disabled.
 
- The server is unable to retrieve the cookie that is stored on the
client computer.
 
- The cookie that is returned by the client is corrupt.
 
- The cookie has expired.
 
- The right bracket (]) delimiter was not found in the cookie list.