I had tried that and it still caused the same issue.
Thankfully I found a solution but I’m unsure as to why it works.
I tried to ping 192.168.99.11 from my Windows CMD and there was no response from the Docker-machine even though that was the IP it listed when I did “docker-machine ip default” (default being the name of the vm).
By doing “ifconfig” within the Boot2Docker VM (but not inside the container), I was able to locate another IP listed under eth0. This IP looks something like 134.36.xxx.xxx to me and is pingable. With the Mongo container running I can now access the database from within Mongo Management Studio by connecting to 134.36.xxx.xxx:32768 and manipulate the data from there.
I find it strange that using the VM IP does not work since that is where the container is port forwarding to?