Windows 10: Pwd asked after mapping on Windows 10 (to access to smb linux share)

Hi,

I use SMB 1 to share folder to a school, when I was on Windows 7 the share worked perfectly (when the computer startup the mapping was operating and after that we accessed to all the shared folder directly), but now that I use Windows 10 (first I've to enable SMB 1) it ask login and password to access to shared folder (at least 1 time after the startup).
I have no idea why I have this problem.

Thanks you ! *Smile

:)

 

Problem connecting to SMB Share on Linux server with Windows 10

Hello All,

Recently my Windows 10 laptop no longer sees the SMB shares on my Unraid 6 server, everything was working fine until a week or so ago. Other Windows 7 machines on the same network have no problem seeing or connecting to the same SMB shares. I did some searching
on the Web and it was suggested that you try to sign into the computer with a local account rather than a Microsoft account but that did not help. I also tried the registry edit suggested in this post:

https://www.schkerke.com/wps/2015/06/windows-10-unable-to-connect-to-samba-shares/

This did not help either, I am currently running Windows 10 Home 64 bit on an Asus UX305LB laptop and my last update was KB3093266, I believe I was able to connect to the SMB shares for a while after the update. It's pretty important that I be able to connect
to the server as I use it to backup the computer, thanks in advance.

 

SMB file servers keep asking for credentials

I have both Windows 10 SMB and Linux Samba file servers. The share permissions are:

• browsable (Linux) / turn on file and printer sharing (Windows)
  
• guest ok (Linux) / turn off password protected sharing (Windows)
• Appropriate file system level permissions on both servers (not really matters here)

Most of the time, using a Windows 10 client to connect to the shared folder is straight forward, just \\my-server and
it is fine. But sometimes, it keep asking for credentials for unknown reason.





It won't connect if I leave all fields blank. Sometimes I need to type a random user account with a blank password, and sometimes both a random account plus a random password to pass that stupid prompt. Linux
clients do not suffer from that issue, at least by using smb://my-server on Ubuntu's Nautilus and select Connect anonymously.

To make the problem worse, let's say I have a shared printer on the server. After a client provides a random user + password, he can connect to the server and use the shared printer. After a few days, he suddenly
cannot print using the previously added printer, until he tries to connect and provides a random user + password again (the printer does not need to be re-added). Looks like the junk user + password time out after a few days (even if you do check Remember
my credentials).

The issue occurs randomly. What could be the cause of the problem?

 

problem accessing smb shares from windows 10

With network discovery on, my ubuntu machine is found (named kodi).

If I check on kodi in the network section of file explorer, it shows my shares.

If I doubleclick on one of the shares, a slow green line crosses the top of the screen and eventually gives the 0x800704cf

If I dont touch this popup, then I can access the share normally.

If I cancel or diagnose (which finds nothing) it is not available.

However if I enter \\ip-address at the top of file explorer it finds the shares and they are immediately accessible.

Also if I turn network discovery off, and type \\kodi at the top of file explorer, it works just like using the IP address

I figure this has something to do with dns, but cannot get network discovery to work properly

Does anyone have any ideas on this? Its only been an issue since the upgrade to windows 10.

Method 1: Run the Network Adapter troubleshooter and check if it helps.

Follow the below steps:

• Type troubleshooting in the search bar.
• Select Troubleshooting.
• Select View all on the top left corner.
• Click on Network Adapter.
• Follow the on-screen instructions to run the troubleshooter.

The issue persists following method 1.

Method 2: Update driver manually.

I suggest you to update the Graphic driver from the Device Manager and check if it works.

Follow the below steps:

• Right click on Start button and click on Device Manager.
• Extend Network adapters driver from the list.
• Right click on the Network driver and click on Update driver Software.

Method 2 shows that the driver is up to date.