Link to home
Start Free TrialLog in
Avatar of thebradnetwork
thebradnetworkFlag for United States of America

asked on

DFS stopped working after loading Endpoint

We have loaded Symantec Endpoint on 6 of our servers running DFS and after running the anti virus they have quit working. We are getting these errors in this order in the Event Log:

13565,13506,1355

We have tried to demote and promote the server and still nothing has seem to work. We have also tried non athoritative restore (D2). It ran successfully without error for a few hours but still wouldnt share the syslog or netlogon.

We have an outbreak of W32.downadup.B and we have removed it from all of the servers and we are still working on the workstations. We have found that by loading Endpoint it is able to maintain the virus spead more efficently than the older versions of Symantec Anti Virus. We arnt sure if that would have an effect on the server but I think that may be something you will need to know.
Avatar of tntmax
tntmax
Flag of United States of America image

Can you confirm that the firewall is relaxed on the servers in Endpoint? There might be blocked traffic. Can you check the logs?
Avatar of thebradnetwork

ASKER

We installed Endpoint without the firewall protection. The only feature that we have installed is the anti virus portion.
Did you exclude the dfs shares from the AV scans? That and sysvol?
ASKER CERTIFIED SOLUTION
Avatar of tntmax
tntmax
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I don't believe so...just out of curiosity why would that effect it? I will try that.
MS recommendation based on previous support calls with them about DFS issues.
Got ya...thank! I will let you know what happens.
Hi,

Are they Windows 2008 64-bit servers?

Check this:

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/83c0c86ee25d3cd3802574d500432c6a?OpenDocument


A Symantec Certified Specialist @ your service
We arnt sure if this is what fixed it. We think it was more due to not having windows updates as well as having the conficker virus still on our network.