Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, January 11, 2018 9:23 AM
Hi,
We are unable to access a share folder in win 10 Machine but in win7 we can access.
The share folder is created in our Japan office and we are accessing it from india. It is strange because same folder we can access from win 7 PC without any issue but in windows 10 it showing below error
" windows cannot access \XXXX\ABC$ check the spelling of the name. Otherwise , there might be a problem with your network. To try to identify and resolve network problem, click diagnose
I have already tried below steps but no luck
1) reprofiling (deleted the user profile and recreated)
2) Updated the windows with latest update
3) Disabled the firewall and removed the antivirus
Please help me how to resolve this issue.
Thanks
Rakesh Kumar
All replies (7)
Friday, January 12, 2018 8:34 AM ✅Answered
Hi,
I consider that you could disable the security software (Norton) to check firstly.
The issue always be related to SMB and the Master Browser NetBios is again not functioning correctly. Few steps you could try.
disabled File and Printer Sharing and enable it again to check.
If smb1 is turned off in Windows Features, it removes the Computer Browser service. Open it in Windows Feature.
Launch Powershell as administrator.
Type "Set-SmbServerConfiguration -EnableSMB1Protocol $true" and hit enter.
Hope it will be helpful to you
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, February 21, 2018 6:53 AM ✅Answered
Hi Carl,
Thanks for your support.!
Yes it was smb issue after disabling smb 3.0 in win 10 pc we can access our share folder.
Thanks
Rakesh Kumar
Sunday, January 28, 2018 11:01 AM
Hi,
Haven't received your message a few days, was your issue resolved?
I am proposing previous helpful replies as "Answered". Please feel free to try it and let me know the result. If the reply is helpful, please remember to mark it as answer which can help other community members who have same questions and find the helpful reply quickly.
Best regards,
Carl
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, September 17, 2018 9:55 AM | 1 vote
I have the same issue on a brand new Surface....
this is the result:
Set-SmbServerConfiguration -EnableSMB1Protocol $true
Confirm
Are you sure you want to perform this action?
Performing operation 'Modify' on Target 'SMB Server Configuration'.
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): Y
Set-SmbServerConfiguration : The specified service does not exist.
At line:1 char:1
- Set-SmbServerConfiguration -EnableSMB1Protocol $true
-
+ CategoryInfo : NotSpecified: (MSFT_SmbServerConfiguration:ROOT/Microsoft/...erConfiguration) [Set-SmbSe
rverConfiguration], CimException
+ FullyQualifiedErrorId : Windows System Error 1243,Set-SmbServerConfiguration
Whats the better way to add a networkdrive today?
How is it inteded to be?
Change Serverside way of shareing? What to do on the Client?
Monday, July 15, 2019 11:40 AM
Hi
based on your reply i assume you have knowledge on this topic. I have shared a folder with my raspbeery pie which is running Raspberian Os. Now my problem is i can not find it on my network with my windows 10 laptop however i am able to find and access it using my android phone.
I have already:
Disabled my firewall and anti-virus
Monday, July 15, 2019 2:09 PM
Hello Daniel,
An issue exists with older paths and sharing from Windows to Windows it seems to specifically use SMB 1 which is disabled by default in new versions of Windows 10.
If you go to appwiz.cpl select to add/remove windows features then enable the check box against SMB1 and restart the computer, once restarted can you then test to see if you can access the shared folder.
All Windows shares that I can see use SMB1 and can't be forced to use 2 or 3 even though it would actually make sense given MS are blocking SMB1 and for good reason too.
It really does seem like an oversight from MS to disable the feature which then prevents Windows shares and a lot of network storage stop running.
Most storage vendors are updating if they haven't already to use SMB2 or SMB3 if not both, now if MS are blocking SMB1 in Win 10 1709 onwards surely they should change what protocol is used by Windows to either SMB2 or SMB3 for the Windows shares \hostname\c$ for instance uses SMB1 which is blocked out of the box.
Kind regards,
Jamie
Thursday, August 15, 2019 11:03 AM
Just an additional update
Through further testing I have seen the SMB1 Windows share was an issue on my site, this seemed to be forcing it to use SMB1 all new builds are bypassing this problem and can talk to other machines without that being setup.
Bu tI would be vary warey of running SMB 1 in place of SMB 2 or 3 or alongside of them due ot issues with security and potential for MITM attacks to take place.