Share via

Unable to connect to shared folder on win 2012 R2 server using win 10

Question

Saturday, April 13, 2019 2:39 PM

Hi,

I have few shares on win 2012R2 and my client machines on win 8.1 can connect just fine

but all the win 10 clients (domain and workgroup) cannot connect to any share.

same client machines can connect to shares from  win 2008R2 file server.

Error Code: 0x80070035 The network path was not found

file and print sharing resource is online but isn't responding to connection attempts

I tried several steps from online like make sure both are updated, enabling smb 1.0 on client, making sure required services are started, disable win firewall on both server but no go, no third party AV.

Please suggest.

All replies (13)

Monday, April 15, 2019 3:17 AM âś…Answered | 1 vote

Hello Beadmin,

Thank you for posting in this forum.

Can your Windows 10 machine successfully ping Win 2012 R2?

I read your other post and it seems that you can access the share via SMBv1. I want you to confirm that SMB2/3 is enabled on both the Windows 10 client and Win 2012 R2 server. Sometimes the SMB protocol is installed but not enabled.

If there is no problem after checking the above situation, please do this on your Windows 10 machine. First reproduce your question, then go to Event Viewer->Applications and Services Logs->Microsoft->Windows->SMBClient, then check the relevant error and warning messages.

Best Regards,

Leon

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

Monday, April 15, 2019 12:13 PM

Big thanks, I have this error which indicates network issues with DC, I was not even looking at this possibility.

However its still strange Win 10 machine and this DC are in same subnet (no firewall Windows or any other) but still I cannot telnet on port 445 to this DC. Netstat shows DC is listening on 445.

However I can telnet to other DCs from other sites. Yes I can ping just fine.

Failed to establish a network connection.

Error: {Device Timeout}
The specified I/O operation on %hs was not completed before the time-out period expired.

Server name: dcname
Server address: DCIP:445
Instance name: \Device\LanmanRedirector
Connection type: Wsk

Guidance:
This indicates a problem with the underlying network or transport, such as with TCP/IP, and not with SMB. A firewall that blocks TCP port 445, or TCP port 5445 when using an iWARP RDMA adapter, can also cause this issue.

Monday, April 15, 2019 9:22 PM

SMB1 is not enabled. Windows 10 has been known to disable SMB1 in the past.

Tuesday, April 16, 2019 8:10 AM

Yes, on this client but I also have issues with other clients where smb1 is enabled.

I dont understand when I can connect by forcing smb1 on client and server, how can this be a network issue.

I think this is some issue with smb1.1 on client machines that is not communicating with smb 0.2 on server.

Wednesday, April 17, 2019 1:46 PM

Hello Beadmin,

Have you checked other things listed in the guidance that might be causing this issue?

Best Regards,

Leon

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

Wednesday, April 24, 2019 6:30 AM

Hi,

Just checking the current situation of your problem.
Please let us know if you would like further help.

Best regards,
Leon

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

Friday, April 26, 2019 8:49 AM

Hi,

Was your issue resolved? 

If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

If no, please reply and tell us the current situation in order to provide further help.

Best Regards,

Leon

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

Tuesday, April 30, 2019 10:49 AM

Sorry of delay but this problem is not resolved yet.. for time being I am forced to disable SMB V2\3 stack

and only use SMB v1 however this is giving performance issues especially with large excel sheet on this server, so I am still looking for solution here. BTW, I did not mention this workload in on GCP. 

Wednesday, May 1, 2019 6:47 AM

Hello Beadmin,

Just want to confirm again: Have you checked the possibilities listed in the guidance?

Guidance:

This indicates a problem with the underlying network or transport, such as with TCP/IP, and not with SMB. A firewall that blocks TCP port 445, or TCP port 5445 when using an iWARP RDMA adapter, can also cause this issue.

Best Regards,

Leon

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

Wednesday, May 1, 2019 12:49 PM

Hi Leon,

I think this error is not accurate.. I cannot even connect from win 10 vm which is on same subnet without any firewall in between. Also,if I can connect using SMB1 then network is still the same and it must be using same ports??

BR,

Beadmin.

Thursday, May 2, 2019 3:16 AM

Hi Beadmin,

In order to successfully use the SMB protocol to access the share, both the port on the client and the port on the server need to be enabled.

The error message mentions that port 445 may be blocked. Although your DC shows that port 445 is listening, there may be some policies on your DC that prevent other machines from using port 445, so you can't successfully telnet port 445 on DC.

Please check if there is any policies in this location to limit the use of port 445.

Best Regards,

Leon

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

Friday, May 10, 2019 12:58 PM

Thanks Leon for your kind help.

My issue is finally resolved and it was firewall, yes we have firewall in between of same subnet .. why, I dont know.

also seems like, smb v3.3 does not work on same port like smb v1 but needs additional ones.

Monday, May 13, 2019 1:08 AM

Hello Beadmin,

Thank you for your update.

I am glad to hear that your issue was successfully resolved. If there is anything else we can do for you, please feel free to post in the forum.

Best Regards,

Leon

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