[
https://issues.apache.org/jira/browse/CASSANDRA-10227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua McKenzie updated CASSANDRA-10227:
----------------------------------------
Summary: Can't accept remote connections using VirtualBox host-only adapter
(Windows 10). (was: Can't accept remove connections using VirtualBox host-only
adapter (Windows 10).)
> Can't accept remote connections using VirtualBox host-only adapter (Windows
> 10).
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-10227
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10227
> Project: Cassandra
> Issue Type: Bug
> Reporter: Paul Knopf
>
> Before I begin, I have created a simple project that reproduces this issue.
> It uses Vagrant (1.7.4) to dynamically setup the box for each network adapter.
>
> https://bitbucket.org/theonlylawislove/cassandrahostonlyadapter/commits/tag/network-host-only
> - Not working
>
> https://bitbucket.org/theonlylawislove/cassandrahostonlyadapter/commits/tag/network-public
> - Working
> Check out each tag, then run "vagrant up". This will setup the VM. Then run
> CassandraTest.exe on the host machine to test remote access. The "public
> network" vm works with remote access, but the "host-only network" does not.
> Within each VM (ssh), I can succesfully connect to the IP (either host-only
> or public) using cqlsh. So, Cassandra is setup and configured properly.
> I also added the VM logs for using both the public network adapter, and the
> host-only adapter.
> Any guidance on this issue would be greatly appreciated.
> I would like to add that I have successfully used other applications with
> host-only adapter on Windows 10, such as Redis and Postgres. There is
> something unique about Cassandra, and I am honestly not smart enough to
> figure it out. Something is definitely broken though :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
