Vince, Since you have the transition pack installed you must have moved something off the SBS box. Which components have you moved? Just ISA? The certs need to reside in IIS and the path should probably be publishing.yourserver.com. Have you checked the paths? Go to IIS right click on your website, choose properties, look at the certificate and see if the path is correct and validated. Do this for each site. You might also want to run certutil and determine if there are any old certs getting in the way in the registry. Since you've tried multiple methods you might find the conflict in there. I'm pretty sure that this is going to be an IIS issue and not an ISA issue. Amy Harbor Computer Services Small Business Computer Specialists -----Original Message----- From: Vince Humphreys [mailto:vincehumphreys@xxxxxxxxxxx] Sent: Monday, November 08, 2004 12:57 PM To: [ISAserver.org Discussion List] Subject: [isalist] Issues Publishing SBS 2003 with ISA 2004 http://www.ISAserver.org Hello, I have Windows Small Business Server 2003 (1 nic), with the Transition pack installed, and I am using ISA 2004. On the default web site I have issued a cert called mail.<businessname>.com, and I have create an other SharePoint VS on the same box call team.<businessname>.com and also issues a cert to that. I want to be able to have both ssl from the internet. On the ISA box I went to http://sbsservername/certsvr and got a wildcard cert (*.businessname.com)and used it for the Web listener When I type https://mail.businessname.com/exchange I get the cert message, and I click on it to view the cert, and it says that it is being issues by the team.<businessname>.com and not by mail.team.<businessname>.com How could that be? I have tried various ways to publish both sites but it does not seem to work. Some of the things that I have tried: 1: Use the "Connect to the Internet Wizard" to issue the cert (self signed) 2: Used IIS to get cert and then run the "Connect to the Internet Wizard" and use the option dont change the cert. 3: Import all certs to ISA (wildcard, root, mail and team) and put in personal, and trusted root. If I just want to get OWA to work I can with no issues, but if I try to do both OWA and the other SharePoint VS site that I created it just does not work but the funny thing is that it does work on a machine that is in a workgroup on the same vlan...but not over the net ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: amy@xxxxxxxxxxxxxxxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx