Windows 10: XP SP3 PC can't authenticate for shares on Windows 10 PC, SMB1 enabled

I just completed a fresh installation of Windows XP on an old laptop that I have. Service pack 3 has been installed and I can reach the internet without any issues. When I try to map a network drive to my Windows 10 computer (Version 20H2) I am told that the account is disabled. Yet if I try to do the same mapping from another Windows 10 computer it works without an issue. The username/password are good. SMB v1 has been installed on the Windows 10 machine. I have tried enabling insecure guest logons. I have a shared folder on the XP machine and the Windows 10 machine can see it without issues. What step am I missing to allow the XP machine to see the Windows 10 shares? [edit]I be dumb. It was a typo in the username/password on the XP machine.[/edit]

:)

 

Can't share files on desktop pc with laptop

Helllo @chermesh, *Smile

Since this is for sharing between a Windows 7 and Windows 10 PC, you may need to enable SMB1 on the Windows 10 PC if you haven't already from step 2 option 1 below in first link.

Share Files and Folders Over a Network in Windows 10

Enable or Disable SMB1 File Sharing Protocol in Windows

 

Windows 10 1803 and applications on SMB1 shares can't connect to anything

Talking Client side, since the server (2003) didn't change: SMB1 is not blocked, otherwise I wouldn't be even able to see the share. The issue is not that I can't see the share or open the files there, the issue is that if I run an exe from a SMB1 share
that exe won't be able to establish connections. If I run it from a SMB2/SMB3 share or from a local disk on my PC it all works as before.

I can't see an option like "Allow exe's on SMB1 shares to establish connections" in Windows Features, only Client and Server and, obviously, they are both ON. I tried disabling and restarting then re-enabling and restarting and it didn't resolve the issue.

I checked under monitoring, as you say: the "Advanced Options" link is grayed out, This is due to internal policies, and I received assuration that no changes were made to the policies, or to F-Secure, which is listed as the agent responsible for all the 3
networks listed and is controlled by a Policy: also F-Secure hasn't changed, since under the same policies and F-Secure settings we have both Windows 10 1709 PCs and Windows 10 1803 PCs and only the latter have the issue.

The only change one needs to have the issue, is to perform the 1803 WIndows 10 update

 

SMB1 disabled, SMB2 enabled; Can no longer access network shares

If you're system is up to date, there's no need to be concerned about Wannacry - as such there's no problem using SMB1 (despite all the comments about SMB1)

I had the same problem - no shares visible on File Explorer - researched the issues related to disabling SMB1 - and quite frankly, it's only SMB1 on XP machines that will be (would have been before MS released a patch for XP) susceptible to a Wannacry attach. I suggest you reinstate SMB1 and enjoy accessing your network shares as before

R