Unable to reach the Windows 10 SMB network folder from the Windows 10 desktop using Ethernet.
Unable to reach the Windows 10 SMB network folder from the Windows 10 desktop using Ethernet.
based on what i know, network shares through windows require all devices to run home OS, and the server should be from the same generation. i had problems with windows 10 but not with 7 until all my systems were 10. this might not work. https://learn.microsoft.com/en-us/troubl...file-share permission issues could stem from an OS mismatch.
I thought it through, but my server laptop runs Windows 10 Pro and my dad's W11 can connect to the network share through File Explorer’s Network menu when using WiFi. It seems Pro/Home isn’t the problem. How would I apply any of those Microsoft commands? Would it work for Windows 10 as well, if the listing mentions up to Windows 8.1? The Accesschk in CMD just keeps prompting for a valid command, no matter what you enter. I also don’t understand the phrases like “Verify that the NetApp Filer has the Synchronize bit set” or “A network trace can show the DesiredAccess error for SMB2 CREATE.” Those terms only give vague explanations online.
ok so the issue falls to firewall blocking or permissions on the host machine to the client. well since that is an smb v2 thing have you enabled it on the client? if not To enable SMBv2, you want to confirm your operating system can run it. Most Windows 10 operating systems can. Open the Powershell and type in Get-SmbServerConfiguration | Select EnableSMB2Protocol. You should receive a True in response, meaning you can run SMB2 on your computer. if so. Check firewall and permissions on host to client for read write access to the area that client is trying to create a folder.
The SMB configuration confirms SMB2 is enabled. The firewall remains unresponsive, suggesting a permissions issue. Access to shared folders appears dependent on wireless connection. Advanced sharing settings are hidden, making it hard to view who can access drives. Permissions in Advanced Sharing are set to Full Control, but password protection is off. The "not present or started" error persists when navigating via File Explorer. Adding the laptop to Advanced Sharing doesn’t resolve the login prompt. Consider using a CLI tool or script to audit drive permissions and verify access rights.