Microsoft seems to be having to deal with issues related to printers for a while now. Reed more here:
Windows July update breaks printing and scanning when using smart-cards - Neowin
Microsoft seems to be having to deal with issues related to printers for a while now. Reed more here:
Windows July update breaks printing and scanning when using smart-cards - Neowin
A tree is known by its fruit, a man by his deeds. A good deed is never lost, he who sows courtesy, reaps friendship, and he who plants kindness gathers love.
Blessed are they who can laugh at themselves, for they shall never cease to be amused.
I don't reply to private messages from end users.
Outside of military and government, there hasn't been a wide adoption of smart cards, and even in those arenas, it's at the workstation level as opposed to the printer level that the card is required. Kerberos has caused all sorts of strange issues in the past since it's incredibly sensitive in terms of time and the ciphers it can negotiate.
I had a computer that wouldn't authenticate to the domain it was on even though the object was fine. It turned out that the time zone was set for Pacific Time, but the time itself was manually set to Eastern Time so instead of an expected three hour time zone offset, the network saw a time in the future (example: Eastern Time is 4.00 PM, 1.00 PM Pacific. The way the computer was set, the network saw a time of 4.00 PM Pacific time, or 7.00 PM Eastern time, which would be in the future).
Ricoh did make a reader for CAC/PIVAuth, CAC Common Access Card. They also had an online training course on how tho install and configure it. When I was in the Army Reserves, the only association the CAC had with printing was that you had to use it to log in to one of the unit's computers in order to print from that computer.
Common problem when new techs do not know how to properly set the time zone.
I had a computer that wouldn't authenticate to the domain it was on even though the object was fine. It turned out that the time zone was set for Pacific Time, but the time itself was manually set to Eastern Time so instead of an expected three hour time zone offset, the network saw a time in the future (example: Eastern Time is 4.00 PM, 1.00 PM Pacific. The way the computer was set, the network saw a time of 4.00 PM Pacific time, or 7.00 PM Eastern time, which would be in the future).
Its a bot.
Btw, this one also:
Toshiba, will they survive?
Last edited by tsbservice; 09-09-2021 at 08:12 AM.
A tree is known by its fruit, a man by his deeds. A good deed is never lost, he who sows courtesy, reaps friendship, and he who plants kindness gathers love.
Blessed are they who can laugh at themselves, for they shall never cease to be amused.
I don't reply to private messages from end users.
Bookmarks