Unable to access network share giving 0x80070035

Question

_{Sunday, June 23, 2019 11:23 AM}

Kindly note we have an issue with accessing shared folders which is in the domain ( windows 2016 DC ) using windows 10 Computers.

as part of troubleshooting, we removed computers from domain and we are able to join windows 7 back without any issue but not able to add windows 10 PC back to the domain.

at the same time, we have windows 7 computers accessing the same Shared folders without issues.

Regards
Mahesh
+250788558905
+250737305180

All replies (6)

_{Wednesday, July 10, 2019 8:18 PM ✅Answered}

We managed the solution on the issue it was Port 445 Getting blocked on the systems and fixed the same .

Mahesh P N Consultant

_{Sunday, June 23, 2019 12:03 PM}

Hello,

See if suggestions provided here helps you:

https://www.kapilarya.com/the-network-path-was-not-found-0x80070035-windows-10

Let us know if this helps!

Note: Included link in this reply refers to blog post by a trusted Microsoft MVP.

Microsoft MVP (Windows and Devices for IT)

Windows Insider MVP

Windows Help & Support [www.kapilarya.com]

_{Sunday, June 23, 2019 1:10 PM}

Hi Kapil,

Thank you very much for your feedback

I have tried the same but the result still stay the same

network path cannot be reached 0x80070035...Will it be related to something on the server

Regards

Mahesh

+250788558905
+250737305180

Mahesh P N Consultant

_{Monday, June 24, 2019 3:05 AM}

Hello Mahesh,

The current situation is that Windows 10 cannot access shares on Windows Server 2016, right?

If so, do the following actions.

Reproduce your problem first, then check the relevant logs on the client and server based on the corresponding timestamp.

On Windows 10, go to Event Viewer->Applications and Services Logs->Microsoft->Windows->SMBClient, then check logs here.

On Windows Server 2016, go to Event Viewer->Applications and Services Logs->Microsoft->Windows->SMBServer, then check logs here.

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, June 24, 2019 9:03 PM}

Hi Leon,

You are very Right , Windows 10 cannot access shares on Windows Server 2016

I gone through the Event logs on the client and it is clearly indicating the following error

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: XXX-SXXX-03.epic.local
Server address: 172.xx.xxx.xx9: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.

and from Server it is giving following Error

SMB Session Authentication Failure

Client Name: \172.xx.xx7.221
Client Address: 172.16.xx7.221:50161
User Name:
Session ID: 0xC400A400003D
Status: The attempted logon is invalid. This is either due to a bad username or authentication information. (0xC000006D)
SPN: session setup failed before the SPN could be queried
SPN Validation Policy: SPN optional / no validation

Guidance:

You should expect this error when attempting to connect to shares using incorrect credentials.

This error does not always indicate a problem with authorization, but mainly authentication. It is more common with non-Windows clients.

This error can occur when using incorrect usernames and passwords with NTLM, mismatched LmCompatibility settings between client and server, an incorrect service principal name, duplicate Kerberos service principal names, incorrect Kerberos ticket-granting service tickets, or Guest accounts without Guest access enabled

**Regards **

Maheshranny

_{Wednesday, June 26, 2019 9:05 AM}

Hi,

This Windows 10 machine does not join the domain, is it?

Do you check the corresponding log according to the timestamp?

The 0x80070035 error is usually caused by address resolution and port issues. But the log you gave also shows the problem with authentication.

It is recommended that you turn off the firewall and anti-virus software and delete the previously saved credentials (check if the previous credentials are cached in the Credential Manager).