Windows 10: Samba Share/ Legacy Drive Mapping not staying Connected

Hello All, I have an issue where we need to map a network drive to Windows 10/11 Pro Laptops. For the Windows 10 Pro laptops, I can successfully Map the Drive letter Q: to the machine useing a net use cmd script as such. net use Q: \\192.xxx.xx.x\etc\etc /user:uname pw /persistent:Yes and it works. When I restart the PC the connection fails. The Server Share I'm connecting to is old and we will be upgrading it but for now its a Unbuntu 16. something server and Samba Share. Any ideas on how I can get the drive to reconnect on reboot? Also I will add I've configered a standard policy for the dev

:)

 

Windows 10 Pro no longer connects to Samba Share on Linux Workstation

Hello Simon,

To better assist you, kindly provide the following information:

• What version of Samba Share are you using?
• What troubleshooting steps have your done so far?

We look forward to your response.

Thank you.

 

Connecting NAS - mapping of drives

Ok,

If you want, we can do a step by step troubleshooting of your current situation:

If you are able to ping your Machine and it responds.
Code:

Try to view if your NAS appears on the Network List:
Code:

If Your NAS appears on the list, try to view it:
Code:

The available shares will be listed there.

Then Try to List the content of one of the directories:
Code:

This should list the content of the directory,

If all this works Try to map a drive on one share:
Code:

Pls reply with the "response" of the first "encounter" of a non positive output.

This exercise should reveal if you have a Network or Protocol or Cipher or Authentication problem.

 

Connecting NAS - mapping of drives

OK ... step by step all worked.
I have now mapped the 2 volumes as Y & Z and can access the files on them

Any idea why the Command line would work yet the Easy Find Utility that has worked for years does not ?