Hmmm, when I try to telnet from host machine at 127.0.01:6667 I get: Connection closed by remote host When I try to ssh from host machine at 127.0.0.1:6667 I get: server unexpectedly closed network connection ---------------------------------- Also tried these experiments from the virtual box with the container running and Kafka started telnet from virtual box telnet 127.0.0.1 6667 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. and netstat -tan | grep :6667 tcp6 0 0 :::6667 :::* LISTEN tcp6 0 0 :::8080 :::* LISTEN tcp6 0 0 :::2222 :::* LISTEN So it looks like the port forwarding is working between host and VM, and VM and container, but not between host machine and container? Of note, I still get the output between the VM and the Container even if the services at those ports are not running, however, the connection is automatically closed as opposed to the CLI waiting for me to input Ctrl-C. So I guess what this shows is that the port forwarding is working, however, I'm not sure it elucidates where the error with Producing to Kafka is, or why the host machine can't make the same connections as the VM with regards to the container. The Windows service configuration is: Kafka uri: http://127.0.0.1:6667 and when I run the service on my host machine and a consumer in the container, this is what I see: bin/kafka-console-consumer.sh --zookeeper localhost:2181 --from-beginning --topic test-topic {metadata.broker.list=sandbox.hortonworks.com:6667, request.timeout.ms=30000, client.id=console-consumer-59653, security.protocol=PLAINTEXT} ^CProcessed a total of 0 messages But no errors on the host machine... ... View more

John, Thank you for the response. Yes, I am running the C# service and VirtualBox on the same windows host. Here is what I get with those two experiments. netstat -ano | findstr "6667 8080" TCP 127.0.0.1:6667 0.0.0.0:0 LISTENING 3344 TCP 127.0.0.1:8080 0.0.0.0:0 LISTENING 3344 TCP 127.0.0.1:18080 0.0.0.0:0 LISTENING 3344 TCP [::1]:62738 [::1]:49154 ESTABLISHED 28080 and for the browser This site can’t be reached The webpage at <a href="http://127.0.0.1:6667/">http://127.0.0.1:6667/</a> might be temporarily down or it may have moved permanently to a new web address. ERR_UNSAFE_PORT @jwhitmore ... View more