My problem getting SBS/Exchange server to receive mail through a new ASA 5505 was solved when it was determined 'I' was suffering from bug CSCti38867, where the ASA fails to proxy arp. As a result, I am no longer using a separate static IP for the external interface of the ASA and the public IP of my Exchange server. The interface is now the public IP.
I'm greatly relieved to have found the solution to this bug, even if it meant settling for a single IP. However, I have a GoDaddy SSL cert on my server for use with the RWW and OWA functions of SBS 2003. The problem is, now that I'm setting up AnyConnect, when I attempt to connect to the public IP on the ASA, AnyConnect sees the SBS certificate. I had created a self-signed identity cert on the ASA for use with AnyConnect via IPSec, but the client bombs out anyway.
I thought I read that it's possible to get a GoDaddy SSL (or I assume other basic SSL) cert to perform 'double duty'. I'm not sure mine is compatible (the extensions didn't seem to conform to what was mentioned in that article--you can tell I haven't spent much time with certs). Can I keep my current SSL cert and configure the ASA and AnyConnect in such a way that it ignores it and just deals with the self-signed cert, or am I forced to replace the SSL cert? Any help on setting this up is much appreciated. Thanks!