Windows 10 1803 Server and Clients, problems with SMB. Network Path not found.

Hello! I am an IT guy and have found issues with Windows 10 1803. If you are doing filesharing and 1803 is on the Server and Client, then on occasion I run into problems accessing the server by the \\ComputerName and the error is Network Path not found. 

This isn't a problem with Network Discovery, as others have complained about with 1803, which I wish Microsoft would also fix that as well. Where the computer shows up in the list on the Network and you have to enable services manually to get it to show up. What I am talking about is just accessing the computer by the UNC path.

If the server is 1709, and the clients are 1803, I don't seem to have issues. But if the server is 1803, then intermittently there is a problem with Network Path not found error coming from workstations. Rebooting the workstation may or may not fix it. 

Not sure what the issue is, but I hope Microsoft gets down to the bottom of these issues and makes this as reliable as a Windows 7 Network. I don't care about the removal of Home Groups because I never use Home Groups... but having reliable filesharing is important.

Are you guys at Microsoft planning on fixing this stuff?

I also disabled SMB2\3 and put on SMB1 with the power shell scripts and sc config commands and that worked.. but not reliably. Same error.. Network Path not found on occasion. 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Tried this already... Not reliable. Network path not found intermittently. 

EDIT: And we shouldn't be having to do stuff like that anyways... When you think about it. ;)

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I would like to say, that with 1803 and Windows 7 clients no issues at all.

SMB2 seems to be working. Too bad we can't disable SMB3 without disabling SMB2 as well. There doesn't seem to be a way.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Because MS made changes to Win v1803 that caused issues for PC's to resolve link between IP and Hostname in peer-to-peer networks.

I have solve this issue by using hosts -table (step 6.2 on my example), to create link between IP and Hostname. (Not very handy on large networks.)

It's old historic way back from 60's in ARPANET, the predecessor of internet, long time before DNS was invented.

https://answers.microsoft.com/en-us/windows/forum/windows_10-files/homegroup-removed-how-to-get-network-sharing-work/01277332-2916-4a68-853a-116696b20743

"Are you guys at Microsoft planning on fixing this stuff?"

To get your concern to MS dev engineers you have to use Feedback Hub.

Update = Replace old bugs with new ones.

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

uh, yes it does work every time. I have did about 300 PC's since v1803 on numerous Home and Business networks.

Instead of using  \\Computer Name

you have to create shortcuts to them using

 \\Computer IP ADDRESS

Then you connect to each PC using the IP ADDRESS shortcut, not through network folder.

Then if you have the connection issue between PC's and having to connect by

 \\Computer IP ADDRESS

you will need to go into each PCs C:\ drive>>properties>>security>>advanced

and add network user in the list with full permissions.

then when you select to share anything, EVERYONE user is there by default. then you add NETWORK in the list, set the permissions for both the same.

It is all explained in my article midway down with photos.

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Resolving the computer by IP is... just... this whole thing is broken. I suppose I can do try that at an office. But... even if it does work, we need to be letting MS know that this is not.. satisfactory.. not at all.

Windows 2000 6 Month MCSE course... is my background...  

This 1803.. ain't right... Having to enable services for automatic just to get the computer name to show up in the network list.. isn't good.

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thank god we don't have these problems with Server 2016! =0

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated September 15, 2020 Views 21,428 Applies to: