Solved New computer can't see my shared drives

Just got a new laptop and am in the process of getting it set up. I am finding that I cannot connect to the USB drives on my Nighthawk router. My old laptop attaches with no issues and as far as I can tell I have my network set up the same as the old one (my system 1, haven't added the new one yet). Both machines are running Win 11 Pro. Any ideas campesr?

A router‑shared USB drive is almost always exposed using SMB1
Try enabling SMB 1.0/Cifs Client
Control Panel → Programs & Features → Turn Windows features on or off → check: SMB 1.0/CIFS Client
Reboot afterward.

glasskuter said:

A router‑shared USB drive is almost always exposed using SMB1
Try enabling SMB 1.0/Cifs Client
Control Panel → Programs & Features → Turn Windows features on or off → check: SMB 1.0/CIFS Client
Reboot afterward.

Click to expand...

That was actually one of the first things I looked at, but no dice.

To fix the "your organization's security policies block unauthenticated guest access" error in Windows 11, enable insecure guest logons via Group Policy or Registry Editor. This occurs because Windows 11 blocks insecure SMBv2/v3 guest access to protected network shares. Note: This reduces security.
Method 1: Use Group Policy Editor (Recommended)

Press Windows + R, type gpedit.msc, and hit Enter.
Navigate to: Computer Configuration > Administrative Templates > Network > Lanman Workstation.
Double-click Enable insecure guest logons and set it to Enabled.
Click Apply/OK and restart your computer.

Press Windows + R, type regedit, and hit Enter.
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.
Right-click in the right pane, select New > DWORD (32-bit) Value.
Name it AllowInsecureGuestAuth and set its value to 1.
Restart your computer.

Method 3: Use PowerShell

Open PowerShell as Administrator.
Run: Set-SmbClientConfiguration -EnableInsecureGuestLogons $true.

FreeBooter said:

Method 3: Use PowerShell

Open PowerShell as Administrator.
Run: Set-SmbClientConfiguration -EnableInsecureGuestLogons $true.

Click to expand...

This got me to the next step where I got this error.



I then Googled this up, and it finished the job. All is working now!

We are glad to hear your issue has been resolved, thank you for letting us know that all is now well!