• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 274
  • Last Modified:

Exported Certificate Not Working

On an ISA 2000 server, a Thawte certificate set to expire in a few months.

Exported it to a second ISA2000 server (which I'm setting up to run on a replacement ISP connection).

Imported the certificate on the 2nc ISA2000 server.

But trying to make a https connection to the 2nd server fails.

I don't know what to do to test, tweak, fix... whatever.

Can anyone help me?

Thanks.
0
gateguard
Asked:
gateguard
  • 5
  • 4
1 Solution
 
Dave_DietzCommented:
If you view the certificate in a Certificates management console does it say you have a private key that corresponds to the certificate?

What process did you use to export/import the certificate?

Dave Dietz
0
 
gateguardAuthor Commented:
Yes.  It does say I have a private key.

On the General tab, it has issued-to, issued-by, valid-from-to and then: "You have a private key that corresponds to this certificate."
0
 
Dave_DietzCommented:
That's a good sign.  :-)

How are you trying to connect to the other server?  Do you have a website on it you can connect to?  Are you publishing a site through it?  If so are the forwarding rules configured correctly?

Dave Dietz
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
gateguardAuthor Commented:
The existing, working ISA2000 publishes several websites.  On only one of them has the HTTPS and REQUIRE-128 selected on the bridging tab of its web publishing rule.  The others are straight http.

The one that requires https is a webmail server and does NOT require https on the inside LAN.  There is no certificate on that server (and never has been).  The certificate was created on some now-defunct webserver and exported to the ISA which authenticates the incoming connection and then "terminates the secure channel at the proxy".

On a new ISA2000, connected to a different ISP (we're losing our existing ISP), I have been able to make all the other websites work (testing with a computer on the outside using its HOSTS file to access the new ISA server).

But when I try to go to the https://webmail.domain.com, I fail get one pop-up that says "you are about to view pages over a secure connection", but then the page just fails.

To the best of my ability I have replicated the settings on the working ISA to those on the new ISA, changing only the outside IP addresses, trying to keep everything else exactly the same.

And everything else is working.  Server publishing, web publishing H.323 gateway.  Just this nagging problem of the https connection (and the little matter of the mail server itself, and its connections with the outside world, which is another question I'll ask another time).
0
 
gateguardAuthor Commented:
Sorry.  Mistaken wording.  

Correction:

I DO get the  one pop-up that says "you are about to view pages over a secure connection", but then the page just fails.
0
 
Dave_DietzCommented:
Have you checked the ISA logs?

This really sounds like we're not even getting to the ISA server....

Dave Dietz
0
 
gateguardAuthor Commented:
I got the solution from Thawte.

I had to re-export the certificate from the original IIS, this time NOT choosing the STRONG ENCRYPTION option.

Now I can use the certificate.   Even though on the web publishing BRIDGING tab I did click "require 128 bit".

I have no idea what is going on with certificates.  Anyway, this one is working.

Any closing thoughts on all of this?
0
 
Dave_DietzCommented:
Yep.  :-)

When you choose strong encryption you are prompted for the certificate password every time it is used.

Since the certificate was being used by a service the prompt was being displayed on a non-existant desktop.

Makes perfect sense in retrospect.....

Dave Dietz
0
 
gateguardAuthor Commented:
Thanks for working with me on this.
0

Featured Post

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now