Share via

Windows 10 cannot access shared folder, do not use port 139 to connect resource

Question

Wednesday, January 10, 2018 2:11 AM | 1 vote

I have a shared folder access problem recently. I have a fresh installed Windows 10. But I cannot access the shared folder on the server, it says cannot find the resource location. I try to install both win10 and Win7 into VM and confirmed the problem is only on Win10.

I try to use wireshark to monitor the network traffic, and found that port 445 on the server is blocked for some reason (but I cannot change the setting on the server). When Win7 try to access the shard folder, it use only port 139 . But on Win10, it keeps trying to connect the port 445 and failed. 

I have tried to choose the "enable NetBIOS over TCP/IP" in the advanced setting page of TCP/IP, but nothing changed.

I want to know, is there a way to force Win10 to use port 139 (NetBIOS over TCP/IP) only or disable the directly SMB connection (port 445) to access shared folder?

I can access other shared folder on the servers not blocked port 445 on Win10, so I think the setting on win10 is correct. (enabled the network discovery & disabled all firewall)

All replies (10)

Thursday, February 22, 2018 9:37 AM ✅Answered

Finally, the solution is disabling SMB v2/v3 AND fix the broken registry.

1. Disable MRxSmb20 service and remove the dependence in LanmanWorkstation service:

https://superuser.com/questions/1191412/smb-without-port-445?answertab=active#tab-top

2. Fix the broken registry in Windows 10

https://social.technet.microsoft.com/Forums/windows/en-US/41b4d697-2371-4496-9d95-d7f026485049/netbios-over-tcpip-issue-from-recent-update-windows-10

But the LanmanWorkstation service is the only one need to modify. On my fresh installed Windows 10, I need to add the following string to the registry key:

[Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Bind]
\Device\Smb_Tcpip_{392892A2-9848-4758-95DE-A670CCB14C8E}
\Device\Smb_Tcpip6_{392892A2-9848-4758-95DE-A670CCB14C8E}
[Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Export]
\Device\LanmanWorkstation_Smb_Tcpip_{392892A2-9848-4758-95DE-A670CCB14C8E}
\Device\LanmanWorkstation_Smb_Tcpip6_{392892A2-9848-4758-95DE-A670CCB14C8E}

[Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Route]
"Smb" "Tcpip" "{392892A2-9848-4758-95DE-A670CCB14C8E}"
"Smb" "Tcpip6" "{392892A2-9848-4758-95DE-A670CCB14C8E}"

you need to change the GUID to your network adapter, find the GUID using command

wmic nicconfig get caption,index,TcpipNetbiosOptions,SettingID

3. Reboot and done.

Thursday, January 11, 2018 8:36 AM

Hi,

Generally, Windows try to connect simultaneously over NetBIOS (port 139) and SMB (port 445). If no response from the target on 445, it reverts back to 139. This offers legacy support for NetBIOS based feature. That is why if you disable NetBIOS on a server, it will still connect to other servers, but any NetBIOS based feature that require connectivity to that server will fail.

Here I suggest you run netstat /na command in both Windows 7, Windows 10 and Shared file Server to confirm if all 445 and 139 port is opened.

And then you have two choices.

Option one: Enable the SMB port 445 on both of Windows 10 and shared File Server.

Option two: Enable the NetBIOS on both of Windows 10 and shared File Server.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Thursday, January 11, 2018 12:49 PM | 1 vote

Generally, Wndows try to connect simultaneously over NetBIOS (port 139) and SMB (port 445). If no response from the target on 445, it reverts back to 139. 

Thanks for the reply.

Yes, windows should use port 139 if port 445 is no response. That's what Win7 do, and that's what I want. But Win10 do not, Win10 stick on the port 445, no matter what I am setting.

I have checked the server, and found out the port 445 is not blocked on the server, but is blocked by the switch or router or gateway or something I don't know. Anyway, I can access the server shared folder using Win7 & WinXP,  but not Win10. And the reason is the port 445 is globally blocked by the IT guys, maybe to prevent malware spreading.  

  1. I am sure all the ports are opened on both the server and client, all firewall is disabled, And I can connect to the port 445 if two computer close enough(e.g. they are both plug into the same switch or router). But globally, the port 445 is blocked by something else on the network.
  2. the shared folder is accessible using WinXP and Win7 client without any special setting. (they use port 139)
  3. if I use Win10, I can access other shared folder if the port 445 is accessible.

I just wonder what's the difference in Win10.  Is there a special setting to let Win10 fall back to 139? or Is it a bug in Win10?

Thanks.

Tuesday, January 16, 2018 9:13 AM

Hi,

That's really odd. I need more time to do research, please give us more patience.

Thanks for your understanding.

Update：

According to my understanding and researches, maybe you can use 139 instead of 445 by disabling SMBv2/v3 as this reference:

https://superuser.com/questions/1191412/smb-without-port-445?answertab=active#tab-top

Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Friday, January 19, 2018 1:54 AM

Thanks Karen,

I have already tried this method before I post my question, it doesn't work.

And I searched a lot and after doing the following one, it fixes my problem:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/f3a909c8-04e8-485d-894c-3f92683c0fd7/can-not-enable-netbios-over-tcpip-on-shared-network-interface

This involving a lot register edit, and before doing that I have already tried a lot other methods, so I don't know if this is the right answer to my question, and which part of the register edit is necessary if not all.

All of my computers (two physical computers and one virtual machine) has this problem with newly installed (and fully updated) Win10 have this problem, so I think the local network I connect is really strange if it is not a Win10 bug.

I need some time to reinstall a new Win10 VM to test this method, I will update the post later if I find the correct way to fix my problem.

Friday, January 19, 2018 1:59 AM

Hi gwjwin,

Ok and let's look forward to your final solution.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Wednesday, January 24, 2018 10:23 AM

I have the same issue with Windows 10 1709.

Can't connect to old CNC Machine with Windows 2000 or older.

Because there are using the Port 139 for SMB/NetBIOS!

Tuesday, February 27, 2018 8:48 AM

Thanks for sharing your solution and experience here. It will be very beneficial to other community members who have similar problems.

If it's convenient, please mark the helpful reply as answer in order that other community members could find the helpful reply quickly.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Tuesday, April 9, 2019 1:05 PM

Hi,

That's really odd. I need more time to do research, please give us more patience.

Thanks for your understanding.

Update：

According to my understanding and researches, maybe you can use 139 instead of 445 by disabling SMBv2/v3 as this reference:

https://superuser.com/questions/1191412/smb-without-port-445?answertab=active#tab-top

Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Hello, i've no problem with port 139 and 445 on the single nodes.

I need that the cluster respond on both ports, instead now the cluster responds on the 445 only but nodes responds on both, i won't redo the cluster

Tuesday, April 9, 2019 3:23 PM

Hi,

That's really odd. I need more time to do research, please give us more patience.

Thanks for your understanding.

Update：

According to my understanding and researches, maybe you can use 139 instead of 445 by disabling SMBv2/v3 as this reference:

https://superuser.com/questions/1191412/smb-without-port-445?answertab=active#tab-top

Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Hello, i've no problem with port 139 and 445 on the single nodes.

I need that the cluster respond on both ports, instead now the cluster responds on the 445 only but nodes responds on both, i won't redo the cluster

I need to use both port on cluster name not he 139 instead of the 445.

I cannot understand why by pounting the single active node it works, if i point cluster name doesn't.