Windows 10: Win10 1909 KB5006667 breaks local user access to shared printers

We have quite a few systems on our campus running Windows 10 1909 that sign on to the system with a local account to the system.Once they sign in they then use the add printer option to map to a printer on our Windows printer server in order to print to a network printer.The issue is that when 2021-10 Security Update for Microsoft Windows KB5006667 is installed that process no longer works.1. Sign on to system with local account2. From the Start Button select Settings3. Select Devices then Printers & Scanners4. Click the +Add a printer or scanner5. Click the "The printer that I want isn'

:)

 

installing network printer on an Xp to use shared printer on win10

If you had problems with "credentials" trying to install a network printer on an Xp this solution will work, Does not involve credentials.

George

If you have problems trying to install a network printer on an Xp computer to the shared printer on Win10:

(the win10 is plugged directly into the computer!)

try this



Firstly

On the win10 computer indicate the share name then in the securities window list all the users that will be using this printer. These will be user codes and will verified by win10.

If you do not know the name of the win10 machine then do this now.

Summary:

Computer name

Printer share name

List of permitted users.



Secondly sign on to the xp computer with a user name that is mentioned in the securities list above.



Then proceed as follows:



1) click start then click printers and faxes

2) click add printer ( in left pane)

3) click next

4) select LOCAL printer attached to this computer: click next

5) Select create a new PORT. Select “local port” for the port type and click next.

6) System asks for port name: enter path and share name for example \\win10computername\printersharename
this is similar to mapping a network drive, instead of server, folder it is server printer share name.

7) Select printer brand and model number (for the driver)

8) Follow the rest of the wizard.

9) Do not share printer. Win10 will manage it

10) Print test page, print a simple document.

 

Cannot access shared network drive


Personally, I wouldnt use Everyone. If anyone hacks into you, they have full access to everything and can demolish everything on your raid. I would rather set up accounts and access separately for each person. That way, I know who did all that damage. In the end with a little extra work, I feel more secure by using Authenticated Users.


If this helps.
step 1 create non-microsoft account and without email and address without admin rights
step 2 share a drive or folder to specific user account (if Everyone is listed, remove it)
step 3 set security > add Authenticated Users (if more than 1 account) or add specific users
step 3a remove Everyone from list
step 3b uncheck full control and write for all items listed except SYSTEM and Admin account.
step 4 right click Start > Computer Management > System Tools > Shared Folders > Shares ... to verify settings and change anything else. You can also see the number of connections to each share here.

 

win10 printer credentials problem

Sean

1) On the host, everybody has access to this printer.

On the workstation nobody can get access to this printer.

On the host all known users including Everyone are given permissions to use this printer.

On the workstation I tried all users, no one could get access to this printer.

All of them could access drives/ folders in either direction.

To test your suggestion I signed on using same and different user codes : made no difference.

In fact I get the message about credentials even if I set the host printer as NOT being shared.

( A lot of these warnings are reminiscent of systems using domains but this is supposed to be a peer to peer system)

Logically, I do want the same user to be able to share drives and printers.

By the way, using the same user code, password, and work group name is the easiest way to setup file sharing between Win10 and XP

Thanks for the suggestions. If you or any one has more suggestions I will try them

George

I