Forum Replies Created
Not sure if anyone can help .. but also when I look in the log for the asa the packet comes in and then reads:
6 Aug 04 2016 09:51:41 18.104.22.168 64148 10.0.9.9 3389 Teardown TCP connection 270840007 for outside:22.214.171.124/64148 to inside:10.0.9.9/3389 duration 0:00:00 bytes 0 No valid adjacency
The server names were just examples – in essence there are a number of servers (not web servers and not all terminal servers) which face the internet and as a result the SSL needs to match the server name.
In this case as the cert was issued to servername.abc.co.uk and the server is called servername.local … they obviouslly do not match
Tricking the exchange server using the scripts from godaddy was simple – I didn’t have to rename the server (its still called email.local but the certificate works as email.abc.co.uk)