YouAreHere
New Member
- Joined
- Oct 3, 2019
- Messages
- 5
- Thread Author
- #1
We have a printer which we connect to over wi-fi on our home network. I tried to install the printer via the Windows 10 Add a Printer or Scanner function. Windows 10 went through what looked like the normal printer installation process, however, Device Manager was showing an error against the printer saying the device could not be used because the drivers were unsigned. This is strange because Windows 10 installed the drivers on its own.
I looked at the Event Viewer logs at the time of the printer installation and the Security log showed something on the network tried to logon to the Windows 10 Guest account on two occasions.
---------------------------
An attempt was made to query the existence of a blank password for an account.
Target account name: Guest
---------------------------
An account failed to logon
Logon Type: 3
Security ID: NULL SID
Account Name: Guest
Failure reason: Account currently disabled
Caller process name: C:\Windows\System32\rundll32.exe
----------------------------
Based on the timing, I'm guessing it was the printer that was trying to access the computer Guest account. Is this expected behavior for a wi-fi printer to try and logon to a Guest account?
I looked at the Event Viewer logs at the time of the printer installation and the Security log showed something on the network tried to logon to the Windows 10 Guest account on two occasions.
---------------------------
An attempt was made to query the existence of a blank password for an account.
Target account name: Guest
---------------------------
An account failed to logon
Logon Type: 3
Security ID: NULL SID
Account Name: Guest
Failure reason: Account currently disabled
Caller process name: C:\Windows\System32\rundll32.exe
----------------------------
Based on the timing, I'm guessing it was the printer that was trying to access the computer Guest account. Is this expected behavior for a wi-fi printer to try and logon to a Guest account?