Hi,

Sounds like you don't have events configured correctly.
http://world.episerver.com/documentation/Items/Developers-Guide/Episerver-CMS/75/Event-management/WCF-event-management/

/Mikael

Mikael is right, it is probably an issue with the remote event setup that prevents the cache synchronization. I just wanted to add that the page modified checkbox has nothing to do with cache sync, cache is always synced on save/publish.

Then please help me understand:

On Edit server (10.205.162.12) i have setup following:
<system.serviceModel>
<serviceHostingEnvironment multipleSiteBindingsEnabled="true" aspNetCompatibilityEnabled="true" />

<services>
<service name="divi.cms/EPiServer.Events.Remote.EventReplication" behaviorConfiguration="DebugServiceBehaviour">
<endpoint
name="RemoteEventServiceEndPoint"
contract="EPiServer.Events.ServiceModel.IEventReplication"
bindingConfiguration="RemoteEventsBinding"
address="net.tcp://localhost:13101/RemoteEventService"
binding="netTcpBinding" />
</service>
</services>

<client>
<endpoint name="divi.cms.webshop-10.200.162.11"
address="net.tcp://10.200.162.11:13101/RemoteEventService"
bindingConfiguration="RemoteEventsBinding"
contract="EPiServer.Events.ServiceModel.IEventReplication"
binding="netTcpBinding"/>
</client>

<behaviors>
<serviceBehaviors>
<behavior name="DebugServiceBehaviour">
<serviceDebug includeExceptionDetailInFaults="true" />
<!--TODO: the option should be only in test environment true in the production should be false-->
</behavior>
</serviceBehaviors>
</behaviors>
<bindings>
<netTcpBinding>
<binding name="RemoteEventsBinding">
<security mode="None" />
</binding>
</netTcpBinding>
<customBinding>
<binding name="RemoteEventsBinding">
<binaryMessageEncoding />
</binding>
</customBinding>
<basicHttpBinding>
<binding name="ETP">
<security mode="Transport" />
</binding>
<binding name="ETP1" />
</basicHttpBinding>
</bindings>
</system.serviceModel>

on Front (10.200.162.11) server:

<system.serviceModel>
<serviceHostingEnvironment multipleSiteBindingsEnabled="true" aspNetCompatibilityEnabled="true" />
<services>
<service name="divi.cms/EPiServer.Events.Remote.EventReplication" behaviorConfiguration="DebugServiceBehaviour">
<endpoint
name="RemoteEventServiceEndPoint"
contract="EPiServer.Events.ServiceModel.IEventReplication"
bindingConfiguration="RemoteEventsBinding"
address="net.tcp://localhost:13101/RemoteEventService"
binding="netTcpBinding" />

</service>
</services>
<client>
<endpoint
name="divi.cms.backoffice-10.205.162.12"
address="net.tcp://10.205.162.12:13101/RemoteEventService"
bindingConfiguration="RemoteEventsBinding"
contract="EPiServer.Events.ServiceModel.IEventReplication"
binding="netTcpBinding" />

</client>
<behaviors>
<serviceBehaviors>
<behavior name="DebugServiceBehaviour">
<serviceDebug includeExceptionDetailInFaults="False" />
<!--TODO: the option should be only in test environment true in the production should be false-->
</behavior>
</serviceBehaviors>
</behaviors>
<bindings>
<netTcpBinding>
<binding name="RemoteEventsBinding">
<security mode="None" />
</binding>
</netTcpBinding>
<customBinding>
<binding name="RemoteEventsBinding">
<binaryMessageEncoding />
</binding>
</customBinding>
<basicHttpBinding>
<binding name="ETP">
<security mode="Transport" />
</binding>
<binding name="ETP1" />
</basicHttpBinding>
</bindings>
</system.serviceModel>

First of all you don't need the client configuration  on the front server since that one is only going to listen to the events from the admin server.
Second you should on the front end server change the service adress from localhost to the same as the client-adress you are calling from the admin server.