Prev: FSMT Error
Next: vb.net LDAP error
From: Miha on 22 Feb 2010 02:33 Hi We have two web servers running on Win2003 Standard.One is for production and the second for testing. The have different IPs, but the public URL is the same. From time to time we switch public IP (our company web site)to second private IP server for testing purposes, and then back to the first web server. Can we use the same SSL (HTTPS) web certificate (issued by Versign) for both of the servers for our company domain? If yes, how can this be done on a second server in IIS? Regards,Miha
From: .._.. on 22 Feb 2010 09:56 Yes, it can be done. Using the MMC Certificate snap-in, export the certificate (be sure to get both the public and private keys) to the hard drive. http://technet.microsoft.com/en-us/library/cc779668%28WS.10%29.aspx If you did this already, and didn't mark the private key "exportable" you will be unable to copy the certificate in this way. Just move the file like any other file. In IIS certificates wizard, choose "import a certificate" (or similar). The certificates care about the URL matching up, and having the public and private key. They don't care about the IP. Note, the certificate should be considered sensitive information and protected from ending up "out in the wild" "Miha" <miha(a)positiva.si> wrote in message news:O2fliF5sKHA.4752(a)TK2MSFTNGP04.phx.gbl... > > Hi > > We have two web servers running on Win2003 Standard.One is for production > and the second for testing. The have different IPs, but the public URL is > the same. From time to time we switch public IP (our company web site)to > second private IP server for testing purposes, and then back to the first > web server. > Can we use the same SSL (HTTPS) web certificate (issued by Versign) for > both of the servers for our company domain? If yes, how can this be done > on a second server in IIS? > Regards,Miha > >
From: Miha on 22 Feb 2010 10:38 Thanks! Regards,Miha ".._.." <testing(a)jacksoncountybank.com> wrote in message news:WWwgn.15$Sp1.13(a)newsreading01.news.tds.net... > Yes, it can be done. > > Using the MMC Certificate snap-in, export the certificate (be sure to get > both the public and private keys) to the hard drive. > http://technet.microsoft.com/en-us/library/cc779668%28WS.10%29.aspx > > If you did this already, and didn't mark the private key "exportable" you > will be unable to copy the certificate in this way. > > Just move the file like any other file. > > In IIS certificates wizard, choose "import a certificate" (or similar). > > The certificates care about the URL matching up, and having the public and > private key. They don't care about the IP. > > Note, the certificate should be considered sensitive information and > protected from ending up "out in the wild" > > > "Miha" <miha(a)positiva.si> wrote in message > news:O2fliF5sKHA.4752(a)TK2MSFTNGP04.phx.gbl... >> >> Hi >> >> We have two web servers running on Win2003 Standard.One is for production >> and the second for testing. The have different IPs, but the public URL is >> the same. From time to time we switch public IP (our company web site)to >> second private IP server for testing purposes, and then back to the first >> web server. >> Can we use the same SSL (HTTPS) web certificate (issued by Versign) for >> both of the servers for our company domain? If yes, how can this be done >> on a second server in IIS? >> Regards,Miha >> >> > >
From: Dan on 25 Feb 2010 05:20 I would also suggest you read the Verisign licensing terms - certificates are normally specified as only being allowed to be used on a single server, and to use on additional servers there will be an additional licensing fee. Dan "Miha" <miha(a)positiva.si> wrote in message news:uFdODU9sKHA.3904(a)TK2MSFTNGP02.phx.gbl... > Thanks! > Regards,Miha > ".._.." <testing(a)jacksoncountybank.com> wrote in message > news:WWwgn.15$Sp1.13(a)newsreading01.news.tds.net... >> Yes, it can be done. >> >> Using the MMC Certificate snap-in, export the certificate (be sure to get >> both the public and private keys) to the hard drive. >> http://technet.microsoft.com/en-us/library/cc779668%28WS.10%29.aspx >> >> If you did this already, and didn't mark the private key "exportable" you >> will be unable to copy the certificate in this way. >> >> Just move the file like any other file. >> >> In IIS certificates wizard, choose "import a certificate" (or similar). >> >> The certificates care about the URL matching up, and having the public >> and private key. They don't care about the IP. >> >> Note, the certificate should be considered sensitive information and >> protected from ending up "out in the wild" >> >> >> "Miha" <miha(a)positiva.si> wrote in message >> news:O2fliF5sKHA.4752(a)TK2MSFTNGP04.phx.gbl... >>> >>> Hi >>> >>> We have two web servers running on Win2003 Standard.One is for >>> production and the second for testing. The have different IPs, but the >>> public URL is the same. From time to time we switch public IP (our >>> company web site)to second private IP server for testing purposes, and >>> then back to the first web server. >>> Can we use the same SSL (HTTPS) web certificate (issued by Versign) for >>> both of the servers for our company domain? If yes, how can this be done >>> on a second server in IIS? >>> Regards,Miha >>> >>> >> >> > >
|
Pages: 1 Prev: FSMT Error Next: vb.net LDAP error |