Need some help, i been battling with my main PC, running windows 10 Home that recently updated to 1803. On 1709 and before, sharing was as simple as its been for years with windows, i own many PC on a local network, and all have same user and pw, and sharing was as simple as turning on network discovery, i can see all my pcs and access their main hard drives, even shared individual extra hardrives from some pcs, all work perfect. Now windows 10 decided to drop Workgroups on 1803 and probably some other stuff that broke my network sharing. I still have a 4x Windows 7 pcs, a blue iris dedicated camera server, a small pc that its use for when someone else needs a pc, my brothers laptop, a windows 2011 (thats similar to 7) and now dual booting my pc between 7 and 10. All windows 7 PCs work great, but none of my windows 10 pcs (2 with home, 2 with pro) can access the windows 7 machines, they see the PC on the network but once you click on them, they negotiate but never resolve, Error 0x80070035 appears. I have look for tutorials, on youtube and forums, i feel there are lots of info as this is something that many use, but i have tried everything that i have found and still the same issue. Here some videos and things that i have tried, How To Homegroup Without Homegroup in Windows 10 - April 2018 Update - Setting / Network and Internet / Status / Change connection properties / Network Profile / Private - Setting / Network and Internet / Status / Sharing options / Private / Turn on network discovery, Turn on File and printer Sharing - Setting / Network and Internet / Status / Sharing options / All networks / Turn off public folder sharing, use 128bit encryption, Turn off password protected sharing - Windows Explorer / Folder / Give Access to / Everyone How To Share a Complete Drive in Windows 10 - April 2018 Update I also tried to share the folder and hardrive as explained on the video. Also did the Services / Function Discovery Resource publication / Automatic and checked that it was started and running. Error 0x80070035 "No se Encuentra la Ruta de Acceso a la Red" en Windows 10/8/7「4 Soluciones」2018 - TCP/IP Netbios Helper: check that it was automatic and running - Network and Sharing center / Ethernet / Properties / TCP/IPv4 / Properties / Advanced / WINS / Enable NetBios over TCP/IP - REGEDIT / Hkey_Local_machine / Software / Microsoft / MSLicensing / Removing HARDWAREID and STORE - Local Security Policy / I couldn't do it because its removed on my freshly formatted w10 1803, probably the video is 1709 that was upgraded (i really don't know). I still cant access any of the windows 7 computers drives or folders from a windows 10 1803 machine, i have even formated in case i messed it up, and did all the settings again, no luck, i was so frustrated that i installed windows 7 again on my main pc and it works fine accessing windows 7 and 10 machines. Either way, i really want to go back to 10, i have issues with Z370/8700K on 7 (not huge but does have some issues), so if you have any recommendations ill give a shot. Thanks,
Hi there. Good news first: 0x80070035 means "network path not found" (and yes, this is indeed good news because it is likely that your firewall blocks the traffic or the method used is not supported on one of the machines; for both ways there are solutions) Is the Win7 machine visible by PING from the Win10 one? Is the Win10 machine visible by PING from the Win7 one? Are any ISATAP network cards found within device manager? Delete them if not needed. File sharing still enabled? Win7 machine is up 2 date with Windows Updates? (Asking because of WannaCry patch) Is either the Win7 machine set to use SMB greater than v1 or your Win10 machines set to use SMB v1? Because Win10 (out-of-box) only supports SMB v2 or greater, while Win7 sticks to ONLY SMB v1. You may change that, but those are the default values. They have to agree to use the same version on both ends. The IP address of the "server" is static? (heavily recommended but not necessary, you have to use tzhe name then later on) Use username/password combo to share. Assuming Win7 is the server, Win10 is the client: Create a folder or select one you want to share. Create a "share user" on the Win7 machine, standard user is OK, no admin needed. Give the account a password. Right click -> properties -> "sharing" (I do not know the exact phrase in English) -> "Advanced sharing" Setup a name ("$" at the end makes it "invisible" by network discovery) and setup access rights. Give your share user full access or the access you need (read only?). Ensure the user may write/read to/from this directory by accessing the folder properties (after you exit the share options), select SECURITY and check the rights of the user and change it if needed. You could effectively block yourself by setting the share user to FULL ACCESS in the sharing options but denying the user any access with the SECURITY options. Just FYI ... Ensure Windows Firewall (or the product you use) is setup to allow file sharing / SMB. Test locally to access your share by entering: Code: \\127.0.0.1\YOUR_SHARE_NAME Try to setup this as a permanent share localy, either by navigating to COMPUTER and setup a network drive or by this command (sets the share as drive Z:, change letter if needed): Code: net use Z: \\127.0.0.1\YOUR_SHARE_NAME With both methods, a popup window shold appear, asking you for the username / password to access. If this doesn't work locally to this point, either your firewall is messing with your system / share options or because of previous repairs your system is somehow damaged. If this works, head on to the next steps. You managed to get your share 100% working to this point. SMB is commonly used within enterprise networks and is compatible through different versions of Windows, even though older versions pose some security risks (see SMB 1.0 and WannaCry). Start up your Win10 rig and go to COMPUTER and setup a network drive to the Win7 server. But instead of 127.0.0.1 enter the correct IP of the Win7 machine or if you use dynamic IP addresses use its DNS name like: Code: \\10.20.30.40\YOUR_SHARE_NAME or \\YOUR_DNS_NAME\YOUR_SHARE_NAME like: \\386SX\totally_not_porn$ Click on the mark where it says "use alternative credentials" or the like and OK. Same window will pop up and ask for the user/password. Enter your share user WITH THE MACHINE NAME like this: Code: User: 386SX\shareuser Password: !your!password! You tell your Win10 machine to login with the credentials of "shareuser", which are found on the machine "386SX" and its password "!your!password!". You created the user on another amchine, right? So you have to point your machine to the storage of the credentials you want to use. Connection should succeed, Explorer should open and show the contents of the share. If you fail at some point please post screenshots and grey out sensible information. Regards EDIT: Microsoft to the rescue ... https://support.microsoft.com/en-gb...-disable-smbv1-smbv2-and-smbv3-in-windows-and
Quote from the last MS link I posted: I would strongly recommend to >>DISABLE SMB<< 1.0 on your Windows 10 machines, but enable SMB 2.0 in your Windows 7 machine. I may remind you SMB 1.0 is very insecure, SMB 2.0 is far better (but not perfect ...) and offers the same stuff 1.0 would offer you.
OK if it is only temporary. I just wanted to point this out so the OP considers changing this and does not use it as a permanent solution.
Thanks 386SX and WhiteLightning for replying on my thread, Yes Yes, the Win7 pc can ping the Win10 pc Yes the Win10 pc can ping the Win7 pc Not sure what you mean but ill look for them. I have done this, and it does work, but right now it doesn't, its like doesn't negotiate, like it times out and gives me the error 0x80070035 Both Win7 and Win10 are up to date. IIRC they are as windows comes with, i never really played with them, simply worked and never mess with them. I think my win7 machine is using SMBv1, on my win10 is confusing picture below shows it still has it. They are both dynamic but not a big deal, i just do an ipconfig to get the current local ip for the session, usually it remains like that for months, but i can set them static if you think this would fix the problem. This did work, while i cant access the folders shared under networking,opening the run and typing \\192.168.0.28\Downloads open the file explorer and showed it as an ip, i can access the folders now =), extra step but im fine with it. Now seems like Microsoft is acknowledging the problem, seems im not alone on this 1803 change and lots of users are having my same issue, File Explorer may not detect other devices or perform file sharing on the local network when running Windows 10 version 1803 , can you please take a look into the changes they suggest if you recommend them? im kinda thinking on leaving it as it is for the time being, with your address solution i should be fine, and wait for a next update to fix the issue. This is how my win10 pc is (didnt touch it yet), seems has the client and not the server, but i never access the win10 machine, i only access three win7 machines and whs2011, so im assuming clicking the server wont matter. Thanks again for your suggestions,
From what I see this should be fine, except the UPNP Host service. If not critically needed, I would disable this. UPNP tends to be easily exploitable. But hey, you know the sentence: "Never change a running system." As long as it works for you right now, leave it as it is. You're welcome. EDIT: Regarding the SMB server service: You will only need this if your machine (Win10) acts as a server. Because you said it doesn't, you don't need the service. For easy access probably you would prefer to setup a network drive. You can do this by going into "Computer" and opening the ribbon. Right now I cannot recall what the menu itself is named, but look for "Map network drive" as the button to click on. Enter the path like above (\\192.168.0.28\Downloads) and set what drive letter should be setup for it. I for myself start from the last ones (Z: going backwards like Y, X, ...), but you are free to use A: or B:, which somehow may lead to something funny, for example "Please insert a disk in drive A:" and you set A: to be a network drive with all the needed files on it. It sometimes works just fine (but sometimes it doesn't, so this is experimental). Remember to select the optuion to keep the share on reboot, so it doesn't vanish. An alternative to setup a share as a permanent share which survives a reboot by entering in an elevated (administrative) command prompt: Code: net use Z: \\192.168.0.28\Downloads /PERSISTENT:YES or if you need separate user details to access use: Code: net use Z: \\192.168.0.28\Downloads /USER:192.168.0.28\USERNAME PASSWORD /PERSISTENT:YES /SAVECRED Change USERNAME and PASSWORD to the ones you use. Please note the is a space between USERNAME and PASSWORD, but no other argument like "/PW:" or something to enter the password. So for example your username is BIGDADDY and your password is HeLL123 (password is CaSe-SenSiTiVe!) you should enter: Code: net use Z: \\192.168.0.28\Downloads /USER:192.168.0.28\BIGDADDY HeLL123 /PERSISTENT:YES /SAVECRED I wish you the best and hope this is something what makes your work a bit easier.
Not meant to be rude, but ... how does this fit into this thread? What kind of help do you want? I am willing to help you, but please at least give me some more details to work with. ;-) What Windows Update did it? => Find the KB number! Did you try to revert it? => Open CMD as admin and run: Code: wusa /uninstall /kb:1234567890 Input your KB number instead of "1234567890" and hit enter. What is the message you get from Fightcade? => Example: "Error 404: Fightcade service not found." or something like that. Otherwise usually Code: format c: /q (ran by administrative CMD) deals with all issues. (That's a joke, if that is not clear!)
