@T D The original problem is related to the fact the 6667 port is not mapper in the hosting VM. As you a running your cluster in docker container, the hosting VM should perform its launch with proper port mappings. In order to enable this port connect to your VM using ssh -p 2122 root@localhost and perform the following steps: 1. Disable sandbox service: systemctl disable sandbox.service init 6 2. Alter the launch script: vi /root/start_scripts/start_sandbox.sh 3. Add this line after the last -p operation and save the script: -p 6667:6667 \ 4. Delete existing container docker rm sandbox 5. Enable sandbox service: systemctl enable sandbox.service init 6 After this you will be able to check that the port is opened using this command: docker ps | grep 6667 Now add port forwarding in the NAT configuration of your VM: kafka=>TCP=>127.0.0.1=>6667=> =>6667 After this you will be able to connect to the kafka broker on your sandbox. ... View more

As you are accesing it from the Cross realm, your widows-based clients should know the KDC location to create proper SPNEGO token. You need either create a separate policy in your AD for that type of users or you can manually from command line add mappings in client machine's registeries so that they would know about your Hadoop realm KDC: ksetup /addkdc HADOOP.DOMAIN.COM hadoop.nodewithkdc.com ksetup /addhosttorealmmap hadoop.nodewithkdc.com HADOOP.DOMAIN.COM ... View more

Had the same error in my config, fixing it to proposed resolved an issue ... View more