New Laptop. NAS showing in File Explorer, but access denied

NEWBIE seeking help
I recently purchased a new laptop and during set up stage I answered yes to copy across windows settings from previous PC. All seemed OK , BUT!

The connection for a NAS (Mirodin5) was copied across. This can be seen in windows file explorer as show in screenshot below.


The mapping for folders on that NAS were not copied.

When I click on ‘Mirodin5” I get a message that Windows “cannot access \\Mirodin5” Right clicking on Mirodin5 does NOT bring up option to delete the entry
Using CMD and net use brings no help as that (also screen shot below) does not show any network connection for Mirodin5


I am at a loss on how to resolve this issue. I do want to set up connections to the NAS folders.

Incidentally I did have an issue accessing the NSA drives on the pervious PC. That was resolved by deleting the credentials managers entry for Mirodin5.

There are not any entries in credentials manage on the new laptop.

Kind Regards
Bruce

Hi Bruce,

Might this article apply to your dilemma?

NAS with SMB in Windows 11 24H2 may fail

Kind regards,

tecknot

Here's what I finally ended up doing for all my 24H2 and 25H2 machines so they could see my NAS and the Windows 10 machines.

In Control Panel\All Control Panel Items\Programs and Features\Turn Windows Features on or off.
Check if there are No Ticks are on SMB 1.0/CIFS Client and SMB 1.0/CIFS Server Only a tick on SMB Direct

Make Sure you are on a Private Network NOT Public

Next go into Group Policy (Pro Version Only) gpedit.msc

Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options
Double click on Microsoft Network Client: Digitally sign communications (always)
Double click on Microsoft Network Client: Digitally sign communications (if server agrees)
Set both of these to "Disabled"
Click on OK.

Computer Configuration, Administrative Templates, Network, Lanman Workstation
Double click on "Enable Insecure Guest Logons"
Set this to "Enabled"
Click on OK.

Reboot

Dear tecknot, & gunrunnerjohn,
Thank you for taking the time to reply to me, it is truly appreciated. I learnt a great deal from the feedback from both of you and managed to solve the issue, using the advice in link that tecknot provided.

Excellent!

Kind regards,

tecknot