Open Tradefreak opened 4 years ago
That is most likely something changed in upstream Bitcoin Core, so not specific to Namecoin. I think @xaya had some issues with this as well. Do you recall any details here (perhaps it is Windows specific)?
If the question was addressed to me: The Windows-firewall is open on port 8336 for internal IPs, the server farm is an Active Directory.
It was not, it was addressed to Andrew (@xaya) who I believe had similar issues on Windows in the past and may be able to provide more details. In any case this is probably an issue from upstream Bitcoin and not Namecoin. Can you try if Bitcoin Core works for you with the same settings?
have you tried -rpcbind=0.0.0.0 (or ip of your network card)
I believe you need this to connect now. iirc
While the server operation of the Namecoin Core Qt v. 0.13.99 (with the additional "Manage names" tab) made no problems, the actual Namecoin Core Qt v. 0.19.0.1 in server mode can't be connected anylonger through the internal network. E.g. if you have the node running in server mode started with the additional commands
-rpcallowip=127.0.0.1 -rpcallowip=192.168.0.3
on the machine with the IP 192.168.0.2 and want to make RPC-requests from 192.168.0.3, it's no longer possible. Even on the same machine it works only with requesting at 127.0.0.1:8336. Both machines running with Windows Server 2019.