Registering the proxy with the Data Security module/content/support/library/shared/v75/web_dlp/proxy_dss.aspx<H2>Web Security Gateway Anywhere Getting Started Guide v7.5</H2>
<H3>Registering with the Data Security Management Server</H3>
<OL>
<LI>Ensure that Content Gateway and Data Security Management Server systems are running and accessible, and that their system clocks are approximately synchronized. </LI>
<LI>Ensure the Content Gateway machine has a fully qualified domain name (FQDN) that is unique in your network. Host name alone is not sufficient. </LI>
<LI>If Content Gateway is deployed as a transparent proxy, ensure that traffic to and from the communication interface ("C" on a V-Series appliance) is not subject to transparent routing. If it is, the registration process will be intercepted by the transparent routing and will not complete properly. </LI>
<LI>Make sure that the IPv4 address of the eth0 NIC on the Content Gateway machine is available (not required if Content Gateway is located on a V-Series appliance). eth0 is the NIC used by the Data Security Management Server during the registration process. </LI>
<LI>After registration, the IP address can move to another network interface on the same machine; however, that IP address is used for configuration deployment and must be available as long as the 2 modules are registered. </LI>
<LI>From the Content Gateway Manager, select <B>Configure　&gt; Basic　&gt; General</B>.</LI></OL>
<P>Click <B>View Complete Document</B> for more.</P>