G'day this is what finally worked for me. No SMB1 crap, IPV 4 and IPV6 enabled and the table below. I know I am connecting a W10 to WServer2016 but the setup on the Client box should help you out. It took me 4 days to get it there and now everything is in harmony (for now).
I am not using a server just network my main win 10 to my other windows 10 & windows 7 through a router sharing folder & there a block on it.
G'day...yes I understood that however, originally I too had 2 W10x86 1803 boxes with the same issue as you described. I then installed the server on one of those boxes but kept the other as it was and still I couldn't connect or kept loosing the connection. Then I applied all those settings that you see under the "Client" column. Now it all works just fine. Oh, and before I did all that I did a clean and fresh install of W10x64 1803 so that I started with a clean slate. Good luck...Cheers!
Explain how do you get to the top part of this graph to these area to change? i am aware of services.msc the other areas above where do I go there?
I can only guess that those Firewalls Rules (Ntray,NDigital,NPVR,NRecord) are for connecting to the WServer2016/Domain. I'm not even sure what they are, but I've never seen them on Win10 Home or Pro ... lol
I saw the settings in services.msc there & changed them & make no difference.
The Ntray, NRecord, NPVR and NDigital are for another program to access other computers on the network specific to that proggy. So please disregard sorry for the confusion. However, in order for 1803 to connect to another networked computer you need to enable the following : Window Defender on, FW on for private and guest or public, Function Discovery Provider Host, Function Discovery Resource Publication, SSDP Discovery and UPnP Device Host=Running, automatic, Local Service. Now there are a few dependencies that need to be check to make sure they are running as well. They should be by default but it never hurts to check. Those are: Network Store Interface Service, DCOM Server Process Launcher, RPC Endpoint Mapper, Remote Procedure Call (RPC), once you make these changes then you should be able to see your other computer when clicking on Network in file Explorer. Restart your PC and they (or it) should be seen. Do this on a second PC as well so they can both see each other. If they don't see each other then go back to the FW settings and turn it off for both Private Networks and or Guest Networks but leave the Public Networks enabled. This is just for testing the changes you made. If you can't see you network comps then turning off the firewall should definitely allow them to be seen. If they are seen with the FW off then obviously its a FW issue. Remember that 2 of your PC's have to be set up this way. When M$ decided to eliminate SMB1 due to a possible breach M$ in their infinite wisdom sent out 1803 with no SMB1 enabled but introduced SMB2 and so on. This is just the first step. If you get this far and are able to see the comps but not get into a specific folder/file, you need to set permissions and security for them. This is what worked for me on 2 W10 1803's plus acces to the server on a domain environment. Cheers!
You saying in firewall settings? inbound or outbound? You need to tell me where to go there & post pictures of it as I can't find these in firewall settings. The rest also where do I go after firewall settings? You are all over the place & not sure. I do not see RPC Endpoint Mapper but RPC Locator & its set to manual & enabled it but no change. I can see the PC on my other machine though network in windows explorer but not the shared folders on there if i click it says windows cannot access:\\(Name of PC) & also on the PC i am sharing the folder I can see the shared folders but if i try to open it in windows explorer on it says same message as other PC. I do not see the public shared folders on main PC also as well as other PC.
G'day...No worries, I will get some screen shots for you to follow as soon as I finish a Windoze installation for a customer. Should be about an hour or so. Cheers!
In the meantime I did notice Eagle 51 gave you a link to a tutorial that has pretty much what I did/do to make this work. My setups are mostly based on Options 1,2,6 and 7 with a few tweaks. I wish I had seen this tutorial earlier it would've saved me some time. In any event at this point for you, since you most likely have made a bunch of changes. I would start by implementing a W10 repair either from your ISO file on USB or using the repair tool within your setup. This way we can start from fresh. No need to reinstall, just a repair will do the trick and it is much faster. Essentially what the repair will do is bring back you PC to most of its defaults. A "reset" is more detailed but it gets rid of some of your stuff so stay away from that for now.
Last edited by snaitaz; 06 Sep 2018 at 10:20.
Thanks for the info actually. I have never had similar problems with the W10 versions up to 1709 (never installed 1803 actually).
Quote