asked on Desktop File Sharing
I have a Workgroup of about 9 computers. One of the Windows 10 desktops serves as a share for 2 spreadsheets. Everyone can access the share except one PC gets "Network error: Cannot access \\OHDSales, Error code 0x80070035, The network path was not found." The "server" and the "client" are both Windows 10 Pro. The client could not see any PCs on the network via Windows Explorer until I enabled SMB\CIFS1.0 under control panel >> Programs Features >> Add/Remove Windows Features. Now it can see all the network PCs (AND WILL EVEN GET PROMPTED FOR CREDENTIALS WHEN CLICKING ON AAANNNYYY OF THEM! BUT PROMPTS ONLY THE ABOVE STATED ERROR IF TRYING TO ACCESS THE SHARE ON THE "SERVER.)
I can ping the "server" IP. But can't access the share via Windows Explorer using \\hostname or \\IPAddress.
I can ping the "server" IP. But can't access the share via Windows Explorer using \\hostname or \\IPAddress.
Windows 10Windows OSWindows NetworkingNetworkingDesktops
Last Comment
Owen Rubin
ASKER
BTW, No antivirus installed on the "server." Only Windows Defender (which the firewall is currently disabled).
ASKER
Hello?
Hi. Have you read this yet: https://www.drivereasy.com/knowledge/error-code-0x80070035-the-network-path-was-not-found-solved/
Hi mikesmithcc,
Do any of the other PCs in the Workgroup get prompted for credentials when clicking on other computers in the network? Or is this only afflicting your "client" computer?
If the other computers share a file with the affected "client", is it able to access them?
The "client" can now see the "server" on the network, but can't access the 2 spreadsheets?
Sorry if these are a lot of questions that might seem silly, but I just want to clarify your situation.
Martin Nguyen
Do any of the other PCs in the Workgroup get prompted for credentials when clicking on other computers in the network? Or is this only afflicting your "client" computer?
If the other computers share a file with the affected "client", is it able to access them?
The "client" can now see the "server" on the network, but can't access the 2 spreadsheets?
Sorry if these are a lot of questions that might seem silly, but I just want to clarify your situation.
Martin Nguyen
So while I suspect you have done all that, can you check the IP address of the machine that cannot connect and make sure it is on the same network. A manual entry in the IP panel could cause this machine to have a bad mask, bad network address, or just not be on the net.
Can that same machine see any of the other machines and/or the internet itself?
Can that same machine see any of the other machines and/or the internet itself?
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
"The client could not see any PCs on the network via Windows Explorer..." - and that is normal and expected, even desirable behavior. Don't use the network neighborhood looking for shares, but map drives.
"I can ping the "server" IP" - ping is no indicator at all. It just tells you, that the machine is alive, but nothing about file sharing.
"No antivirus installed on the "server."" - what about the client that has the problem? Any AV active there apart from windows defender?
"I can ping the "server" IP" - ping is no indicator at all. It just tells you, that the machine is alive, but nothing about file sharing.
"No antivirus installed on the "server."" - what about the client that has the problem? Any AV active there apart from windows defender?
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Owen, all these PCs have to keep a static IP because one of the software programs they run requires it. But the target has a valid mask and matches all others. This machine DID actually have the same problem as the one client I worked from (none of the other PCs could be seen under Windows Explorer >> Network until after I enable Windows Feature from Control Panel, SMB1.0/CIFS). I think the only time I've seen that SMB problem, was after Windows 10 first release, a lot of copier techs were screaming. However it can now "see all PCs in Windows Explorer, but even before that, all other PCs were and are accessing the share just fine, only the one client is having trouble.
Thanks for the update Mike. This is a strange one.
Can this machine connect to a share on any other machine?
Is there any chance of a duplicate IP on the network? Maybe change the IP (since it is static) to a new IP and see if anything changes.
Grasping at possibilities here now, sadly.
Can this machine connect to a share on any other machine?
Is there any chance of a duplicate IP on the network? Maybe change the IP (since it is static) to a new IP and see if anything changes.
Grasping at possibilities here now, sadly.
ASKER
Martin, all the PC can potentially access any other PC shares (i.e, they get a cred prompt. They are already all connected to this share and are experiencing now problems. A mixture of W7Pro and W10Pro. I haven't tested whether the "server" can access other shares on other PC but have verified that the server can NOT access a share from the problem client and vice versa. It seems to be a problem between these two PCs. Before neither showed any other network PCs in Windows Explorer under Network, but after enabling SMB1.0 in Windows Features they have all the other PCs on the network showing up. And get cred prompts if try to double click on any, except these two.
ASKER
McKnife, nothing apart from Windows Defender on the client either
ASKER
sarabande, can not access share by \\hostname\sharename or \\IPAddress\\sharename either. Get the same "Windows cannot access" error. Cannot map a drive
Have you tried this with the firewalls disabled? Do you have other firewall software on either machine?
I would turn them off one at a time and see if any change. This is unlikely the problem, but lets eliminate things to be sure.
I would turn them off one at a time and see if any change. This is unlikely the problem, but lets eliminate things to be sure.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Will double check for duplicate right now, although I'm not onsite to unplug the suspect. Will compare mac address with whats in firewall. I can't check for accessing other shares as there currently are no others and not onsite at the moment. Oddly enough their is a Toshiba Copier on the network with file shares and both machines can access that share just fine
ASKER
John, I have not but am about to read the article now. And see about setting up users. Sorry, was trying to answer the ones I could quickly
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
JOhn, "You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect yur PC from unsafe or malicious devices on the network" is what net use reports
Did you disable SMBv1 and did you check that all connections are Private - not public, and did you ensure Homegroup is OFF.
ASKER
I created a user and password on the "server" for the affected client. Now it work! Thanks! I knew that was an option but I've never been forced to do that before. Thanks again!
Thank you. That is how it works now so good to go.
The need to do that sounds like a connection profile with the local username and password of the affected machine was already saved on the affected machine. If that is saved, then every time you try and connect it would use the local name and password, which was failing before you added it to the server.
Start->Control Panels-User Accounts->Manage Your Credentials and look and see if a stored credential was saved on the client machine for the target server. That may have been causing the problem.
Glad you got it to work.
Start->Control Panels-User Accounts->Manage Your Credentials and look and see if a stored credential was saved on the client machine for the target server. That may have been causing the problem.
Glad you got it to work.