Port Forwarding Doesn't Work At All Issue 1675 Docker/for-mac

Dec 13, 2017 - Description I've been successfully using Docksal on Mac with Virtualbox, and now I'm trying to switch from Virtualbox to Docker for Mac.

Hello, I did follow the links you posted at #1 and #2, though I am confused. #1 basically said call Verizon Tech Support. #2 didn't really shed any light on my problem at all - that I was able to make sense of.

Then you tell me to start up my application and see if it works. The question I had was - was there something you wanted me to try before just starting up my application? Because I haven't done anything to the system since the last post you kindly made. So it didn't work then, it doesn't work now - because I didn't receive any further instructions. However as per your instructions I did restart the program, and it still self tests as failing both TCP and UDP at the port.

As another data point - every port I test through the various port testing sites shows as closed - 21, 25, 80, 110, 139, 143, 194, 3389, etc. Interestingly enough, canyouseeme.org shows the port I forwarded and I want opened as No route to host while all the ports above failed as Connection Timed Out. On the GRC port testing site all the ports listed above, including the forwarded port show up as stealthed - GRC makes no distinction for the forwarded port. Also on an inspiration, I went back through the prefab port forwards on my router and did find a premade portforward for my application. I tried using that as well, but it also failed the exact same ways as discussed above. I did have the router firewall set to typical on the port forward tests listed in this post. Here is a link to the application self test Thank you for your efforts so far!

Hi, not sure if this was discussed with any detail, but it is possible for you to succesfully set up your port forward, and it not work. The reason why? Software firewalls. Both windows firewall and norton/trendmicro etc etc et al, can block applications and services. If your router firewall rules settings look similiar to this then I would begin disabling the firewall and start doing my tests again. (192.168.1.5 TCP ANY - 443 (TCP or UDP ANY is important, you can not define the source port)) Remember, it's not enough to port forward in the router for port forwarding to work. You have to have a few things in play.

The service has to be started. Ecs 945gct-m3 driver for mac. the (software) firewall has to allow the service through.

and then the router has to be doing port forwarding. So far it looks like we are focusing on 1 and 3, and not addressing 2. Also take a look at. There might be something you're missing that is addressed in that article. If you could take a picture of your port forwarding rules, and then give us a link or post the image in here, that would also help us to understand if you did the 'actual port forwarding' correctly. Report back to homebase. Hello Thank you for taking the time to consider my issue and post.

You are correct in that we have not strongly focused on the firewall aspect of this problem strongly - though we have lightly thouched upon it. To whit, somewhere in the beginning I had both the router and Windows 7 firewall shut off (and the port forwarding still failed under that particular arrangement) and was told that I ought to have my router firewall turned on so that it would respond to routing set ups.So let us indeed focus on number 2 - no pun intended! An example of my not fully understanding everything is the example you provided below as a port forward. I don't understand what the 'ANY' refers to and I am not entirely sure what a 'source port' is. I know what a port on the router means, but beyond that I am lost. As mentioned earlier, I only had a few minutes to skim the link. I did, as a very quick experiment turn off Windows 7 firewall and did test positive for TCP portforwarding on the desired port.

That was heartening (progress!), but confusind as well as the portforward was set for both TCP and UDP. Later tonight I will take the screen shot, as you requested, of the port forwarding rules from the router and post a link to the images that you might review them. There was also some weirdness, to me, going on with the Windows firewall settings (or probably better said - there was stuff going on that I didn't understand). Would you like me to post an image of that screen as well? Hubrisnxs wrote: If your router firewall rules settings look similiar to this then I would begin disabling the firewall and start doing my tests again. (192.168.1.5 TCP ANY - 443 (TCP or UDP ANY is important, you can not define the source port)) Also take a look at. Since you found a problem in the windows firewall, I have two suggestions.

Use this to make sure the port is active and added. And if it still doesn't work, then maybe you're windows firewall is simply corrupted. Use this tool to fix that. (I didn't create it, but I cut and paste the words from the guy's website who did) This small app will repair WMI & the Windows Firewall. I made this app to simplify the process for users to get WMI and the Firewall working again. Repair WMI & Windows Firewall.

Hello Hubrisnxs, Thank you for you response. I went to the link as you suggested. The instructions listed do not match what I see on my computer.

They look like they may be Vista related - I am running Windows 7 64bit. The controls the site indicated do not show up on my system in the same format.

Would you possibly have a link that would be for Windows 7 specifically? If you need or wish, I can upload a screen shot and demonstrate the differences. Let me know what you require from me. Regarding the Repair WMI & Windows Firewall tool kit - I've alredy run that sometime about a week or so ago. Thank you for suggesting the possibility, though.