asked on

Exchange 2007 Certificate SAN mismatch

Exchange 07, on sbs2008

Best Practice Analyzer states

The subject alternative name (SAN) of SSL certificate for https:mail.seainc.net/autodiscover/autdiscover.xml does not appear to match the host address. Host address: Mail.seainc.com. Current SAN: DNS Name=Seainc.com, DNS Name=remote.seainc.com, DNS Name=SEADC.seainc.local

our remote mail is at mail.seainc.com/remote, and I get a certificate error saying it's actually "remote.server.com"

How do I correct the certificate?

I type in get-exchangecertificate and it gives me 5 or so thumbs that all but 1 point to remote.seainc.net

How do I point it all too mail.seainc.com

e_aravind

The subject alternative name (SAN) of SSL certificate for https:mail.seainc.net/autodiscover/autdiscover.xml does not appear to match the host address.

>> What are the other SAN entries you have on this cert.
do you have the CAS servers FQDN name listed in the SAN values?

ASKER CERTIFIED SOLUTION

Akhater

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

JHULBE1

ASKER

I just ran the wizard, and am rebooting, we'll see what happens.

JHULBE1

ASKER

Now mail.seainc.net/remote does nothing

Akhater

even internally ? are all services up ? any relevant error in the evnt log ?

JHULBE1

ASKER

I re-configured it to remote.seainc.net to see if it would come back up. It does work internally.

JHULBE1

ASKER

still down externally

Akhater

if it works internally it shouldn't be exchange

do you have port 443 forwarded to the ip address of your exchange server ?

any erros in event log ?

JHULBE1

ASKER

Looks like vpn is down now. I get pass the firewall, and see "allow in eth0 myipaddress port 1723" but It fails to connect

Akhater

can't see how this could happen !

check the event log...

JHULBE1

ASKER

Event log had some generic distributedCOM errors in application.

Don't really see anything worth mentioning in event log

JHULBE1

ASKER

Terminal services is littered with Event IDs400

The Terminal Services Gateway (TS Gateway) server must be available on the network and the appropriate services must be running on the TS Gateway server. The Terminal Services connection authorization policy (TS CAP) and Terminal Services resource authorization policy (TS RAP) stores must also be available, so that these policies can be evaluated to determine whether remote clients meet policy requirements. TS CAPs specify who can connect to a TS Gateway server. TS RAPs specify the internal network resources (computers) that clients can connect to through a TS Gateway server. If TS CAPs and TS RAPs are not available, the TS Gateway server will not be available for client connections.

JHULBE1

ASKER

I reloaded a configuration of my watchgaurd firewall before I started having any issues. Checked the A-records with my domain host. Rebooted, and waited 20-30 minutes before anything.

Seems to be corrected. Thanks!

JHULBE1

ASKER

Thanks

Akhater

Thanks for the update and for the points