Nothing of the above-mentioned worked for me, but luckily I found a solution. I'll put it here just in case: In "Local Group Policy Editor" - Computer Configuration > Administrative Templates > Network > Lanman Workstation - Enable insecure guest logons: Not configured (by default) switch to *Enabled* Weird that it was the "Error 0x80070035 The network path was not found" pop-up and not the one saying that unauthenticated guest access is blocked by security policies.
Hi there, by far you have the best video for solve this issue. There's one thing you can add to your video that can help many people once it was the only thing that solved the issue in my Win10/Seagate Personal Cloud and it's related do saved credentials. Follow this: Control Panel > User Accounts and Family Safety > Credential Manager - then select Windows Credentials and look for saved credentials (should be the same as the login name used for the Seagate Personal Cloud/ NAS web interface). Afterwards go to map network driver and try again (in my case I had to click on "Connecting using a different user name". Good luck for all.
deleting those folders in regedit worked for me. background: fresh install of win 10 64bit; spent a week trying to map the NAS network drive; this video helped.
You deserve a comment of gratitude. I have tried many suggestions, to an extent that I started to lose an overview of what combinations I have already tried. Following your steps resolved my issue connecting my Synology DS918+ NAS system in Windows 10 1709. Before this fix, I could only see it and access through a browser but not through Windows Explorer. Thank you very much.
thank you so much for video. just to add i followed all the steps and nothing was working, i then turned my wi-fi adaptor off and boom, NAS drive came to life. turned wi-fi back on and its all working fine. saved your videos for any future trouble shooting. very clear and helpful. many thanks.
Thanks for this video. Unfortunately I'm still stuck with error 0x80070035. I have already worked through your other video on "The network path was not found". Anything else I can try except for fresh installation of Win 10 Pro 64-bit?
I had this problem on a new install of Win 7 Pro, tried to find answers to fix this online with no success. I then I remembered how you solved another hard problem for me years ago. You will always be my first search from now on.Thank you this worked
I came across this SOLUTION after half a day of doing everything else (the same 5 steps this video and many others show). I'm grateful to the video creator here. It's all helpful and good. Just not what I needed. FOR EVERYONE WHO IS STILL STUMPLED....Try this...(This applies to DSM Synology) OP: Can you share the step to mount missed folder? I had similar issues, not all folder missing after DSM updates. Solution: Just figured this out myself after a brief panic after not seeing my encrypted folders: In DSM: Go to Control Panel Select Shared Folder from the sidebar Choose your encrypted folder Select the 'Encyption' dropdown menu and choose "Mount"
Brilliant! Tried following several other UA-cam videos with no success before following your suggestions. I was only successful when I implemented your very last, almost afterthought suggestion, and nearly didn't bother watching all the way through to the end. As some ppl have said following your suggestions hasn't worked for them, it might be better to simply itemise all your procedures, in case they give up before this final suggestion. Anyway, many thanks for doing this guide, it's the only one I have found that achieves access to my NAS in Windows 10.
Finally a video that shows a "real" solution for a network not working. A 10 minutes solution after looking hours for videos that all say the same thing and don't fix anything. Thanks a million.
One little utility you could use is wireless network watcher. It will tell you the IP addresses of everything connecting to your network, in real time. If the drive your trying to connect to isn't listed then power off your media server or whatever you're having problems trying to connect to - Power it back on and check to make sure the IP address shows up in the Wireless Network Watcher utility. Once it does then you know you don't have a hardware of cabling issue and you can proceed to follow the instructions listed in the video. Good video by the way.
It worked! thanks a lot: Go to Local Policies - Security Options -Network security: and look for LAN Manager Network security: LAN Manager authentication level. Now change this to Send LM & NTLM-use NTLMv2 session security if negotiated.
Awesome job, been having issues with my nas for a long long time now, nothing has worked till now and finally after watching this it is fixed, had to do the last pro bit but hoorah it is all working, Great job Brian I thank you .
These are all great ideas and a demonstration of good troubleshooting. Not splitting hairs here but, I have been doing this a long time. Could be something else as well! While I am a Linux guy I do actually use Windows and OSX as well. I too had run into this issue and it frustrated the hell out of me. If None of this worked for you, here is what you will need to do. NOTE, SMBv1 is VERY INSECURE, for this reason it has been disabled. Your NAS provider, mine is Seagate, should provide a firmware update to fix this issue by updating the NAS to use Version 2. My NAS was discontinued and runs OpenWRT so , I could update it manually being its mostly open source but its a pain in the ass. That said you too will likely not be able to update your NAS. If its an actual file server then yes you need to update it instead of doing this. 1) We need to open Control Panel, so you can either type Control Panel in the search box or right click the start button choose run and type Control Panel. 2)Click on "Programs" then Click "Turn Windows Features on or off" ( Under the heading "Programs"). Scroll down just below SNMP to SMB 1.0/CIFS File Sharing Support. You can check the Box for this option, it has likely been unchecked as a security measure. Checking this box enables the client and server using protocol 1. Ideally you really only need the client enabled. Once done reboot. You should be able to access NAS and or server folder again. Cisco Content Security Engineer, CPT, CEHv8.
Worked great on a connection between Win7 and WinXP and also worked to a Linux volume. This problem does not seem to happen with WinXP but has been an issue with Win7 machines. Thank You!!!
Thanks for the video, great step by step instructions. Re-installed Windows 10 and could see my NAS on the network but could not connect. I followed every step and nothing solved my problem. Frustrated I eventually checked my Zone Alarm Extreme Network Security settings, changed quite a lot and hey presto - I could then map and access my NAS. I cannot say which setting that I changed solved the problem, but I suggest people with the same issues check their Firewall settings as well.
Works well. Additionally it might require checking the firewall setting especially with anti virus software. Flag the network as trusted, just incase you have Kaspersky installed.
Nothing worked for me. Then I found this for my Synology NAS: Login to your NAS website: Control Panel > File Services > Advanced Settings > Maximum SMB Protocol: Set this to SMB3 > Apply THIS did work for me!
Same. WinServer2019 can access win10 pro client, but Win10 Pro client will not access the server shared folder. All could have been avoided if Microsoft would have left NIC teaming in windows 10 pro.
@@dinithshalinda8069 make your computer visible and make sure ur network is private. As I remembered it worked on some computers and other not. I had to reinstall a fresh windows
I found the solution. Windows 10 doesn't have SMB1 activated. Do it in the program installation section (where you can activate or deactivate Windows functions). System will ask to reboot. Do so, and voilá.
1.) Does it apply also to sharing other computer on the same network? 2.) Do I configure these settings in the computer I want to access from? 3.) How do I add the 'Control Panel' to the menu when right click on the Start sign? 4.) When I change the Service to Automatic and click on Apply, the Start button is disabled and I have to first Stop it in order to have the Start button enabled. Does it make sense?
Worth to try to enable SMB V1 for Win10: Control Programs > Programs and Features > Turn Windows features on or off > SMB 1.0/CIFS File Sharing Support
for somebody that still unable to fix this, hope you find this helps. on the destination pc/notebook (not on the pc that had 0x80070035 error), search Advance sharing setting. then make sure you turn on "Turn on file and printing sharing" both on guest or public and private section. hope this helps someone! thanks
This is an amazing video.. however.. I can access my NAS (D-Link DNS320L), I can map a network drive, I can browse it with windows explorer.. but copying files results in the error you're describing here. I do a monthly backup so I just add a certain amount of files, like 15-20GB/month.. and the copy process fails randomly at a different percentage of the process, different every single time. Sometimes the "retry" button would work, sometimes it doesn't work.. sometimes I have to click it 20 times and it resumes, but usually it doesn't. I have no idea what's going on. Both drives in the NAS seem to be working fine, they pass the SMART test and a full scan, there's 30% free on the drives. I tried reformating them, tried moving over from Raid 0 to JBOD, same thing happens. To be fair, I did manage to copy over 3TB with a few retries but now it's stuck on literally the last few gigs. These errors that happen at different times are hella hard to diagnose. Maybe it's time for a new NAS? Thanks for a great video.
This is a no-brainer suggestion/fix. The real problem, especially when accessing non-Windows shares, often lies with the client's "Microsoft Network" and "Network Access" related settings within Local Security Policy (secpol.msc).
From a win10 home laptop I can see 4 computers on my network (win7 PC, win8 PC, iMac, laptop). This tutorial helped with accessing the windows PC's. Any advice on accessing the iMac? It seems to be windows version dependent since the win7 PC can access the Imac with no problems.
thanks, dude, eventually fixed issue AFTER i followed your vid and then had to RESTART my MODEM. then it worked fine. Thanx P.S fekn hate windows. far too complex. it must have taken you or someone else weeks to troll through all the possible issues.
Hi, I have followed all steps in your video, but it always pop up the same error. I am using two computers connected by crossover cable, on both PC I have win 10. Do you have any idea what can cause this probem? Thx. BTW, very good video!
First of all thanks a lot for your tutorial, I really thought this would solve my error 0x80070035 problem. Unfortunately, I'm still stuck with it. I'm experimenting with Rasberry Pi5 and OpenMediaVault, I've set up a NAS with 4 X 4TB SSD drives. The SSD drives are combined in one (snapraid) pool. I have multiple laptops and desktops all on the Windows 10 operating system. The machines running Windows 10 full version have no problem accessing the network drive. But on the machines running Windows 10 Tiny the network drive is visible but access is denied. All the machines are visible to each other and can access each other's drive. The machines running Windows 10 Tiny are activated as Windows 10 IoT Enterprise LTSC , 21H2. Any other advice!?
I am a network engineer. I had problems with a personal cheep dell notebook I almost never use. So I did most of everything I already know how to fix computer problems and also watched a bunch of youtube videos on how to fix the yellow triangle issue. Nothing worked. So I turned ON the Personal Hotspot on my iphone and WAS able to connect my notebook wirelessly with NO problem. Doing it so, I eliminated the problem with my wireless hardware and software on the notebook. Therefore, once again I; Downloaded drives again directly to the notebook hoping to fix the problem, ran the installation and configurations. When I connected notebook back to my home router instead of the Iphone, I still got the same yellow triangle problem. So I connected to my shitting comcast router hoping to find a way to update the firmware but no luck. I found a way to make the router restart with its factory defaults setting. I did restart the router and After setting up the router with the same SSID and password, my notebook with wireless is working again without the yellow triangle at bottom of my Win10 machine. This particular cheap notebook has no ethernet card, just wireless; therefore it forced me to find the problem. It was hard for me to guess the router was causing whatever problem because I have other connected wireless Iphones, security PI3 cameras and chromecast all using the wireless router with no issues. I am glad it is working now and that I can share it with you all. good luck. God Bless
This worked for me... Go to Start, right click Run, type in the NAS IP address as follows... \\###.###.###.###, hit enter. Your NAS folder structure should show up under Windows... Double Click one of the folders you see and you should be prompted for you log-in credentials. Enter your credentials, you should be able to access your NAS's content... Window ran an update yesterday in my PC and I suspect this is the cause of the problem....
The above instructions are a temporary fix - You will need to do this each time you need to access the NAS. Haven't worked out how to make this permanent yet...
Windows 10 Enterprise LTSC Build 1809 The latest Fall updates have disable (SMB 1.0/CIFS File Sharing Support/SMB Direct) and (Insecure guest logons) This has a direct effect on router external drives and connecting shares on other computers. They are located separably 1) Control Panel>Turn Windows features on or off. 2) Local Group Policy Editor>Computer Configuration> Administrative Templates>Network>Lanman Workstation>Insecure guest logons (Set to Enable)
Been happily using a Raspberry Pi 3 setup with a 2TB portable SSD as a little NAS for the past 3 years. Suddenly today it won't connect. Getting the error you describe here. Tried everything here, even unplugged and restarted everything. Still nothing. What next to try?? good video, just didn't work for me thanks
I followed the video and successfully copied everything on my WIndow's pro computer. I restarted. No luck, still have the same error code. I went over everything again, everything perfect as described in your video. It just didn't work. I'm trying to connect to Huawei Mate 20 phone - It appears as a network drive like any other computer. Before I re-installed Windows, It connected fine Finally, I looked at my Windows Firewall Control. Windows Explorer.exe fixed the problem. Woohoo.
Hello, I have tried according to your instructions, but the error message is still there. Is there anything I need to be doing further? Plz, advise. Thanks for your video, it helped a lot.
Some folks have fixed it [including myself] by going to -> Control Panel -> Programs and Features -> Turn Windows Features Off or On and assuring a check-mark is in "SMB 1.0/CIF" but also un-checking the sub entry of "Automatic Removal." Having that SMB 1.0 unchecked is a default of latter updates.
Very good/clear explanations, but my problem was not solved - apparently (found out just now) it had to do with smb1 vs smb2. My NAS - WD from 2011 - apparently needed (the very old and unsafe) smb1.
I did everything in the video with no problems until the Map Network Drive box. I did not get the Enter Network Credentials box. The diagnostic still says error code 80070035. What do I do now? It simply says the device cannot connect.
Unfortunately for me, still can't access network computer. I followed all your steps mentioned in this video, still no luck. Same error code. Windows 10 21H1
I had the same problem, tried everything, 10 hours later I found the problem. It was Zonealarm free firewall that caused it. Installed Eset security and it solved it.
Just started having this issue recently on Windows 11, followed these steps and didn't fix it, still the same error code. Any updated fixes that I could do? The other machine that I'm trying to access on my Network is able to access mine no problem.
Please Brian can you next create the two videos I have asked for. First create the video that explains the difference between the .themepack & .deskthemepack file name extension. Then, create the second video explaining on how to fully create an Aero theme in Windows 7, and how to organize all the required items in a folder when creating custom wallpapers, colors, screensavers, cursors, sounds and icons. Thank you.
Nothing of the above-mentioned worked for me, but luckily I found a solution. I'll put it here just in case:
In "Local Group Policy Editor" - Computer Configuration > Administrative Templates > Network > Lanman Workstation - Enable insecure guest logons: Not configured (by default) switch to *Enabled*
Weird that it was the "Error 0x80070035 The network path was not found" pop-up and not the one saying that unauthenticated guest access is blocked by security policies.
Thanks a lot bro,this fix my error too... I refreshed my pc and then this network error popuped. thanks a lot
Thank you sir. After trying umpteen different things, this was what got me over the top. Well done!
This was the key to fixing my problem
THIS !!
Thanks dude
Hi there, by far you have the best video for solve this issue. There's one thing you can add to your video that can help many people once it was the only thing that solved the issue in my Win10/Seagate Personal Cloud and it's related do saved credentials. Follow this: Control Panel > User Accounts and Family Safety > Credential Manager - then select Windows Credentials and look for saved credentials (should be the same as the login name used for the Seagate Personal Cloud/ NAS web interface). Afterwards go to map network driver and try again (in my case I had to click on "Connecting using a different user name". Good luck for all.
deleting those folders in regedit worked for me.
background: fresh install of win 10 64bit; spent a week trying to map the NAS network drive; this video helped.
You deserve a comment of gratitude. I have tried many suggestions, to an extent that I started to lose an overview of what combinations I have already tried. Following your steps resolved my issue connecting my Synology DS918+ NAS system in Windows 10 1709. Before this fix, I could only see it and access through a browser but not through Windows Explorer. Thank you very much.
thank you so much for video. just to add i followed all the steps and nothing was working, i then turned my wi-fi adaptor off and boom, NAS drive came to life. turned wi-fi back on and its all working fine. saved your videos for any future trouble shooting. very clear and helpful. many thanks.
Thanks for this video. Unfortunately I'm still stuck with error 0x80070035. I have already worked through your other video on "The network path was not found". Anything else I can try except for fresh installation of Win 10 Pro 64-bit?
I had this problem on a new install of Win 7 Pro, tried to find answers to fix this online with no success. I then I remembered how you solved another hard problem for me years ago. You will always be my first search from now on.Thank you this worked
OMG, I can't believe this has an end now, been looking for a solution for days! Deleting those files solved the issue! THANKS SO MUCH!
I came across this SOLUTION after half a day of doing everything else (the same 5 steps this video and many others show). I'm grateful to the video creator here. It's all helpful and good. Just not what I needed.
FOR EVERYONE WHO IS STILL STUMPLED....Try this...(This applies to DSM Synology)
OP: Can you share the step to mount missed folder? I had similar issues, not all folder missing after DSM updates.
Solution: Just figured this out myself after a brief panic after not seeing my encrypted folders:
In DSM:
Go to Control Panel
Select Shared Folder from the sidebar
Choose your encrypted folder
Select the 'Encyption' dropdown menu and choose "Mount"
Brilliant! Tried following several other UA-cam videos with no success before following your suggestions. I was only successful when I implemented your very last, almost afterthought suggestion, and nearly didn't bother watching all the way through to the end. As some ppl have said following your suggestions hasn't worked for them, it might be better to simply itemise all your procedures, in case they give up before this final suggestion. Anyway, many thanks for doing this guide, it's the only one I have found that achieves access to my NAS in Windows 10.
Super clear, step-by-step and thorough instructions. Worked perfectly! Thank you!!!!!
Finally a video that shows a "real" solution for a network not working. A 10 minutes solution after looking hours for videos that all say the same thing and don't fix anything.
Thanks a million.
One little utility you could use is wireless network watcher. It will tell you the IP addresses of everything connecting to your network, in real time. If the drive your trying to connect to isn't listed then power off your media server or whatever you're having problems trying to connect to - Power it back on and check to make sure the IP address shows up in the Wireless Network Watcher utility. Once it does then you know you don't have a hardware of cabling issue and you can proceed to follow the instructions listed in the video. Good video by the way.
It worked! thanks a lot:
Go to Local Policies - Security Options -Network security: and look for LAN Manager Network security: LAN Manager authentication level. Now change this to Send LM & NTLM-use NTLMv2 session security if negotiated.
DUDE! You freaking ROCK!!! That solved the issue for us! Those two dang registry folders did the trick! Thank you SO MUCH!!!
It actually worked, out of all the hours spent trying to figure this out, those registry folders were the key. Thanks!
Awesome job, been having issues with my nas for a long long time now, nothing has worked till now and finally after watching this it is fixed, had to do the last pro bit but hoorah it is all working, Great job Brian I thank you .
You're welcome.
Still solving the problem after the latest Windows update. The last one for Windows Pro did the trick. Thank you!
These are all great ideas and a demonstration of good troubleshooting. Not splitting hairs here but, I have been doing this a long time. Could be something else as well! While I am a Linux guy I do actually use Windows and OSX as well. I too had run into this issue and it frustrated the hell out of me. If None of this worked for you, here is what you will need to do. NOTE, SMBv1 is VERY INSECURE, for this reason it has been disabled. Your NAS provider, mine is Seagate, should provide a firmware update to fix this issue by updating the NAS to use Version 2. My NAS was discontinued and runs OpenWRT so , I could update it manually being its mostly open source but its a pain in the ass. That said you too will likely not be able to update your NAS. If its an actual file server then yes you need to update it instead of doing this. 1) We need to open Control Panel, so you can either type Control Panel in the search box or right click the start button choose run and type Control Panel. 2)Click on "Programs" then Click "Turn Windows Features on or off" ( Under the heading "Programs"). Scroll down just below SNMP to SMB 1.0/CIFS File Sharing Support. You can check the Box for this option, it has likely been unchecked as a security measure. Checking this box enables the client and server using protocol 1. Ideally you really only need the client enabled. Once done reboot. You should be able to access NAS and or server folder again. Cisco Content Security Engineer, CPT, CEHv8.
Worked great on a connection between Win7 and WinXP and also worked to a Linux volume. This problem does not seem to happen with WinXP but has been an issue with Win7 machines. Thank You!!!
Hi, thank you for the great video, I follow all the steps but no luck, any other suggestions please?
Thanks!
Funcionó. He resuelto el problema de acceso al NAS siguiendo las instrucciones de este video. Gracias!
Fixed my problem. Couldn't connect to my other computers after Windows 10 Spring upgrade. Kudos!
Braco!! You are my hero for the day. I have taken days to try and sort out the mapping problem. Thanks for your clear and practical video.
Had trouble using Hamachi to access a server drive. This helped fix the problem. Thanks
Thank you, still helping in 2024👍
Hi, thanks for this video, followed the procedure and all sorted. It was annoying as my laptop used to see my NAS drive it then stopped.
Thanks again.
Thanks for the video, great step by step instructions. Re-installed Windows 10 and could see my NAS on the network but could not connect. I followed every step and nothing solved my problem. Frustrated I eventually checked my Zone Alarm Extreme Network Security settings, changed quite a lot and hey presto - I could then map and access my NAS. I cannot say which setting that I changed solved the problem, but I suggest people with the same issues check their Firewall settings as well.
Have been fighting this for a a couple of weeks on a brand new Windows 10 computer. This worked!
Tried RUN box as shown at 06:02 and it asked me user name and password. I used my NAS -s user name and password and it worked. Thank you for the help
I love you Britec! You solved my problem that I have worked on for the past several weeks! THANK YOU!
Works well. Additionally it might require checking the firewall setting especially with anti virus software. Flag the network as trusted, just incase you have Kaspersky installed.
Nothing worked for me. Then I found this for my Synology NAS: Login to your NAS website: Control Panel > File Services > Advanced Settings > Maximum SMB Protocol: Set this to SMB3 > Apply
THIS did work for me!
You are a life saver. Thank you!
Depois de procurar tanto pela solução para este problema, foi uma alivio enorme encontrar a solução no teu video, siceramente muito obrigado
I have done everything and it's still the same issue. I can't access other computers but they can access mine except for one computer
Same problem
Same. WinServer2019 can access win10 pro client, but Win10 Pro client will not access the server shared folder. All could have been avoided if Microsoft would have left NIC teaming in windows 10 pro.
please check the other computer network discovery setting also check the network related services puy in automatic
You fix your problem plz help me
@@dinithshalinda8069 make your computer visible and make sure ur network is private. As I remembered it worked on some computers and other not. I had to reinstall a fresh windows
It's worked for me! Thank you for sharing tips and step by step, already subcribed🙌
Didn't work. This problem exists from the last major Windows update 2 or 3 weeks ago that upgraded Win 10 Pro version to 1709.
same with me
have you found the solution?
I found the solution. Windows 10 doesn't have SMB1 activated. Do it in the program installation section (where you can activate or deactivate Windows functions). System will ask to reboot. Do so, and voilá.
FandreiosAner I enabled smb1 and now it only happens on two devices instead of all any further tips¿
I did so, it works!! Thank You!
BRO YOU ARE A FLIPPIN LEGEND!! I STRUGGLED FOR WEEKS WITH THIS ERROR AND YOU JUST FIXED IT!!
THANK YOU! NEVER STOP MAKING VIDEOS AND HELPING PEOPLE
I will try, glad I could help.
1.) Does it apply also to sharing other computer on the same network?
2.) Do I configure these settings in the computer I want to access from?
3.) How do I add the 'Control Panel' to the menu when right click on the Start sign?
4.) When I change the Service to Automatic and click on Apply, the Start button is disabled and I have to first Stop it in order to have the Start button enabled. Does it make sense?
Worth to try to enable SMB V1 for Win10: Control Programs > Programs and Features > Turn Windows features on or off > SMB 1.0/CIFS File Sharing Support
It worked great, I did this fix on a windows 7 computer and instead deleting the registry keys I just renamed them and then worked.
As always well explained - Thanks Brian - Have a great weekend!
you too John.
Thanks for putting instructions in text as well sometimes I cannot play the video due to restrictions.
for somebody that still unable to fix this, hope you find this helps.
on the destination pc/notebook (not on the pc that had 0x80070035 error), search Advance sharing setting. then make sure you turn on "Turn on file and printing sharing" both on guest or public and private section. hope this helps someone! thanks
Watched several other videos and this is the one that worked thank you!
This is an amazing video.. however.. I can access my NAS (D-Link DNS320L), I can map a network drive, I can browse it with windows explorer.. but copying files results in the error you're describing here. I do a monthly backup so I just add a certain amount of files, like 15-20GB/month.. and the copy process fails randomly at a different percentage of the process, different every single time. Sometimes the "retry" button would work, sometimes it doesn't work.. sometimes I have to click it 20 times and it resumes, but usually it doesn't. I have no idea what's going on. Both drives in the NAS seem to be working fine, they pass the SMART test and a full scan, there's 30% free on the drives. I tried reformating them, tried moving over from Raid 0 to JBOD, same thing happens. To be fair, I did manage to copy over 3TB with a few retries but now it's stuck on literally the last few gigs. These errors that happen at different times are hella hard to diagnose. Maybe it's time for a new NAS? Thanks for a great video.
great video, I've looked at many videos showing how to solve this problem and yous is the best.
This is a no-brainer suggestion/fix. The real problem, especially when accessing non-Windows shares, often lies with the client's "Microsoft Network" and "Network Access" related settings within Local Security Policy (secpol.msc).
"0x80070035 network path not found"
Solution:
gpedit.msc > Computer Config > Administrative Templates > Network > Lanman Workstation > Enable insecure guest logons > Enable
Thanks
This is final solution for me. Works well!
thanks!
This work for me, Thanks!!
The only solution work for me. Thank you Bro. And thank for britec for the all greated video
From a win10 home laptop I can see 4 computers on my network (win7 PC, win8 PC, iMac, laptop). This tutorial helped with accessing the windows PC's. Any advice on accessing the iMac? It seems to be windows version dependent since the win7 PC can access the Imac with no problems.
thanks, dude, eventually fixed issue AFTER i followed your vid and then had to RESTART my MODEM. then it worked fine. Thanx P.S fekn hate windows. far too complex. it must have taken you or someone else weeks to troll through all the possible issues.
toda i attend this problem. ? and your solution i am using... *super* --- your solution is working..... thank you
Thank You very much! The first step for mine was not disabled but I followed the rest and it is fixed.
Hi, I have followed all steps in your video, but it always pop up the same error. I am using two computers connected by crossover cable, on both PC I have win 10. Do you have any idea what can cause this probem? Thx. BTW, very good video!
First of all thanks a lot for your tutorial, I really thought this would solve my error 0x80070035 problem.
Unfortunately, I'm still stuck with it.
I'm experimenting with Rasberry Pi5 and OpenMediaVault, I've set up a NAS with 4 X 4TB SSD drives.
The SSD drives are combined in one (snapraid) pool.
I have multiple laptops and desktops all on the Windows 10 operating system.
The machines running Windows 10 full version have no problem accessing the network drive.
But on the machines running Windows 10 Tiny the network drive is visible but access is denied.
All the machines are visible to each other and can access each other's drive.
The machines running Windows 10 Tiny are activated as Windows 10 IoT Enterprise LTSC , 21H2.
Any other advice!?
It's actually worked! I've been frustrated trying to figured it out, I'm glad I came across this video and actually fixed the error. Thank you so much
Thank you for this! This solution worked great for me! Fixed Error 0x80070035 in Windows 10
Thanks man solved this after headbanging for 3hrs
I am a network engineer. I had problems with a personal cheep dell notebook I almost never use.
So I did most of everything I already know how to fix computer problems and also watched a bunch of youtube videos on how to fix the yellow triangle issue.
Nothing worked. So I turned ON the Personal Hotspot on my iphone and WAS able to connect my notebook wirelessly with NO problem.
Doing it so, I eliminated the problem with my wireless hardware and software on the notebook. Therefore, once again I;
Downloaded drives again directly to the notebook hoping to fix the problem, ran the installation and configurations.
When I connected notebook back to my home router instead of the Iphone, I still got the same yellow triangle problem.
So I connected to my shitting comcast router hoping to find a way to update the firmware but no luck. I found a way to make the router restart with its factory defaults setting.
I did restart the router and After setting up the router with the same SSID and password, my notebook with wireless is working again without the yellow triangle at bottom of my Win10 machine.
This particular cheap notebook has no ethernet card, just wireless; therefore it forced me to find the problem.
It was hard for me to guess the router was causing whatever problem because I have other connected wireless Iphones, security PI3 cameras and chromecast all using the wireless router with no issues. I am glad it is working now and that I can share it with you all. good luck. God Bless
Deleting the registry entires worked for me, thanks!
I've done everything exactly as is stated in this video, but unfortunately, I am still not able to access my NAS. What could be the problem?
This worked for me...
Go to Start, right click Run, type in the NAS IP address as follows... \\###.###.###.###, hit enter.
Your NAS folder structure should show up under Windows...
Double Click one of the folders you see and you should be prompted for you log-in credentials.
Enter your credentials, you should be able to access your NAS's content...
Window ran an update yesterday in my PC and I suspect this is the cause of the problem....
The above instructions are a temporary fix - You will need to do this each time you need to access the NAS.
Haven't worked out how to make this permanent yet...
You sir have won a beer if we ever meet Ill treat you like a queen thank you very much.
Windows 10 Enterprise LTSC Build 1809
The latest Fall updates have disable (SMB 1.0/CIFS File Sharing Support/SMB Direct) and (Insecure guest logons)
This has a direct effect on router external drives and connecting shares on other computers.
They are located separably
1) Control Panel>Turn Windows features on or off.
2) Local Group Policy Editor>Computer Configuration> Administrative Templates>Network>Lanman Workstation>Insecure guest logons (Set to Enable)
I hv solved with method 2) !
Method 2 work for me also , thank you very much
lol Your very Welcome :) @@lyhourchhay2981
Nice n easy,,, Thank you Zack Attack, problem solved.!
working fine thanks :) , BTW i spent many hours to find this solution
Been happily using a Raspberry Pi 3 setup with a 2TB portable SSD as a little NAS for the past 3 years.
Suddenly today it won't connect.
Getting the error you describe here.
Tried everything here, even unplugged and restarted everything.
Still nothing.
What next to try??
good video, just didn't work for me
thanks
Beautifully done, thank you for your help.
Mate! You saved me a few hours! God bless!
I followed the video and successfully copied everything on my WIndow's pro computer. I restarted. No luck, still have the same error code. I went over everything again, everything perfect as described in your video. It just didn't work.
I'm trying to connect to Huawei Mate 20 phone - It appears as a network drive like any other computer. Before I re-installed Windows, It connected fine
Finally, I looked at my Windows Firewall Control. Windows Explorer.exe fixed the problem. Woohoo.
Hello, I have tried according to your instructions, but the error message is still there. Is there anything I
need to be doing further? Plz, advise. Thanks for your video, it helped a lot.
I have this error code just for my HomeGroup which is not accessible from my second PC?
It worked Thanks a lot. Wish I saw your video first.
Some folks have fixed it [including myself] by going to
-> Control Panel
-> Programs and Features
-> Turn Windows Features Off or On
and assuring a check-mark is in "SMB 1.0/CIF"
but also un-checking the sub entry of "Automatic Removal."
Having that SMB 1.0 unchecked is a default of latter updates.
is this really work?
@@randompapawholovesfootball It worked for me on my windows 10. All I can say is follow the steps and try it out.
This worked for me on Win 10 Pro 1713, thanks for helping!
none of these procedures worked at all. Windows 10 still can't see my home server
Thanks a lot! simple solution for an annoying problem
Very good/clear explanations, but my problem was not solved - apparently (found out just now) it had to do with smb1 vs smb2. My NAS - WD from 2011 - apparently needed (the very old and unsafe) smb1.
I did everything in the video with no problems until the Map Network Drive box. I did not get the Enter Network Credentials box. The diagnostic still says error code 80070035. What do I do now? It simply says the device cannot connect.
Am still facing the same problem
Thank you so much for this video. Solved my issue with the Local Security Policy Authentication Level fix :)
Thank you so much, great advice you are the best
I changed policy to reject and it worked!
Thanks, it worked the first time after rebooting. Sadly, the second time I boot up the system the error is back...
Thanks I am know able to "see" my PI running Home Assistant again.
Thank you...
Resolved the problem...
thumbs up...
Thank you for your help. It solved my problem.
great help, it works every time.Thank you very much
Thank you so much. It's working with me as well.
Thanks a lot miracle! Worked within first time
Unfortunately for me, still can't access network computer. I followed all your steps mentioned in this video, still no luck. Same error code. Windows 10 21H1
I would like to mention that Error Code: 0x80070035 can also be caused by having a cross cable connecting the machines.
Guillermo Rexach you are actually a life saver, I was getting so frustrated
hey bro that worked for me & my housemate thanks you made my day
Thank you. I've started the TCP/IP netbios helper service and the problem is gone.
Still it's not working is there any way to resolve
same here
I had the same problem, tried everything, 10 hours later I found the problem. It was Zonealarm free firewall that caused it. Installed Eset security and it solved it.
You saved me at the end Thanks!
GOOD ! This is helpful for me . Really thank you .
Awesome well done fixed my problem and so easy to follow
Thank you. so much. Now I can see to other computer in my home network.
Just started having this issue recently on Windows 11, followed these steps and didn't fix it, still the same error code. Any updated fixes that I could do?
The other machine that I'm trying to access on my Network is able to access mine no problem.
Don't follow this video, just use credential manager, that regedit is destroy the operating system.
Please Brian can you next create the two videos I have asked for. First create the video that explains the difference between the .themepack & .deskthemepack file name extension. Then, create the second video explaining on how to fully create an Aero theme in Windows 7, and how to organize all the required items in a folder when creating custom wallpapers, colors, screensavers, cursors, sounds and icons. Thank you.
I will do when I get the time, I got a number of videos to do before I get to your video requests.
Thank you very much Brian for explaining to me in more details on your plan to create your own videos before doing mine. Many thanks.
It appears the developers at Microsoft simply do not understand how real people want to use their computers.
typical,doesnt work like any other tutorials smh :/
"0x80070035 network path not found"
Solution:
gpedit.msc > Computer Config > Administrative Templates > Network > Lanman Workstation > Enable insecure guest logons > Enable
try this that finally worked for me :)
@@Maldeus can confirm, this actually worked.
@@Maldeus You're the genius here . Thanks so much!
@@Maldeus holy crap. i love you. there needs to be more people like you in the world. it worked like a charm.
@@Maldeus THANK YOU SOOOO MUCH MAN I'VE SPENT DAYS WRACKING MY BRAIN OVER THIS!!!
Thank you! Works for me under Windows 10!
Which version your windows