We've discovered another example of strange behaviour in Windows Active Directory that's at the root of this problem. Basically what's happening is that the LDAP interface of Active Directory which it exposes to the outside world, and an Internal API within Active Directory have different NetBIOS? names for the Domain. This means that the sync service is sending one NetBIOS? name, and CensorNet is expecting another. As you may guess, this means that it fails.

The fix is simple:

1. Log into the censornet command line as root and run:

nmblookup -A [AD server IP address]

For example, my AD server is 192.168.1.21, so I'd do:

nmblookup -A 192.168.1.21

2. On the Active Directory server, login as Administrator and run "regedit". Search through until you find:

HKEY_LOCAL_MACHINE\SOFTWARE\CensorNet\Synchronization Service

Change the SyncDomain? key to be the same as the one returned by the nmblookup. Save and exit regedit. Now from within the Services on your Active Directory server, restart the Censornet Synchronization service. It should now work.

-- BigMick - 14 Apr 2010