If you need a free SSL certificate, I can create one and send you the steps by which you can use it.

PS: I will respond depending on my free time :) so ... please be patient

hi there!

I really need a free SSl certificate. Just a question, can i use a software like abylon SELFCERT to create a certificate and install it on the server instead of taking a certificate from a CA or from you for example?

Hope someone can help me.

thanx

I use openssl and here you find everything you need http://www.dylanbeattie.net/docs/openssl_iis_ssl_howto.html, you must install CA certificate on the IIS server and workstation. Is very important to use a IIS Certificate Request.

If you need help please reply here.
Have a nice day!

Just to make sure, With this open ssl i won´t need to puchase a x.509 certificate from Verisign for example, correct?

thanx

Yes is correct, you can use your ssl certificate.

Cool!!

I´ve succeeded trough all the process and now i´m generating my own x.509 certificates!!!

Very easy and very well explained.

Thank you a lot!!

bye

Hi, need your help again:

 I´ve generated my SSL certificate, converted it to x.509 and installed it on server(through IIS manager ). I have already double-clicked on ca.cer and iisx509.cer and put it on my Trusted Certificates Root store(at least I believe it is in there!) on my server and on my client. But, sadly, my workstation still cannot conect to the ris server(get stucked on CCWorkstation splash screen on server machine or client machine)!!!!!!

any idea?

 

thanx in advance,

Do you receive an error or not? Ris server listening on port 8000?

Server on port 8000(already open on windows firewall).

Message error: "Cannot connect to net.tcp://:8000/ClearCanvas.Ris.Application.Common.Login.ILoginService". The message continue with "TCP error code 10061 " when running on the server and "TCP error code 10060 " when running on the client.

Another information, or doubt from myself: At the IIS, do I need to stablish a HTTPS connection with the RIS application? Becouse my SSL configuration from RIS state that "The site has no security connection(HTTPS) and can not accept SSL connections"

If your problem is from the ssl certificate RIS workstation would complain about it.
I do not think your problem has to do with the certificate, can you connect from client to server "telnet ip_server 8000" ?

The telnet return the message: "Connecting to 192.168.1.4 . . . Could not open connection to the host, on port 8000: Connect failed"

When you have some  time, can you help me over skype? adriamomsalgado@yahoo.com.br

 

thanx

It seems you can not connect to the RIS Server.
Try "netstat - a" on server and check if the RIS Server listening on port 8000 if you get "hostname:8000", then the problem is your firewall, temporarily disable the firewall on the server and try again.

The netstat -a returned: 

Local addres             external address           State

TCP    0.0.0.0:7              Laptop-dri:0           LISTENING

TCP    0.0.0.0:9              Laptop-dri:0           LISTENING

TCP    0.0.0.0:13             Laptop-dri:0           LISTENING

TCP    0.0.0.0:17             Laptop-dri:0           LISTENING

TCP    0.0.0.0:19             Laptop-dri:0           LISTENING

TCP    0.0.0.0:80             Laptop-dri:0           LISTENING

TCP    0.0.0.0:104            Laptop-dri:0           LISTENING

TCP    0.0.0.0:135            Laptop-dri:0           LISTENING

TCP    0.0.0.0:445            Laptop-dri:0           LISTENING

TCP    0.0.0.0:1000           Laptop-dri:0           LISTENING

TCP    0.0.0.0:5357           Laptop-dri:0           LISTENING

TCP    0.0.0.0:9998           Laptop-dri:0           LISTENING

TCP    0.0.0.0:49152          Laptop-dri:0           LISTENING

TCP    0.0.0.0:49153          Laptop-dri:0           LISTENING

TCP    0.0.0.0:49154          Laptop-dri:0           LISTENING

TCP    0.0.0.0:49155          Laptop-dri:0           LISTENING

TCP    0.0.0.0:49166          Laptop-dri:0           LISTENING

TCP    0.0.0.0:49371          Laptop-dri:0           LISTENING

TCP    0.0.0.0:49413          Laptop-dri:0           LISTENING

TCP    0.0.0.0:50221          Laptop-dri:0           LISTENING

TCP    127.0.0.1:5354         Laptop-dri:0           LISTENING

TCP    127.0.0.1:5357         Laptop-dri:49429       TIME_WAIT

TCP    127.0.0.1:12025        Laptop-dri:0           LISTENING

TCP    127.0.0.1:12080        Laptop-dri:0           LISTENING

TCP    127.0.0.1:12110        Laptop-dri:0           LISTENING

TCP    127.0.0.1:12119        Laptop-dri:0           LISTENING

TCP    127.0.0.1:12143        Laptop-dri:0           LISTENING

TCP    127.0.0.1:12465        Laptop-dri:0           LISTENING

TCP    127.0.0.1:12563        Laptop-dri:0           LISTENING

TCP    127.0.0.1:12993        Laptop-dri:0           LISTENING

TCP    127.0.0.1:12995        Laptop-dri:0           LISTENING

TCP    127.0.0.1:27015        Laptop-dri:0           LISTENING

TCP    127.0.0.1:27015        Laptop-dri:49194       ESTABLISHED

TCP    127.0.0.1:49194        Laptop-dri:27015       ESTABLISHED

TCP    127.0.0.1:49431        Laptop-dri:wsd         TIME_WAIT

TCP    192.168.1.3:49371      192.168.1.3:49401      ESTABLISHED

TCP    192.168.1.3:49371      192.168.1.3:49404      ESTABLISHED

TCP    192.168.1.3:49371      192.168.1.3:49405      ESTABLISHED

TCP    192.168.1.3:49371      192.168.1.3:49407      ESTABLISHED

TCP    192.168.1.3:49371      192.168.1.3:49408      ESTABLISHED

TCP    192.168.1.3:49371      192.168.1.3:49409      ESTABLISHED

TCP    192.168.1.3:49371      192.168.1.3:49414      ESTABLISHED

TCP    192.168.1.3:49371      192.168.1.3:49422      ESTABLISHED

TCP    192.168.1.3:49401      192.168.1.3:49371      ESTABLISHED

TCP    192.168.1.3:49404      192.168.1.3:49371      ESTABLISHED

TCP    192.168.1.3:49405      192.168.1.3:49371      ESTABLISHED

TCP    192.168.1.3:49407      192.168.1.3:49371      ESTABLISHED

TCP    192.168.1.3:49408      192.168.1.3:49371      ESTABLISHED

TCP    192.168.1.3:49409      192.168.1.3:49371      ESTABLISHED

TCP    192.168.1.3:49414      192.168.1.3:49371      ESTABLISHED

TCP    192.168.1.3:49422      192.168.1.3:49371      ESTABLISHED

TCP    192.168.1.4:139        Laptop-dri:0           LISTENING

TCP    192.168.1.4:49424      yo-in-f139:https       ESTABLISHED

TCP    192.168.1.4:49426      yw-in-f125:5222        TIME_WAIT

TCP    192.168.1.4:49427      yw-in-f125:5222        TIME_WAIT

TCP    192.168.1.4:49428      yw-in-f125:5222        ESTABLISHED

TCP    192.168.1.4:49430      yw-in-f125:5222        TIME_WAIT

TCP    [::]:7                 Laptop-dri:0           LISTENING

TCP    [::]:9                 Laptop-dri:0           LISTENING

TCP    [::]:13                Laptop-dri:0           LISTENING

TCP    [::]:17                Laptop-dri:0           LISTENING

TCP    [::]:19                Laptop-dri:0           LISTENING

TCP    [::]:80                Laptop-dri:0           LISTENING

TCP    [::]:135               Laptop-dri:0           LISTENING

TCP    [::]:445               Laptop-dri:0           LISTENING

TCP    [::]:1000              Laptop-dri:0           LISTENING

TCP    [::]:5357              Laptop-dri:0           LISTENING

TCP    [::]:9998              Laptop-dri:0           LISTENING

TCP    [::]:49152             Laptop-dri:0           LISTENING

TCP    [::]:49153             Laptop-dri:0           LISTENING

TCP    [::]:49154             Laptop-dri:0           LISTENING

TCP    [::]:49155             Laptop-dri:0           LISTENING

TCP    [::]:49166             Laptop-dri:0           LISTENING

TCP    [::]:49371             Laptop-dri:0           LISTENING

TCP    [::]:49413             Laptop-dri:0           LISTENING

TCP    [::]:50221             Laptop-dri:0           LISTENING

UDP    0.0.0.0:7              *:*

UDP    0.0.0.0:9              *:*

UDP    0.0.0.0:13             *:*

UDP    0.0.0.0:17             *:*

UDP    0.0.0.0:19             *:*

UDP    0.0.0.0:500            *:*

UDP    0.0.0.0:1434           *:*

UDP    0.0.0.0:3702           *:*

UDP    0.0.0.0:3702           *:*

UDP    0.0.0.0:3702           *:*

UDP    0.0.0.0:3702           *:*

UDP    0.0.0.0:4500           *:*

UDP    0.0.0.0:5355           *:*

UDP    0.0.0.0:50503          *:*

UDP    0.0.0.0:55964          *:*

UDP    0.0.0.0:59242          *:*

UDP    0.0.0.0:59677          *:*

UDP    0.0.0.0:64322          *:*

UDP    0.0.0.0:64324          *:*

UDP    127.0.0.1:1900         *:*

UDP    127.0.0.1:52798        *:*

UDP    127.0.0.1:57376        *:*

UDP    192.168.1.4:137        *:*

UDP    192.168.1.4:138        *:*

UDP    192.168.1.4:1900       *:*

UDP    192.168.1.4:5353       *:*

UDP    192.168.1.4:57375      *:*

UDP    [::]:7                 *:*

UDP    [::]:9                 *:*

UDP    [::]:13                *:*

UDP    [::]:17                *:*

UDP    [::]:19                *:*

UDP    [::]:500               *:*

UDP    [::]:1434              *:*

UDP    [::]:3702              *:*

UDP    [::]:3702              *:*

UDP    [::]:3702              *:*

UDP    [::]:3702              *:*

UDP    [::]:4500              *:*

UDP    [::]:5355              *:*

UDP    [::]:50504             *:*

UDP    [::]:59678             *:*

UDP    [::]:64323             *:*

UDP    [::]:64325             *:*

UDP    [::1]:1900             *:*

UDP    [::1]:57374            *:*

UDP    [::1]:64338            *:*

UDP    [::1]:64339            *:*

UDP    [fe80::8c46:59eb:29f3:5a7e%12]:546  *:*

UDP    [fe80::8c46:59eb:29f3:5a7e%12]:1900  *:*

UDP    [fe80::8c46:59eb:29f3:5a7e%12]:57373  *:*

 About the Firewall issue, when you said that didn´t believe it was a certificate trouble, I turned the firewall off, but got the same results!

 

  --- Edit: I have no telnet server on my server!!!!!!!

It seems that the RIS Server not listening on port 8000, you install RIS server on default port (8000)? give restart to RIS Service or better a full server restart. Certificate may be a problem if you have not generated certificate x.509 after the last IIS request.

 Just for information: I´ve installed the telnet server and everything went just fine, firewall turned on or off.

About the installation of the RIS server, I´ve already uninstalled the RIS server, the Workstation, the .NET 3.5 and the IIS and reinstalled again.

The messages continued the same!!!!

 I trully believe the certificate is the pain in my ass.

Are you using the OpenSSL solution and everything working ok?

 

While RIS server does not listen on port 8000 you can't use RIS solution. I use X.509 certificate generated by openssl and everything is ok. What version of IIS you use? What OS ?