Back at it this morning and, while I don't quite get what's happening, I consider this resolved. This morning I did the following: removed a prior install of Apache Zeppelin after I realized that after a reboot, it still responded to localhost:8080 confirmed it was indeed gone started up Virtual box and started the sandbox then zeppelin still responded to localhost:8080, which really confused me then tried localhost:9995, to which a different zeppelin page responded - so that was a good thing then, remembering something from a previous experience, I tried 127.0.0.1:8080 and then Ambari responded with its login page This is now the second time I have seen localhost and 127.0.0.1 be treated differently; one of these days I'll have to figure out why. But for now, I'm back in business and continuing the tutorial. Thanks everyone for their help! Cecil ... View more

@Michael Young Here you go: [root@sandbox ~]# ifconfig -a docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 inet6 fe80::42:b5ff:fe1d:634f prefixlen 64 scopeid 0x20<link> ether 02:42:b5:1d:63:4f txqueuelen 0 (Ethernet) RX packets 1462 bytes 512300 (500.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1942 bytes 216711 (211.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::a00:27ff:fea5:537e prefixlen 64 scopeid 0x20<link> ether 08:00:27:a5:53:7e txqueuelen 1000 (Ethernet) RX packets 2256 bytes 271935 (265.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1972 bytes 734622 (717.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 12 bytes 1020 (1020.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12 bytes 1020 (1020.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth6cc2f97: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::3485:4aff:fe87:17d0 prefixlen 64 scopeid 0x20<link> ether 36:85:4a:87:17:d0 txqueuelen 0 (Ethernet) RX packets 1462 bytes 532768 (520.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1950 bytes 217359 (212.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@sandbox ~]# ... View more

@Michael Young mine look similar: ... View more

@Satish Bomma apparently the sandbox is configured differently (or the docker and VM are getting confused). See snippet ... View more

@Michael Young The tutorial is http://hortonworks.com/hadoop-tutorial/learning-the-ropes-of-the-hortonworks-sandbox. I clicked on the "Ask a Question" at the end of the tutorial and it provided the tags hdp-2.5.0 and tutorial-160. When I use port 2222 and ifconfig I get this (and I have to use the reset password): $ ssh root@127.0.0.1 -p 2222 root@127.0.0.1's password: Last login: Fri Dec 16 16:55:32 2016 from 10.0.2.2 [root@sandbox ~]# ifconfig eth0 Link encap:Ethernet HWaddr 02:42:AC:11:00:02 inet addr:172.17.0.2 Bcast:0.0.0.0 Mask:255.255.0.0 When I use port 2122 I can use the hadoop password and see this: $ ssh root@127.0.0.1 -p 2122 root@127.0.0.1's password: Last login: Fri Dec 16 18:05:07 2016 from 10.0.2.2 [root@sandbox ~]# ifconfig docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 The two give me a different IP address (slightly). But both time out. ... View more