Windows Certificate Services – Setup a CRL
Setup a CRL KB ID 0000957 Problem One of the often-overlooked tasks in a Public Key Infrastructure (PKI) deployment is configuring your Certificate Services Certificate Revocation List (CRL). For smaller deployments with only one server, you don’t need to worry about complex design considerations (though a CRL doesn’t have to be hosted on a Certificate Services server). In my test environment, I have only one PKI server,...
Juniper SRX Cluster (Active / Standby)
SRX Cluster KB ID 0000990 Problem I’ve had very little exposure to JUNOS and Juniper equipment, and later in the year I have to deploy some for a client in a failover cluster. So I had a good look round on the Internet, and found loads of good blog posts and KB articles like this one. The problem is they are all geared to setting up a cluster, they ASSUME you then know about security zones, how to add default routes, and setup...
451 4.7.0 Temporary Server Error
451 4.7.0 KB ID 0001823 Problem If you attempt to connect to and send mail via command line to your Exchange Server, you may see the following error after you end the data section of the operation. 451 4.7.0 Temporary server error. Please try again later. PRX5 Solution 451 4.7.1 Error Log into Exchange Amin Center > Mail Flow > Receive Connectors > Default Frontend {Server-Name} > Edit > Scope > Select the IPV4 entry...
FortiGate Securing Remote Administration
KB ID 0001734 Problem When considering Securing FortiGate remote administration, I’ve written about changing the https management port to something other than TCP 443 before, I suppose that’s security by obfuscation (though even a script kiddy with one hours experience, will be able to spot an html responses). Typically with other vendors you limit remote administration access, to specific IP addresses (or ranges). So...
VMware – {hostname} could not reach isolation address: none specified
KB ID 0000445 Problem Seen on vSphere: Error Host {hostname} could not reach isolation address:none specified. Solution 1. In my case the host did NOT have a default gateway, (this had occurred because the subnet mask of the server had been entered incorrectly when the server was built. So the default gateway appeared to be on a different network). 2. With the offending host selected, Configuration > DNS and Routing >...