and is that the same name on your cert? Does the value for the FQDN property on the connector match the name in the cert?
On Mon, Sep 21, 2009 at 4:25 PM, James Kerr <cluster...@gmail.com> wrote: > mail.careresource.org > > ----- Original Message ----- > *From:* Tom Kern <tpk...@gmail.com> > *To:* MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com> > *Sent:* Monday, September 21, 2009 3:43 PM > *Subject:* Re: get-exchangecertificate > > What is the FQDN on the send connector you have created? > > > > On Mon, Sep 21, 2009 at 3:06 PM, James Kerr <cluster...@gmail.com> wrote: > >> The thing thats killing me is that it is listed in the subject of the >> cert. When I run get-exchangecertificate | fl * I see the FQDN listed in >> certificate domains and the status is valid and under services SMTP is >> listed. I'm really baffled and becoming unhinged over here. The connector in >> question is my send connector to the Internet. >> >> James >> >> ----- Original Message ----- >> *From:* Dahl, Peter <peter.d...@yum.com> >> *To:* MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com> >> *Sent:* Monday, September 21, 2009 2:19 PM >> *Subject:* RE: get-exchangecertificate >> >> When I have seen this error the SMTP connector property for “Specify the >> FQDN this connector will provide in response to HELO or EHLO” did not match >> the subject of the certificate. >> >> >> >> *From:* James Kerr [mailto:cluster...@gmail.com] >> *Sent:* Monday, September 21, 2009 10:15 AM >> *To:* MS-Exchange Admin Issues >> *Subject:* Re: get-exchangecertificate >> >> >> >> Thanks Simon, >> >> >> >> Now I just have to figure out why I'm getting the following error then >> >> >> >> Event ID 12014 Source MSExchangeTransport >> >> >> >> Microsoft Exchange couldn't find a certificate that contains the domain >> name* mail.domain.com* in the personal store on the local computer. >> Therefore, it is unable to support the STARTTLS SMTP verb for the connector >> Internet SMTP with a FQDN parameter of *mail.domainname.com*. If the >> connector's FQDN is not specified, the computer's FQDN is used. Verify the >> connector configuration and the installed certificates to make sure that >> there is a certificate with a domain name for that FQDN. If this certificate >> exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the >> Microsoft Exchange Transport service has access to the certificate key >> >> My cert has the correct CN of *mail.domainname.com* so I dont underdstand >> why I'm getting this error. >> >> ----- Original Message ----- >> >> *From:* Simon Butler <si...@sembee.co.uk> >> >> *To:* MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com> >> >> *Sent:* Monday, September 21, 2009 10:06 AM >> >> *Subject:* RE: get-exchangecertificate >> >> >> >> I = IMAP >> >> P = POP >> >> W = Web >> >> S = SMTP >> >> >> The . means that you are missing one, which is U, for Unified >> Communications. If you do not have that role installed then it will not be >> listed. >> >> >> >> Therefore your certificate seems fine. >> >> >> >> Simon. >> >> >> >> >> >> >> >> -- >> Simon Butler >> MVP: Exchange, MCSE >> Sembee Ltd. >> >> e: si...@sembee.co.uk >> w: http://www.sembee.co.uk/ >> w: http://www.amset.info/ >> >> w: http://blog.sembee.co.uk/ >> >> >> >> >> >> >> >> *From:* James Kerr [mailto:cluster...@gmail.com] >> *Sent:* 21 September 2009 15:01 >> *To:* MS-Exchange Admin Issues >> *Subject:* get-exchangecertificate >> >> >> >> When I run this command I see the SSL cert that I have setup for IIS, >> SMTP, POP and IMAP but listed under services it says IP.WS<http://ip.ws/>. >> Should it list the services I installed the cert for? What is >> IP.WS<http://ip.ws/>? >> Anyone know? >> >> >> >> James >> >> >
