Solved

Websense DC Agent error 4096

Posted on 2011-02-21
4
1,557 Views
Last Modified: 2012-06-22
I have Websense 6.3.3 running on windows 2003 R2 with Pix integration. Websense is working fine but I keep getting Event ID 4096 on my websense server for domains that are not in use.

System error while enumerating the domain controllers. domain: WORKGROUP ecode: 2107 : message: The device is not connected.

System error while enumerating the domain controllers. domain: MSHOME ecode: 2107 : message: The device is not connected.

I have been trying to figure out where Websense is getting this info. If I go to My Network Places I see these networks listed as well as our domain. We have four instances of websense runninig at 4 locations on different subnets. The message is more of a nuinsance than a problem because all 4 servers log the same error. My dc_config.txt file has the correct dc listed so I am assuming websense is getting this from active directory. Can someone tell where I can look?
0
Comment
Question by:InSearchOf
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 29

Accepted Solution

by:
pwindell earned 500 total points
ID: 34952692
You have at leaast two machine on the LAN that are set as worgroup machines,...one using WORKGROUP and the other one using MSHOME.

Websense appearantly doesn't have the sense (yes pun intended) to know the difference between a Workgroup and a Domain and is expecting to find a "Domain Controller" for those two items,...which is impossible since they don't exist because they are not a Domain but are a workgroup

BTW - Workgroups and Domains are not "networks".  Networks are cables, switches, hubs, and routers.  Workgroups and Domians are Administrative Boundaries & Environments.
0
 

Author Comment

by:InSearchOf
ID: 34953570
Thanks for the info and the destinction. So I either find the workgroup PCs and join them to our Domain or get get use to seeing the errors.
0
 
LVL 29

Assisted Solution

by:pwindell
pwindell earned 500 total points
ID: 34953753
....or rename the Workgroup name to match the spelling of the Netbios name of the real Domain.

...or yes,...get used to seeing the errors,...and ignore them.
0
 

Author Comment

by:InSearchOf
ID: 34954147
Ok. The first suggestion sounds good. Thanks for the help.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
Part Two of the two-part Q&A series with MalwareTech.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

635 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question