Opened 9 years ago
Last modified 9 years ago
#14521 closed defect
Remote port only accessible with public network adapter, and not a host-only network adapter (Windows 10). — at Initial Version
| Reported by: | theonlylawislove | Owned by: | |
|---|---|---|---|
| Component: | network/hostif | Version: | VirtualBox 5.0.2 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
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
https://bitbucket.org/theonlylawislove/cassandrahostonlyadapter/commits/tag/network-public
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.
I also added the VM logs for using both the public network adapter, and the host-only adapter.
I realize that the issue is with a 3rd party application, Apache Cassandra. However, if I remember correctly, the host-only adapter worked correctly on Windows 8. I'm sure that the problem is with VirtualBox on the new Windows 10.
Also, these logs were created with the latest test Windows VirtualBox version, 5.0.3-102322.
Any guidance on this issue would be greatly appreciated. If anything, maybe some guidance on some questions I could post to Apache Cassandra forums?
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 :)
