natjbrown
asked on
How do I get Websense to display PC name instead of IP address
We have Websense 6.3.2 running on a Windows 2003 server, using port mirroring with a Cisco ASA 5510. Filtering is working the way we want it. However, when we try to run a report using the reporting tools, the activity is listed by IP address instead of by user or by machine name. Our DHCP server winds up giving people new IP addresses every few days, so this is not very effective for us.
I checked the eimserver.ini file, and found DNSlookup was set to "AUTO". I changed it to "ON", but that had no effect. Where do I go to change this?
I checked the eimserver.ini file, and found DNSlookup was set to "AUTO". I changed it to "ON", but that had no effect. Where do I go to change this?
btw, have you installed the user identification agent as explained in this url?
Go to http://kb.websense.com and search for 2684 and you'll see the article i'm talking about
Go to http://kb.websense.com and search for 2684 and you'll see the article i'm talking about
ASKER
We are using a DC agent to direct who is able to access different groups of websites. It appears to be working fine, and I can add a new directory object without error.
Where do I verify that Hide User Names in Reports is not selected in Websense Manager for my Delegated Administrator?
Where do I verify that Hide User Names in Reports is not selected in Websense Manager for my Delegated Administrator?
ASKER
I tried to verify that Filtering Service is able to retrieve the user-to-IP mapping from my Transparent Identification Agent (DC Agent) by running the ConsoleClient utility against port 15869.
I got:
==========================
XID User Map PrintSelf
Snapshot time: 04-10-2009 14:03:41.226461
Number of entries in map is : 0
==========================
So obviously something isn't right there.
I got:
==========================
XID User Map PrintSelf
Snapshot time: 04-10-2009 14:03:41.226461
Number of entries in map is : 0
==========================
So obviously something isn't right there.
ASKER
Where do I do this?
"# If the user-to-IP mapping has no names in it, check the settings for your Transparent ID Agent in Websense Manager. Make sure that Enable Authentication is enabled for the desired Agent."
"# If the user-to-IP mapping has no names in it, check the settings for your Transparent ID Agent in Websense Manager. Make sure that Enable Authentication is enabled for the desired Agent."
Open RealTimeAnalyzer and see first if it logs usernames or IPs.
If it logs IPs, then you have a problem in identifying users.
If it logs IPs, then you have a problem in identifying users.
ASKER
It appears to log IPs. I have three ethernet ports on this sever, and it appears that some services are trying to use a port that they shouldn't. I now have disabled one of the ports, and now the RealTimeAnalyzer does not show any traffic. I am going to get someone else in to take a look at this mess.
Would not DC agent, radius agent or one of the other transparent user agents do the trick? Check page 231 of this doc http://kb.websense.com/article.aspx?article=3133&p=12
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
# For Websense Explorer issues, verify that Hide User Names in Reports is not selected in Websense Manager for your Delegated Administrator. This is a frequent cause of the problem.
# Verify that directory objects can be added without error messages appearing.
How do you know if you receive error messages when you add directory objects?
Open the file websense.log and review any errors listed for User Service. Possible errors include cannot connect to LDAP server and invalid credentials.
* If you see the error cannot connect to LDAP server:
1. Verify that User Service is started. If you are running in mixed mode, you might have to run User Service as a domain\admin account.
2. Verify that the port used to connect to your Directory Service is open and listening (netstat, telnet).
3. Verify that the settings for the Directory Service are correct in Websense Manager > Server > Settings > Directory Service.
* If you see the error invalid credentials:
1. Re-enter the password for the Directory Service in Websense Manager > Server > Settings > Directory Service.
2. If User Service is running as a domain\admin account, re-enter the password for User Service.
3. Add a root context for the Directory Service. See KB article 2862.
# Verify that Filtering Service is able to retrieve the user-to-IP mapping from your Transparent Identification Agent (such as DC Agent or Logon Agent). To check this, run the ConsoleClient utility against port 15869. See KB article 3349.
# If the user-to-IP mapping has no names in it, check the settings for your Transparent ID Agent in Websense Manager. Make sure that Enable Authentication is enabled for the desired Agent.