Problems connecting to internal nodes.

+1 vote
I have an application where I want to set up an internal multichain network. So all nodes would be on the same internal subnet.  In my case it would be any IP in the range of 192.168.1.1 thru 192.168.1.100. I disabled all firewalls and every time I try to connect to the Genesis node I get the error below. A few times it actually did connect so its strange how sometimes it works but most of the time it seems like it stops syncing the blockchain. I tried whitelisting IPs but that did not help although maybe I am not entering the right command for whitelisting. I read somewhere that bitcoin core blocks IPv4 peer addresses that are on the same subnet. Is that true? Is there a way to make this application work?  

multichaind Testnet@192.168.1.19:2787

MultiChain Core Daemon build 1.0 alpha 23 protocol 10005

Retrieving blockchain parameters from the seed node 192.168.1.19:2787 ...

Error: Couldn't connect to the seed node 192.168.1.19 on port 2787 - please check multichaind is running at that address and that your firewall settings allow incoming connections.
asked Sep 2, 2016 by anonymous
Are you able to telnet to that IP address and port?

1 Answer

0 votes
Yes I am able to telnet in and all ports are open. I also just got the same error this time running a chain on a public network of servers so this is not a local network problem. I was trying to add a new node. Sometimes if I try the same node again the error goes away and the node connects.
answered Sep 5, 2016 by dtarsio
hi! were you able to make it work?
...