DC cannot write to SYSVOL

[edublogger]

Hi,

 

I have 2 DCs, both Windows Server 2008. I am having a problem replicating the SYSVOL between the two. In the Security Event log I'm getting this error repeatedly:

 

The Windows Filtering Platform has blocked a bind to a local port.

 

 

Application Information:

Process ID: 1256

Application Name: \device\harddiskvolume1\windows\system32\svchost.exe

 

 

Network Information:

Source Address: 0.0.0.0

Source Port: 62994

Protocol: 17

 

 

Filter Information:

Filter Run-Time ID: 0

Layer Name: Resource Assignment

Layer Run-Time ID: 36

 

To me it looks like at authentication problem, but this is my PDC so I don't want to do anything too drastic until it is resolved.

 

If I access the SYSVOLs (\\server1\SYSVOL & \\server2\SYSVOL) from the "working" DC I can access and write to both SYSVOLs. But if I go to the not working server I can't write to the local SYSVOL -- although I can write to the SYSVOL in the other DC -- it gives me a permission denied message. I've checked the permissions and they are correct.

 

GPOs and SYSVOL files are not replicating between the two servers, although AD users and groups works fine.

 

Little help?

 

Thanks.

[3s-gtech]

Start here:

 

Many 5159 events are logged in the Security event log after you disable Windows Firewall and enable the "Filtering Platform Connection" auditing policy

 

You're going to have to look at the state of your DFS-R (or FRS if you haven't changed it over) using the built-in commands like dfsdiag /testdcs, to try to build a picture of what it failing. Be warned - you may be looking at moving over your FSMO roles and demoting your current role holder to get a handle on it.