I added more specific rules earlier, but they naturally did not help. Despite this, it still gives me a read timeout error. I realize this is not a good practice, but I'm trying to rule out a firewall issue. I've added an inbound Windows Defender rule to allow all local ports and an output rule to allow all remote ports. I can see the port (50000) in the Windows PowerShell prompt, but it gives me a read timeout. I'm trying to connect to a DB/2 container (image: ibmcom/db2) but it gives me a read timeout error. I'm sorry this is so long, but I don't know what details are important in this case. I don't know what changed from then to now, but I only mention it to say it at least can be done. This same image has worked before though. I don't think this is specific to db2, but rather my setup. I can log into the container from within itself, but when I go to the host and try to log in, I get the same read timeout error.
The particular image is ibmcom/db2, however, I also started an SSH server on the same container. Attempts to connect give me a read timeout error. I'm fighting docker which lets me start a container on my Windows machine that launches a network service, but then I can't fully connect.
