Remote trades are not copying to remote followers (nodes) when using Remote Copy

When trades aren't reaching a follower over Remote Copy, the cause is almost always a blocked port, a misconfigured network adapter, or a leader/follower setting that fell out of sync. This article walks through diagnosing and fixing the connection between a Replikanto leader and a remote follower (node) on the same local network.

Symptoms

• The leader sends trades, but the follower never receives them.
• The follower's Replikanto node does not appear connected, or appears connected but stops relaying trades.
• Everything looks correctly configured on both sides, yet copying still fails.

Quick Connectivity Test

Before changing any settings, confirm whether the follower's Replikanto node is even reachable on the network. On the leader computer, open a web browser and navigate to:

http://<follower_ip>:<port>/replikanto_node

For example, if the follower's IP is 192.168.1.112 and the port is 4547, the URL would be: http://192.168.1.112:4547/replikanto_node

If the node is active and reachable, the page confirms that the Replikanto node is enabled. If the page does not load, there is a network or firewall block between the two machines — go through the causes below.

Common Causes and Solutions

Firewall blocking the follower's port

Both computers must be on the same local network, and the follower must allow inbound traffic on the port Replikanto uses (4547 by default, or the port you defined). Check first whether the follower's Windows Firewall has an inbound rule opening that port — this guide walks through creating it. Once the rule exists, test with a Sim account until trades are reaching the follower, and keep the NinjaTrader Logs tab open on both computers while you test — the logs on either side usually show exactly what's failing.

If trades still aren't copying after the inbound rule is in place, temporarily disable the follower's Windows Firewall for all profiles (domain, public, private) and test again:

• If it works with the firewall off, turn the firewall back on and re-check the inbound rule — the Public profile is often the one left unselected. Select it and test again.
• If it still doesn't work with the firewall off, the block is coming from somewhere else (see the next causes).

Wrong network adapter selected

On a computer with two or more network interfaces, Replikanto shows the IP of the first adapter it finds — which isn't always the one actually connected to your LAN. If the follower's active interface isn't the one Replikanto is using, right-click inside Replikanto, select Properties, open Network, then Adapter, and select the interface that's actually on your network (see where the Network Adapter setting is and what to select). Changing the adapter changes the follower's IP address, so you'll also need to update that IP in the leader's Remote Node settings, then test again.

Third-party antivirus or security software

If the follower still isn't receiving trades, check for other software with its own firewall — antivirus suites such as Malwarebytes, Norton, or McAfee are common culprits. Temporarily disable its firewall component and test again; if that resolves it, add a Replikanto/NinjaTrader exception rather than leaving it disabled.

Leader computer recently rebuilt or changed

If the leader computer was recently rebuilt or had hardware changes (such as a CPU upgrade), its firewall rules and Replikanto configuration may need to be reconfigured. On the leader computer, check the following:

• The Remote Node settings in Replikanto have the correct follower IP address and port — right-click the Remote Node, select Properties, and confirm the IP and port match the follower's current settings.
• An inbound firewall rule exists for TCP port 4547 on the leader too. Even though the leader initiates the connection, Windows Firewall can still block the return traffic.
• NinjaTrader.exe is allowed through the leader's Windows Firewall, both inbound and outbound.
• If the leader runs antivirus software with its own firewall (Malwarebytes, Norton, McAfee, etc.), it isn't blocking NinjaTrader's network communication.

Prevention

• After rebuilding a leader or follower machine, or changing its network hardware, re-verify the firewall rule and the Network Adapter setting before assuming Remote Copy itself is broken.
• Re-check the Network Adapter setting on both machines first when trades stop copying on a previously-working setup — it's one of the most common causes alongside firewall rules and the port number.
• Run the Quick Connectivity Test above right after any network or hardware change, before starting live trading.

Related Articles

• How can I copy trades between my machines over the same local network?
• Where is the Network > Adapter setting, and what should I select?
• Why can't I copy the trades to the other Replikanto via the local network?