Event 4096 after Seizing Domain Controller

We had to seize a domain controller due to a crash. After we did, we started seeing the following event in our Websense server whenever the server reboots: (note: "mgrp-server" was the name of the domain controller that crashed)

Type: Warning
Source: WebsenseDCAgent
Event ID: 4096
Event Time: 4/14/2009 1:08:27 PM
User: n/a
Computer: MGRP-WEBSENSE
Description:
The Windows system call NetSessionEnum returned an error for server MEADEAUTO\MGRP-SERVER. Error Code: 53 : The network path was not found.

I first thought this was directly related to Websense but now I'm thinking it might be related to Windows. Any suggestions?

Thanks!
LVL 2
meade470Asked:
Who is Participating?
 
Hypercat (Deb)Connect With a Mentor Commented:
You mean you changed it and are still getting the errors?  Here's a Websense KB article - don't know if it will be helpful, but it does refer to the bad network path type of error:
http://www.websense.com/SupportPortal/SupportKbs/1077.aspx#communication 
0
 
Hypercat (Deb)Commented:
I don't think it's a Windows problem - if it was you would probably be seeing lots of other errors on your other domain controllers.  Is it possible that the Websense server's LDAP connection was set to use that particular DC? If so, you'd just have to change that setting so that it's connecting to a different DC for LDAP.
0
 
meade470Author Commented:
Thanks for the quick response. Websense was set to look at the DC that crashed, but we changed it.
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
meade470Author Commented:
Thanks again.

We were getting no errors when Websense was pointing to the original DC. Once that DC crashed, we pointed Websense to a new DC and the events started showing. The server shown in the event log is the old, failed DC. Somehow it appears that Websense is remembering  the old server even though there is no configuration pointing to it.
0
 
meade470Author Commented:
The problem was with Websense (an .ini file). I awarded the points to hypercat for his help.
0
 
rafatifardCommented:
HI can you tell me how did you resolve this issue, i do have exactly same problem and filtering dose not working
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.