SubScription Client throwing error

Question

Subscription client is throwing following error:
ERROR: replicator: Job Failed :unable to connect to syndicator: ICE connection ICE Exception: ICE code 405: Unrecognized sender exception:
com.kinecta.net.IOFailureException: unable to connect to syndicator: ICE connection ICE Exception: ICE code 405: Unrecognized sender
     at SiClone.SiCloneIceRequestor.getICEInputStream(SiCloneIceRequestor.java:237)
     at SiClone.SiCloneIceRequestor.onReplicationStart(SiCloneIceRequestor.java:47)
     at SiClone.SiCloneSiteReplicator.run(SiCloneSiteReplicator.java:534)
     at SiClone.SiCloneSiteReplicatorRunner.runJob(SiCloneSiteReplicatorRunner.java:308)
     at SiClone.SiCloneSiteReplicatorRunner.run(SiCloneSiteReplicatorRunner.java:178)
     at com.kinecta.ice.JobScheduler.run(JobScheduler.java:323)
Here siclone.config file:
<siclone last-run-product-code="subscriber" last-run-version="10.1.3.3.0" last-run-os="Windows 7">
<options run-interactive="true" start-browser="true" admin-username="administrator" admin-password="@YWRtaW5pc3RyYXRvcg=="><log filepath="subscriber.log" numfiles="7" filesize="1024" default="info"/>
<proxy proxyset="false" host="" port="-1" ssl-port="-1"/></options>
<defaults>
<ice-delivery-rule/>
</defaults>
<job subscription-id="PROVIDER" url="http://localhost:8890/" username="administrator" password="@YWRtaW5pc3RyYXRvcg==" id="1032432821-1709312003">
<localdir dir="C:\temp"/>
<ice-delivery-rule duration="P86340S" minfreq="P300S" starttime="24:00:00" statusfreq="P60S"/>
</job></siclone>

Answer 1

Hi,
Actually, that would be a different question and really out of the forum. Just some explaination here:
DHCP protocol is used during the communications between client and WDS server. But as we know, we cannot receive a DHCP broadcast from another subnet or VLAN by default. So we need IP helper here to forward DHCP broadcast.
About the setting you can need refer to network device manufacture. Since you have two subnets, there must be a router or switch. Another workaround is just to put WDS and DHCP server into the same subnet with the clients.