Choose from several options for complete web, email and data security.
Evaluate Websense products by watching demos and installing evaluation software.
Learn how Websense solutions help keep our customer safe, secure and productive
Get information on product updates, support resources and more.
Get the most out of support in five simple steps.
Find tools and assets to help sell Websense solutions.
Come work for the global leader in unified information security.
When trying to install the Email Security Gateway version 7.6, I get the following message after entering the IP address of the apliance.
"cannot connect to the specified email security gateway appliance. Please verify network connectivity and appliance network interface configuration.
I can connect to and manage the appliance using a browser and the same IP address i am entering during this step. The IP address I am entering is the the address assigned to interface "c". This is the correct interface, isn't it?
Where are you entering the IP address? A lot of the management is not done via the C interface but rather by the E1 or P1 interface. Some of it can be moved to the C interface by setting a module route on the appliance.
Ray Pesek:Where are you entering the IP address? A lot of the management is not done via the C interface
in the websense email security installer configuration page. It says "specify the email security gateway appliance to be managed and it asks for an IP address. I have screen shots but, I'm not sure how to attach them to a post here.
Sorry, I was not specific enough. Are you entering this in the appliance configuration or in the Windows TRITON server?
In TRITON, when you look at Email Security -> Appliances it shows the C IP address. In TRITON, when you click the Appliances button, it shows the C interface. But the Personal Email Manager uses the E1 or P1 IP address unless you add a specific hotfix to the appliance and TRITON server.
I found an article dealing with the exact problem I was having. Apparently we had to set up a route on the appliance from the appliance to the network where the sql server was located.
Ah yes, I know exactly where you are. That one caused us a lot of problems because we wanted to use a DNS entry instead of an IP address for DR purposes. Change the DNS CNAME to the DR site SQL server and it all just works. But all DNS resolution on the ESG is done from the E1 or P1 interface and never by the C interface.
Our E1/P1 interface can only resolve DNS on the Internet and not our internal zones. The C interface has the connectivity to resolve the internal DNS zones but that doesn't matter. So we were forced to put in an IP address.