Error: A firewall is blocking file Sharing between Windows and the containers #355

medhatelmasry · 2016-12-25T05:40:07Z

Expected behavior

I am using Docker for windows 10 with a Linux container. I am unable to share a drive. I get a firewall error when I do so similar to case #345. This was working OK until I reset my credentials and it stopped working.

Actual behavior

When I try to share any drive I get error:
A firewall is blocking file Sharing between Windows and the containers. See documentation for more info.

Information

Diagnostic ID is
1ED2444F-86D2-400A-A2AC-165C6FA6599A/2016-12-24_21-28-25

Steps to reproduce the behavior

Right-click on the docker icon in the Windows 10 tray and select Settings
Click on Shared Drives tab
Enable C, D, and E drives then click on Apply button
Following error is displayed: A firewall is blocking file Sharing between Windows and the containers. See documentation for more info.

sugun999 · 2016-12-28T14:57:53Z

Do you have any 3rd party security software(example, f-secure) installed on your system? If so, you need to open firewall with security software

johnrb2 · 2016-12-28T20:11:53Z

I got this issue and it was coming from my cisco vpn. Once I disabled the VPN I could share just fine but now I don't have access to the databases I need....

medhatelmasry · 2016-12-29T00:24:51Z

The only firewall on my computer is the generic Windows Firewall for Windows 10. I see only one inbound rule in allowing port 445 from local address 10.0.75.1 to remote address 10.0.75.2. I still get the same error when I disable windows firewall. I am not sure what else to do.

…

On Wed, Dec 28, 2016 at 12:11 PM, John Bench ***@***.***> wrote: I got this issue and it was coming from my cisco vpn. Once I disabled the VPN I could share just fine but now I don't have access to the databases I need.... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#355 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABvKQkNtffSDHwL-GQYrn8Ttw8CAAyQLks5rMsKKgaJpZM4LVWKk> .

friism · 2017-01-04T20:51:17Z

@simonferquel do you have time to look at @medhatelmasry dump?

simonferquel · 2017-01-05T13:00:15Z

@medhatelmasry I see that you are using an insider preview of Windows. Unfortunately in latest build there seem to have a bug with Samba sharing preventing drive sharing with the linux VM to work.

We don't have any workaround for now (except reverting to Windows 14393)

medhatelmasry · 2017-01-05T15:14:08Z

Simon, Thanks for finding out the root of the problem. I will need to wait until this is fixed with subsequent windows insider releases. Medhat

…

On Jan 5, 2017 5:00 AM, "Simon Ferquel" ***@***.***> wrote: @medhatelmasry <https://github.com/medhatelmasry> I see that you are using an insider preview of Windows. Unfortunately in latest build there seem to have a bug with Samba sharing preventing drive sharing with the linux VM to work. We don't have any workaround for now (except reverting to Windows 14393) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#355 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABvKQrWhBXuJHpR_XVfmBNjADaa-uqM0ks5rPOlggaJpZM4LVWKk> .

denisvmedia · 2017-01-11T06:36:50Z

@simonferquel, I don't think there is a bug in Windows. It used to work for me (and still works on another PC with the most recent insider release), but then I had to reset the settings of Docker, after that it stopped working.

simonferquel · 2017-01-11T09:18:40Z

@denisvmedia there was a bug before 15002 with remote access in general (not only Samba File sharing, but also with RDP). I don't know if it did hit everyone though and I suppose Microsoft fixed that in 15002.

denisvmedia · 2017-01-11T09:53:09Z

@simonferquel unfortunately, I don't know, but what really surprises me that this stopped working only after I did the reset in Docker. So even if there is a bug in Windows, there must be a workaround - otherwise how could it work before? (and still works on another PC) I'd be happy to find it... If I can help anyhow, I'm open for that, because currently my work is completely stopped due to this issue :(

Update: As of RDP - it works for me right now - I'm writing this from an external network on my Desktop through RDP.

denisvmedia · 2017-01-11T14:56:54Z

I solved it! Now it works again. I found a comment of @gorbunovav in #114, it worked for me:

Try to share the drive manually in Windows and check, that you can access

\10.0.75.1[Drive Letter]

If it doesn't work - check, that file sharing is enabled for the docker interface location (Public network by default) and try to remove, then add back 'File and Printer Sharing for MS Networks' in 'vEthernet (DockerNAT)' network adapter's properties.

(I've also moved interface to the 'Private network' segment:

Set-NetConnectionProfile -InterfaceAlias "vEthernet (DockerNAT)" -NetworkCategory Private

in the PowerShell)

cmurczek · 2017-01-20T13:50:05Z

I see this issue in Win10 Insider build 15007. Just submitted feedback to MS about this since it had been fixed in a prev. (way older, might have been 14393) Insider build. Currently updating to 15014.

cmurczek · 2017-01-20T14:55:03Z

Volume mapping is working again in Win10 Insider build 15014.

phillipsharring · 2017-01-26T14:09:27Z

@johnrb2 - did you ever figure this out with Cisco VPN? My team are all using a docker container for development and it's made WFH really annoying. Thoughts? Thanks, Phillip

phillipsharring · 2017-01-26T14:13:37Z

Markdown seems to have eaten the solution @denisvmedia posted. In a file explorer, go to: \\10.0.75.1\C

johnrb2 · 2017-01-26T14:38:19Z

@philsown yeah I just had to change the address in network settings to 192.168.x.x since the VPN was already using the 10.0 ones.

johnrb2 · 2017-01-26T14:45:44Z

@philsown there is another thread regarding the Cisco VPN that my solution didn't work for @sugun999 he or she could use some help.

johnrb2 · 2017-01-26T14:49:18Z

On issue #360

absalan · 2017-02-18T07:59:07Z

I had same issue and I just solved it.
My internet security software was blocking file and printer sharing. If you do too, Just right click on the drive that you want to share with docker in file explorer and click on Sharing tap. Than click on advanced sharing. On that popup check the "Share this folder" checkbox and click ok. If your security software warned you just click on it and enable file sharing on it and click ok. Now if you go to docker settings and share the drive, it will work.

sthuber90 · 2017-02-18T11:05:16Z

@absalan When I share my C: drive manually thorugh the advanced sharing settings and then try to activate in the docker settings, I get the notification that firewall is blocking, which it is not (#466) and after that the C: drive is not shared anymore.

rn · 2017-02-18T11:32:31Z

@sthuber90 that's interesting. If you don't enable sharing in the Advanced Settings does it work? Also, how do you enable it? There are several options in the menu. Could you maybe share a screenshot?
thanks

absalan · 2017-02-19T20:39:03Z

@sthuber90 Try to share another drive. windows does have some policy for windows drive and that's why it's preventing you from sharing drive C.

sthuber90 · 2017-02-20T07:44:16Z

@absalan The computer is work on is a corporate one and only has a C drive, otherwise I would have tested sharing an other drive.

@rneugeba

[08:31:05.005][SharedDrivesSettings][Info   ] Apply shared drive settings
[08:31:05.007][NamedPipeClient][Info   ] Sending Mount(C, DOMAIN\USER:**********, Docker.Core.Settings)...
[08:31:06.008][NamedPipeServer][Info   ] Mount(C, DOMAIN\USER:**********, Docker.Core.Settings)
[08:31:06.008][SambaShare     ][Info   ] Mount C
[08:31:06.048][Cmd            ][Info   ] Share name        C
[08:31:06.048][Cmd            ][Info   ] Path              C:\
[08:31:06.048][Cmd            ][Info   ] Remark            
[08:31:06.048][Cmd            ][Info   ] Maximum users     No limit
[08:31:06.050][Cmd            ][Info   ] Users             
[08:31:06.050][Cmd            ][Info   ] Caching           Manual caching of documents
[08:31:06.050][Cmd            ][Info   ] Permission        Everyone, FULL
[08:31:06.050][Cmd            ][Info   ] 
[08:31:06.050][Cmd            ][Info   ] The command completed successfully.
[08:31:06.050][Cmd            ][Info   ] 
[08:31:06.054][SambaShare     ][Info   ] "C" is shared
[08:31:06.108][SambaShare     ][Info   ] Username: USER
[08:31:06.108][SambaShare     ][Info   ] Host IP: 10.0.75.1
[08:31:07.830][ApiProxy       ][Info   ] proxy << POST /v1.26/containers/be1e37c16a936806e798b7d3ecd17d2a39c3a4f596a98341e17cc05748c5da42/attach?stderr=1&stdin=1&stdout=1&stream=1
[08:31:08.187][ApiProxy       ][Info   ] Cancel connection...
[08:31:08.191][SambaShare     ][Error  ] Unable to mount C drive: firewall is blocking
[08:31:08.191][SambaShare     ][Info   ] Removing share C

Even though it says that the firwall is blocking this cannot be the case, as mentioned here.

cmurczek · 2017-02-20T10:02:28Z

This has got nothing to do with suspected policies for the C drive. I just tried to share D and got the same results:
[10:54:49.631][NamedPipeClient][Info ] Sending GetDefaultVhdxPath()... [10:54:50.636][NamedPipeServer][Info ] GetDefaultVhdxPath() [10:54:51.643][NamedPipeClient][Info ] Received response for GetDefaultVhdxPath [10:54:51.642][NamedPipeServer][Info ] GetDefaultVhdxPath done in 00:00:01.0057637. [10:54:53.485][SharedDrivesSettings][Info ] Apply shared drive settings [10:54:53.486][NamedPipeClient][Info ] Sending Unmount(C, Docker.Core.Settings)... [10:54:53.487][NamedPipeServer][Info ] Unmount(C, Docker.Core.Settings) [10:54:53.487][SambaShare ][Info ] Unmount C [10:54:53.652][ApiProxy ][Info ] proxy >> GET /_ping [10:54:53.652][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:53.656][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:53.660][ApiProxy ][Info ] proxy << GET /_ping [10:54:53.663][ApiProxy ][Info ] proxy >> POST /v1.26/images/load?quiet=1 [10:54:53.663][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:53.666][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:53.924][ApiProxy ][Info ] proxy << POST /v1.26/images/load?quiet=1 [10:54:54.104][ApiProxy ][Info ] proxy >> GET /_ping [10:54:54.104][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:54.111][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:54.126][ApiProxy ][Info ] proxy << GET /_ping [10:54:54.145][ApiProxy ][Info ] proxy >> POST /v1.26/containers/create [rewriteBinds] [10:54:54.172][ApiProxy ][Info ] Failed to Walk to [snapshots f483c5cc239a2903863cbc3ee314daa95d60a1ee ro com.docker.driver.amd64-linux proxy http] 9p: No such file or directory [10:54:54.176][ApiProxy ][Info ] Failed to read proxies/http from snaphshot p9p.MessageRerror{Ename:"No such file or directory"} [10:54:54.176][ApiProxy ][Info ] proxy >> POST /v1.26/containers/create [10:54:54.176][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:54.180][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:54.353][ApiProxy ][Info ] proxy << POST /v1.26/containers/create [10:54:54.368][ApiProxy ][Info ] proxy >> POST /v1.26/containers/d18518d66c7d9c0bc61af40b892fe13b1768d34201d8310da310becd806d213b/attach?stderr=1&stdout=1&stream=1 [10:54:54.368][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:54.370][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:54.372][ApiProxy ][Info ] Upgrading to raw stream [10:54:54.375][ApiProxy ][Info ] proxy >> GET /v1.26/events?filters=%7B%22container%22%3A%7B%22d18518d66c7d9c0bc61af40b892fe13b1768d34201d8310da310becd806d213b%22%3Atrue%7D%2C%22type%22%3A%7B%22container%22%3Atrue%7D%7D [10:54:54.375][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:54.376][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:54.380][ApiProxy ][Info ] proxy >> POST /v1.26/containers/d18518d66c7d9c0bc61af40b892fe13b1768d34201d8310da310becd806d213b/start [start] [10:54:54.380][ApiProxy ][Info ] proxy >> POST /v1.26/containers/d18518d66c7d9c0bc61af40b892fe13b1768d34201d8310da310becd806d213b/start [10:54:54.380][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:54.381][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:54.772][ApiProxy ][Info ] proxy << POST /v1.26/containers/d18518d66c7d9c0bc61af40b892fe13b1768d34201d8310da310becd806d213b/start [10:54:55.323][NamedPipeClient][Info ] Received response for Unmount [10:54:55.308][NamedPipeServer][Info ] Unmount done in 00:00:01.8214994. [10:54:55.338][NamedPipeClient][Info ] Sending Mount(D, ***@***:**********, Docker.Core.Settings)... [10:54:55.322][ApiProxy ][Info ] proxy << POST /v1.26/containers/d18518d66c7d9c0bc61af40b892fe13b1768d34201d8310da310becd806d213b/attach?stderr=1&stdout=1&stream=1 [10:54:55.322][ApiProxy ][Info ] Cancel connection... [10:54:55.323][ApiProxy ][Info ] proxy << GET /v1.26/events?filters=%7B%22container%22%3A%7B%22d18518d66c7d9c0bc61af40b892fe13b1768d34201d8310da310becd806d213b%22%3Atrue%7D%2C%22type%22%3A%7B%22container%22%3Atrue%7D%7D [10:54:55.996][NamedPipeServer][Info ] Mount(D, ***@***:**********, Docker.Core.Settings) [10:54:55.996][SambaShare ][Info ] Mount D [10:54:56.056][Cmd ][Info ] This shared resource does not exist. [10:54:56.056][Cmd ][Info ] [10:54:56.056][Cmd ][Info ] More help is available by typing NET HELPMSG 2310. [10:54:56.056][Cmd ][Info ] [10:54:56.056][SambaShare ][Info ] "D" is not shared [10:54:56.057][SambaShare ][Info ] Creating share "D:\" as "D" with Full Control to "[email protected]" [10:54:56.190][Cmd ][Info ] D was shared successfully. [10:54:56.190][Cmd ][Info ] [10:54:56.267][Cmd ][Info ] Share name D [10:54:56.267][Cmd ][Info ] Path D:\ [10:54:56.267][Cmd ][Info ] Remark [10:54:56.267][Cmd ][Info ] Maximum users No limit [10:54:56.268][Cmd ][Info ] Users [10:54:56.269][Cmd ][Info ] Caching Caching disabled [10:54:56.270][Cmd ][Info ] Permission ***\***, FULL [10:54:56.270][Cmd ][Info ] [10:54:56.270][Cmd ][Info ] The command completed successfully. [10:54:56.270][Cmd ][Info ] [10:54:56.285][SambaShare ][Info ] "D" is shared [10:54:56.398][SambaShare ][Info ] Username: *** [10:54:56.401][SambaShare ][Info ] Host IP: 10.0.75.1 [10:54:56.401][SambaShare ][Info ] Cifs options: noperm,iocharset=utf8,nobrl,mfsymlinks,vers=3.02,domain=SURFACE-CMU [10:54:56.525][ApiProxy ][Info ] proxy >> GET /_ping [10:54:56.526][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:56.527][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:56.532][ApiProxy ][Info ] proxy << GET /_ping [10:54:56.535][ApiProxy ][Info ] proxy >> POST /v1.26/images/load?quiet=1 [10:54:56.535][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:56.536][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:56.703][ApiProxy ][Info ] proxy << POST /v1.26/images/load?quiet=1 [10:54:56.847][ApiProxy ][Info ] proxy >> GET /_ping [10:54:56.847][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:56.848][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:56.851][ApiProxy ][Info ] proxy << GET /_ping [10:54:56.859][ApiProxy ][Info ] proxy >> POST /v1.26/containers/create [rewriteBinds] [10:54:56.876][ApiProxy ][Info ] Failed to Walk to [snapshots f483c5cc239a2903863cbc3ee314daa95d60a1ee ro com.docker.driver.amd64-linux proxy http] 9p: No such file or directory [10:54:56.879][ApiProxy ][Info ] Failed to read proxies/http from snaphshot p9p.MessageRerror{Ename:"No such file or directory"} [10:54:56.879][ApiProxy ][Info ] proxy >> POST /v1.26/containers/create [10:54:56.879][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:56.882][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:57.063][ApiProxy ][Info ] proxy << POST /v1.26/containers/create [10:54:57.080][ApiProxy ][Info ] proxy >> POST /v1.26/containers/a58989958bb9d51572e93a2617c7eb56c45faf14ae9e38495af5d37f265f6803/attach?stderr=1&stdin=1&stdout=1&stream=1 [10:54:57.080][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:57.081][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:57.083][ApiProxy ][Info ] Upgrading to raw stream [10:54:57.085][ApiProxy ][Info ] proxy >> GET /v1.26/events?filters=%7B%22container%22%3A%7B%22a58989958bb9d51572e93a2617c7eb56c45faf14ae9e38495af5d37f265f6803%22%3Atrue%7D%2C%22type%22%3A%7B%22container%22%3Atrue%7D%7D [10:54:57.085][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:57.086][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:57.088][ApiProxy ][Info ] proxy >> POST /v1.26/containers/a58989958bb9d51572e93a2617c7eb56c45faf14ae9e38495af5d37f265f6803/start [start] [10:54:57.088][ApiProxy ][Info ] proxy >> POST /v1.26/containers/a58989958bb9d51572e93a2617c7eb56c45faf14ae9e38495af5d37f265f6803/start [10:54:57.088][ApiProxy ][Info ] Dial Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:57.089][ApiProxy ][Info ] Successfully dialed Hyper-V socket 00c5797d-99af-4ba5-abbf-702f0b4c71e7:23a432c2-537a-4291-bcb5-d62504644739 [10:54:57.598][ApiProxy ][Info ] proxy << POST /v1.26/containers/a58989958bb9d51572e93a2617c7eb56c45faf14ae9e38495af5d37f265f6803/start [10:54:58.692][ApiProxy ][Info ] proxy << POST /v1.26/containers/a58989958bb9d51572e93a2617c7eb56c45faf14ae9e38495af5d37f265f6803/attach?stderr=1&stdin=1&stdout=1&stream=1 [10:54:59.116][ApiProxy ][Info ] Cancel connection... [10:54:59.125][ApiProxy ][Info ] proxy << GET /v1.26/events?filters=%7B%22container%22%3A%7B%22a58989958bb9d51572e93a2617c7eb56c45faf14ae9e38495af5d37f265f6803%22%3Atrue%7D%2C%22type%22%3A%7B%22container%22%3Atrue%7D%7D [10:54:59.118][SambaShare ][Error ] Unable to mount D drive: firewall is blocking [10:54:59.125][SambaShare ][Info ] Removing share D [10:54:59.185][NamedPipeClient][Info ] Received response for Mount [10:54:59.183][NamedPipeServer][Info ] Mount done in 00:00:03.1876468. [10:55:00.946][NamedPipeClient][Info ] Sending GetDefaultVhdxPath()... [10:55:00.973][NamedPipeClient][Info ] Received response for GetDefaultVhdxPath [10:55:00.956][NamedPipeServer][Info ] GetDefaultVhdxPath() [10:55:00.959][NamedPipeServer][Info ] GetDefaultVhdxPath done in 00:00:00.0030104.

mickext · 2017-09-06T20:06:14Z

This problem can be happen If you are using Windows 10 Enterprise.

The Group Policy in System Center / Active Directory can blocking the port 445. The System Administrator needs permit this port to your user/ip.

Releasing the door in Windows Firewall Local does not make effect.

Kounavi · 2017-09-20T11:08:01Z

@simonferquel What can I say? :) Back then I was using Divio's app but days have come and gone by and I'm using docker compose now when I have to resort to docker which I find much better and much more flexible for my workflow and usage cases (at least for me). Also, without that workaround I couldn't use docker in any way so it was a necessary evil (but can't recall the details since it's been a long time).

apodznoev · 2017-09-27T16:50:09Z

I've read all this and a couple of other topics and tried everything written there. The only thing that finally worked for me was switch to Docker Edge version:

Client:
Version: 17.09.0-ce-rc3
API version: 1.32
Go version: go1.8.3
Git commit: 2357fb2
Built: Thu Sep 21 02:31:16 2017
OS/Arch: windows/amd64

Server:
Version: 17.09.0-ce-rc3
API version: 1.32 (minimum version 1.12)
Go version: go1.8.3
Git commit: 2357fb2
Built: Thu Sep 21 02:36:52 2017
OS/Arch: linux/amd64
Experimental: true

command0r · 2017-10-09T19:46:09Z

Sounds weird, but the solution offered by @juhap worked for me. Seems more like a Windows 10 glitch that has nothing to do with Docker.

rn · 2018-03-08T17:38:41Z

cleaning/closing old issues.

avindra · 2018-04-11T04:22:58Z

People having this issue with Cisco's VPN software... did you come up with any workarounds?

Seems that the only way for corporate users to work from home is to give up the VPN :/

JoshSchreuder · 2018-04-11T10:41:42Z

I had two firewall rules in Windows Firewall

No idea where these came from, but disabling them allowed me to share the drive. Hope this helps someone.

joegrasse · 2018-04-11T14:10:54Z

@avindra To get docker to work with a Cisco VPN, I had to go into Docker -> Settings -> Network and change the Internal Virtual Switch settings.

For Example:
Subnet Address: 192.168.65.0
Subnet Mask: 255.255.255.0

ralberts · 2018-04-27T19:22:09Z

The Cisco VPN policy settings blocked any local traffic - it basically sends it all through the VPN - though I switched over to OpenConnect and it allows local traffic which allowed docker to work for me. Hope this helps someone.

radekbaranowski · 2018-06-06T12:05:39Z

Does it have anything to do with severe restriction (and complete default removal) on using SMB v.1.0 which is regarded ATM as highly vulnerable, thus deprecated and disabled by default in newest Win10 updates? Struggled with this when lost connection to my local NAS, maybe that's just another chapter of the same story?

efunkenbusch · 2018-08-29T14:29:08Z

In my case, the problem appears to be that our domain policy forces the firewall to be enabled on the Private and Public profiles (disables it for the DomainAuthenticated profile). Even though I have the proper ports enabled on those profiles, it still is blocked. Turning off the Firewall service allows the drives to be mapped, so it's definitely a firewall/security policy issue.

I can reach port 445 on the Docker interface (I've remapped to 192.168.0.1 because our network uses the 10.* network).

I'm running Windows 10 1803, which of course has the issue where you cannot uninstall file and printer sharing. So that workaround is not possible.

mariusjp · 2019-01-07T13:20:01Z

I had two firewall rules in Windows Firewall

No idea where these came from, but disabling them allowed me to share the drive. Hope this helps someone.

You are a lifesaver! I tried EVERYTHING mentioned EVERYWHERE on the internet. And these stupid 2 rules blocked me. Thx for the find!

duc-anh-tran · 2019-02-23T00:38:22Z

For anyone with Cisco VPN issue, follow this guide: #360 (comment)
Finally worked out for me.

germanamv · 2019-03-10T09:00:47Z

Norton smart firewall was the problem for me. Worked fine after disabling it.

DashAce10 · 2019-07-03T03:36:56Z

Disabling this setting worked for me.

LU4E · 2019-07-24T16:48:43Z

check if there is a forbid rules for 445.
mine is forbid rules for bitcoin which forbid 445.

GZFrankPeng · 2019-08-03T12:52:35Z

Disabling this setting worked for me.

I found this, and re-review my the Windows Firewall Settings, and do find a rule which is blocked the 445 port, I enable it, and now it works. Thanks @DashAce10 ! I've spent a lot of time on the issue before it is settled. Beautiful! So I do suggest you to check your Firewall Rules carefully around the port 445. Wish you good luck!

mara8008 · 2019-09-25T13:47:28Z

In my case, Nothing worked with the given suggestions.
I did following steps to solve this problem as i am on VPN(I am using Check point EndPoint Security).
1)Uninstalled the docker completely from system. Clean uninstall.
2)Install the docker with Admin Privileges while i am on VPN.
3)Once the docker up and running, Share the drive and it will work as usual.

Please make sure you do clean Uninstall as mentioned in first step even from system registries.

gabeluci · 2019-10-13T01:23:53Z

@mara8008 A reboot should be enough when Check Point is misbehaving. I've had problems in the past with it enforcing firewall rules even when I'm not connected anymore, even after shutting down the Check Point service (because it uses a driver-based firewall). So the only way to reset those rules is to reboot.

appsparkler · 2019-10-26T05:55:17Z

This is what worked for me on `Windows 10`:

Type Turn Windows Feature On Or Off and check the checkbox for File Sharing. Restart the system.

Good Luck...

tolgabalci · 2019-11-21T00:14:46Z

Thank you @efunkenbusch! I tried over a dozen different things and none of them worked, but changing Docker => Settings => Network => Subnet Address to 192.168.0.0 worked! (My company also uses 10...* for internal addresses)

docker-robott · 2020-06-19T03:14:25Z

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

rn added area/mounts status/triage labels Dec 28, 2016

friism assigned friism and simonferquel and unassigned friism Jan 4, 2017

eliezeralmeida mentioned this issue Feb 12, 2017

Sharing Windows 10; Firewall problem (firewall disabled). #491

Closed

rn added the area/firewall label Feb 15, 2017

colthreepv mentioned this issue Dec 11, 2017

Cannot share drive #1395

Closed

rn closed this as completed Mar 8, 2018

ghost mentioned this issue Apr 29, 2018

Docksal is not working on Windows if connected to VPN docksal/docksal#509

Closed

janne-j mentioned this issue Oct 3, 2018

Error: A firewall is blocking file sharing between Windows and the containers #2677

Closed

2 tasks

gimlichael mentioned this issue May 14, 2019

Unable to Share C (Windows 10 Enterprise) #3908

Closed

manrajesh mentioned this issue Oct 28, 2019

A firewall is blocking file Sharing between Windows and the containers #5015

Closed

2 tasks

docker locked and limited conversation to collaborators Jun 19, 2020

docker-robott added the lifecycle/locked label Jun 19, 2020

Error: A firewall is blocking file Sharing between Windows and the containers #355

Error: A firewall is blocking file Sharing between Windows and the containers #355

Comments

medhatelmasry commented Dec 25, 2016

Expected behavior

Actual behavior

Information

Steps to reproduce the behavior

sugun999 commented Dec 28, 2016

johnrb2 commented Dec 28, 2016

medhatelmasry commented Dec 29, 2016 via email

friism commented Jan 4, 2017

simonferquel commented Jan 5, 2017

medhatelmasry commented Jan 5, 2017 via email

denisvmedia commented Jan 11, 2017 • edited Loading

simonferquel commented Jan 11, 2017

denisvmedia commented Jan 11, 2017 • edited Loading

denisvmedia commented Jan 11, 2017

cmurczek commented Jan 20, 2017

cmurczek commented Jan 20, 2017

phillipsharring commented Jan 26, 2017

phillipsharring commented Jan 26, 2017 • edited Loading

johnrb2 commented Jan 26, 2017

johnrb2 commented Jan 26, 2017

johnrb2 commented Jan 26, 2017

absalan commented Feb 18, 2017

sthuber90 commented Feb 18, 2017

rn commented Feb 18, 2017

absalan commented Feb 19, 2017

sthuber90 commented Feb 20, 2017

cmurczek commented Feb 20, 2017

mickext commented Sep 6, 2017

Kounavi commented Sep 20, 2017

apodznoev commented Sep 27, 2017 • edited Loading

command0r commented Oct 9, 2017 • edited Loading

rn commented Mar 8, 2018

avindra commented Apr 11, 2018

JoshSchreuder commented Apr 11, 2018

joegrasse commented Apr 11, 2018

ralberts commented Apr 27, 2018

radekbaranowski commented Jun 6, 2018

efunkenbusch commented Aug 29, 2018

mariusjp commented Jan 7, 2019

duc-anh-tran commented Feb 23, 2019

germanamv commented Mar 10, 2019

DashAce10 commented Jul 3, 2019

LU4E commented Jul 24, 2019

GZFrankPeng commented Aug 3, 2019

mara8008 commented Sep 25, 2019

gabeluci commented Oct 13, 2019

appsparkler commented Oct 26, 2019 • edited Loading

This is what worked for me on Windows 10:

tolgabalci commented Nov 21, 2019

docker-robott commented Jun 19, 2020

denisvmedia commented Jan 11, 2017 •

edited

Loading

denisvmedia commented Jan 11, 2017 •

edited

Loading

phillipsharring commented Jan 26, 2017 •

edited

Loading

apodznoev commented Sep 27, 2017 •

edited

Loading

command0r commented Oct 9, 2017 •

edited

Loading

appsparkler commented Oct 26, 2019 •

edited

Loading

This is what worked for me on `Windows 10`: