Documentation | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Using DC Agent for Transparent User Identification > Configure domain controller polling in dc_config.txt
Configure domain controller polling in dc_config.txt
Using DC Agent | Web Protection Solutions | v8.5.x | 29-Apr-2022
By default, DC Agent automatically identifies domains and domain controllers at startup, then detects when domains or domain controllers are added or removed from the network. This process is called domain discovery (see Configure DC Agent settings).
DC Agent stores domain and domain controller information in a file called dc_config.txt (located, by default, in the C:\Program Files\Websense\Web Security\bin\ directory on each DC Agent machine).
*
You can edit the dc_config.txt file to change which domain controllers a DC Agent instance polls. Do this, for example, to:
*
Enable load balancing across multiple DC Agent instances.
*
Stop DC Agent from polling domain controllers that don't exist.
*
If you do not want DC Agent or User Service to perform domain discovery, you can create and maintain the dc_config.txt file manually.
*
You can review domain and domain controller information from dc_config.txt in the Security Manager. Go to the Web > Settings > General > User Identification page and click View Domain List.
Note that the DC Agent Domains and Controllers page lists information for the DC Agent instances associated with a specific Policy Server. You may need to use the Policy Server Switch button in the Web toolbar to select the Policy Server associated with the DC Agent instances you want to review.
To edit or create the dc_config.txt file:
1.
Go to the web protection bin folder (by default, C:\Program Files\Websense\Web Security\bin) on the DC Agent machine.
2.
If the dc_config.txt file already exists, make a backup copy in another location.
3.
Create or open the dc_config.txt file using a text editor.
4.
List all of your domains and domain controllers, or verify that all of your domains and controllers are listed. For example:
[WEST_DOMAIN]
dcWEST1.forcepoint.com=on
dcWEST2.forcepoint.com=on
[EAST_DOMAIN]
dcEAST1.forcepoint.com=on
dcEAST2.forcepoint.com=on
If you are editing a file, and domains or domain controllers are missing, you can add them. Before adding entries, run ping <domain dns name> on the DC Agent machine to make sure that the agent can see the new domain.
5.
If there are domain controllers in the list that DC Agent should not poll, change the entry value from on to off. For example:
dcEAST2.domain1.com=off
*
If you configure DC Agent to avoid polling an active domain controller, the agent cannot transparently identify users logging on to that domain controller.
*
If DC Agent's automatic domain discovery has detected a domain controller that should not be used to identify users, set the entry to off, rather than removing it. Otherwise, the next discovery process will re-add the controller.
6.
Make sure that the file includes a carriage return after the last entry.
If this hard return is not included (creating a blank line at the end of the file), the last entry in the file gets improperly truncated, and an error message appears in the websense.log file.
7.
Save your changes and close the file.
8.
Use the Windows Services tool to restart the Websense DC Agent service.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Using DC Agent for Transparent User Identification > Configure domain controller polling in dc_config.txt
Copyright 2022 Forcepoint. All rights reserved.