@Oriane, When you are logged into the virtualbox do a 'docker ps' to see if the container is running: $ ssh -p 2122 root@localhost Last login: Tue Feb 21 03:48:44 2017 [root@sandbox ~]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9cb49389f795 sandbox "/usr/sbin/sshd -D" 12 weeks ago Up 15 hours 0.0.0.0:1000->1000/tcp, 0.0.0.0:1100->1100/tcp, 0.0.0.0:1220->1220/tcp, 0.0.0.0:1988->1988/tcp, 0.0.0.0:2100->2100/tcp, 0.0.0.0:2181->2181/tcp, 0.0.0.0:4040->4040/tcp, 0.0.0.0:4200->4200/tcp, 0.0.0.0:5007->5007/tcp, 0.0.0.0:5011->5011/tcp, 0.0.0.0:6001->6001/tcp, 0.0.0.0:6003->6003/tcp, 0.0.0.0:6008->6008/tcp, 0.0.0.0:6080->6080/tcp, 0.0.0.0:6188->6188/tcp, 0.0.0.0:8000->8000/tcp, 0.0.0.0:8005->8005/tcp, 0.0.0.0:8020->8020/tcp, 0.0.0.0:8040->8040/tcp, 0.0.0.0:8042->8042/tcp, 0.0.0.0:8050->8050/tcp, 0.0.0.0:8080->8080/tcp, 0.0.0.0:8082->8082/tcp, 0.0.0.0:8086->8086/tcp, 0.0.0.0:8088->8088/tcp, 0.0.0.0:8090-8091->8090-8091/tcp, 0.0.0.0:8188->8188/tcp, 0.0.0.0:8443->8443/tcp, 0.0.0.0:8744->8744/tcp, 0.0.0.0:8765->8765/tcp, 0.0.0.0:8886->8886/tcp, 0.0.0.0:8888-8889->8888-8889/tcp, 0.0.0.0:8983->8983/tcp, 0.0.0.0:8993->8993/tcp, 0.0.0.0:9000->9000/tcp, 0.0.0.0:9090->9090/tcp, 0.0.0.0:9995-9996->9995-9996/tcp, 0.0.0.0:10000-10001->10000-10001/tcp, 0.0.0.0:10500->10500/tcp, 0.0.0.0:11000->11000/tcp, 0.0.0.0:15000->15000/tcp, 0.0.0.0:16010->16010/tcp, 0.0.0.0:16030->16030/tcp, 0.0.0.0:18080->18080/tcp, 0.0.0.0:19888->19888/tcp, 0.0.0.0:21000->21000/tcp, 0.0.0.0:42111->42111/tcp, 0.0.0.0:50070->50070/tcp, 0.0.0.0:50075->50075/tcp, 0.0.0.0:50095->50095/tcp, 0.0.0.0:50111->50111/tcp, 0.0.0.0:60000->60000/tcp, 0.0.0.0:60080->60080/tcp, 0.0.0.0:2222->22/tcp sandbox If the sandbox is listed, check to see that it's up. If not you may have to start it although it is made to start automatically when the vm is started. Post the output of the docker ps if you run into problems. Enjoy! John ... View more

@Aruna Sameera, What is the error you get? Can you ls -l $HOME/.ssh/id-rsa.pub ? ... View more

@T D, Since you get a connection that does not immediately close when you connect from the VM to the container, I think the issue is still in getting the port forwarded from the host to the VM through Virtualbox. It looks like it is listening, but it is not working. When you added 6667 between the host and VM, did you stop and restart the VM after? I don't know if it's needed, but I really think that's where the issue is, since you get a connection from the VM to the container. If you stop the VM, I think it should stop listening on 6667 (and all of the other ports). Maybe even restarting VirtualBox once the VM is down so you can validate that none of the ports are forwarded anymore. Then start it all back up again and see if it gets connected correctly. Let me know, I'm really curious about it! John ... View more

@T D, ssh into the sandbox and start a loop that will show connections to the Kafka service. Ctrl-C will stop the loop. Otherwise while it runs, you can see if new connections are made when you start your service and when you do the telnet test. while true; do (netstat -tan | grep -vi listen | grep 6667); sleep 1; don ... View more

The browser test did not work since Chrome blocked 6667 as unsafe. If you have telnet or putty installed, try to telnet to 127.0.0.1 port 6667 and see if it connects. We're just looking to see if we have the connectivity, we're not trying to produce a record on the topic. ... View more

@T D, You are running the C# and virtualbox with the sandbox all on the same windows host, right? From a Windows CMD prompt, what do you get when you do the following? netstat -ano | findstr "6667 8080" I would expect lines that say "listening" for both ports 6667 and 8080, and that the last number (Process ID) would be the same. I think that would verify that the Virtualbox is listening and forwarding the ports as configured. Also, what happens if you connect to http://127.0.0.1:6667 from a browser on the same host? You should at least get a connection and not a timeout. John ... View more

@Preetha Varma, as @Anna Qin stated, you will get to the sandbox by ssh-ing to port 2222. There are two levels of virtualization in the sandbox. The host VM, which runs on virtualbox, and the sandbox container, which runs under docker in the VM. The container is where all of the sandbox processes run. Port 2222 goes into the container and that is why ambari-admin-password-reset has to be run there. ... View more

@Maher Hattabi, If it works when connected to your local sandbox, but fails when you try to go to io-dell-svr8:50070, you need to see if your computer can correctly resolve the name io-dell-svr8 and make sure there is no firewall blocking the connection to 50070 on that host. From a cmd prompt, you should be able to 'nslookup io-dell-svr8' to see if the name resolves. Telnet is not installed by default on windows 10, but if you have putty, you can try to connect to port 50070 and see if it connects. If it times out, you have firewalls between you that you will have to have opened. I hope this helps! John ... View more