Symptoms: Censornet Sync service starts, but is unable to connect.
> >
Symptoms:CensorNet ADSync service starts, but is unable to connect.
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.