Nodetool or JMX connections failing on remote nodes 

Nodetool commands can be run locally but not on other nodes in the cluster on Windows.

Nodetool commands can be run locally but not on other nodes in the cluster on Windows.

If you can run nodetool commands locally but not on other nodes in the ring, you may have a common JMX connection problem that is resolved by adding an entry like the following in cassandra-env.ps1 on each node:

$env:JVM_OPTS = "$env:VM_OPTS -Djava.rmi.server.hostname=public name"

Cassandra 3.4 and later: the default settings start up JMX only on the local node. In cassandra-env.sh or cassandra-env.ps1, add JMX authentication to contact remote nodes. See Jmx Security for details.

If you still cannot run nodetool commands remotely after making this configuration change, do a full evaluation of your firewall and network security. The nodetool utility communicates through JMX on port 7199.

cassandra-env.ps
Apache Cassandra version File location
Windows 3.0 installations C:\Program Files\DataStax Community\apache-cassandra\conf\cassandra-env.ps1
Windows 3.x installations C:\Program Files\DataStax-DDC\apache-cassandra\conf\cassandra-env.ps1