Windows 10: Do SMB 2 and 3 REQUIRE that the target networked PC have a logon password?

If your devices are connecting to each other with SMB 2 or 3, is it REQUIRED that the initiating and/or target device in each instance have a logon password? Or can SMB 2 or 3 be set to connect and drop and get files between an initiating device and a target PC if both including the target PC log on on WITHOUT a password?


My Win 10 Pro 64-bit PC version 1909 logs on WITHOUT a logon password. It's my home machine, and no, I don't want a logon password, so don't bug me about it.


My new HP OfficeJet 9015 printer CANNOT "Scan to Network Folder" onto a shared network folder on my Win 10 PC using SMB 2 and 3 UNLESS I add a logon password to the Win 10 PC. In order to get the 9015 printer to "Scan to Network Folder"without the PC having a logon password, I must enable SMB 1 on both the PC and the 9015 printer AND restrict the printer to using ONLY SMB 1.


The 9015 printer itself does not have any user name password of which I am aware - it has only an IP address on my home LAN. But the issue is that myWin 10 PC does NOT have a logon password for my user account. By the way, my user account on the Win 10 PC is an Administrators account.


See my detailed post about this at < THIS MS ANSWER THREAD >


So, for each of SMB 2 nd 3 separately, what are the rules about communication with a Win 10 PC that does NOT log on with a password?


WARNING - "independent Advisors" should NOT post here unless they have the precise answer to my question. If you post the usual generic nonsense, I shall report you to the Moderator and ask that you be banned. You'd better re-read my post here first.


Thanks.

:)

 

Windows 10 logon requires 2 separate logons

It would be quite a deliberate "accident" to set a BIOS password because you actually need to get into BIOS to set it! Removing it requires the same steps: Get into the BIOS, then clear the password.

If you do not remember the BIOS password then there are two options:

• If this is a desktop PC then you need to open the case and remove the shiny button cell battery from the motherboard for 10 minutes. This will clear the BIOS password.
• If this is a laptop then you need to return it to the distributor.

 

Mapped network drives do not connect at logon in vista with automatic logon enabled

I have vista x64 . I have some mapped network drives . They get connected when i enter the password at logon screen. Now i enabled automatic logon in vista and they do not connect anymore . I have to double click on them and enter the password manually .

Windows displays the message "Could not connect to all drives" at logon .

They used to connect automatically in xo with automatic logon enabled.

My logon password is the same as the administrator password with which i can connect to these drives .

 

2 of 3 computers in home network only show multimedia devices

Hi

OK I understand now, This is not an issue with devices appearing as media devices, it is an issue where devices are simply not appearing in the network list.

Where do you get the "access denied, contact your network manager"?

I would suggest updating to 1809 - 17763.253
Just to ensure that you are at the latest release and updates installed.

As you will have found, there are many posts about this issue and unfortunately there are many proposed resolutions. Enabling SMB 1.0 and the Services listed below normally resolves the issue.

• Function Discovery Provider Host - Automatic
• Function Discovery Resource Publication - Automatic
• DNS Client - Automatic
• SSDP Discovery - Automatic
• UPnP Device Host - Automatic

Older and non compatible devices need SMB 1.0 to be visible on the network and this would need to be enabled on all devices as well not just the PC you are describing.

To recap....

Can you see all devices in network devices as you would expect on the other PCs/Laptops?
Can you ping the devices by IP and by Name? Can you access the PCs via command line \\PCName\Share
------
If you have ensured SMB 1.0 is enabled, SMB Direct, as per the image image below






Then I can only suggest corrupt registry settings.
try running sfc /scannow from an admin command prompt to check for any integrity violations.

then try and force the settings again, try clearing the the SMB 1.0 and SMB Direct settings completely and restarting, then select them as per the image above followed by a restart.


Please post back with updates