What version of the client do you have deployed? Current is 6.25, though I've had success with older versions with Win11 24H2 though with OES client also involved.

Are users connecting with the OES client at all?

If they put in their credentials they can print, but eventually all the printers go away too. This is specifically with 23H4. Eventually it just all breaks on old cleints and ther newest client. If I roll windows back to 23H2 Everything works PERFECTLY again.

Are their credentials for iPrint the same as their local windows?

is iPrint checking those same credentials as for the Windows login (such as AD) if so, make sure that iPrint appliance is still actually talking with that credential store, and that there aren't any issues happening, such as it taking long enough that it now times out.  There are a number of things that the new Windows turned on by default that are tripping things up.  you might need to open a support case for further drilling in.

Yes they are, we sync from AD to the iPrint server, and we also have iCM integrated with AD as per the documentaiton and have for years. I imagine many of you will run into this soon, but we were on the cutting edge of the update. I am hoping someone else sees it so a fix can happen.right now I cannot go to 24H2 with this issues, and remain on 23H2 where everything is working.....

If you are in a position to open a Service Case, please do as that is the best way to make sure OT knows about the issue, and may even have a fix in need of testing with you.   Remembering that our southern neighbours are likely still in their Turkey coma since they get to their Thanks Giving a month after ours ;)

Sadly I have an education volume license with no access to SRs.....

Thought that might be the case.  So we need to find someone else who is hitting it or can reproduce it some way.  None of my clients have hit it yet, even those I know are running 24H2, so there is another factor in there. OES client use without any AD around may avoid the issue. 
I would still health check the iPrint appliance to make sure the sync with AD is working without errors, could be a partial error condition that it normally works around, but that 24H2 has tighter expectations that trips over it.

Hi Mathew

I currently do not have this version of windows but i can try to find out what the problem is as it looks like that Microsoft has changed something in the authentication framework on this windows version. But i need clear answers to my questions:

1. Is the OES client installed? if it is, i is version 24.4? if not, -please install it

2. Is iPrint client version 6.25? if not please install it

3. Enable IPPtrace on workstation. 

Open a Command prompt in "Run as Administrator" mode and type:

IPRNTCFG TRACE

Check the "Enable iPrint Trace" option. Click OK.
At a Command prompt, type

NET STOP SPOOLER
NET START SPOOLER

iprntctl TRAY_ICON

4. Try to print to make the credential screen to appear. Do not enter anything. While screen is on top, go to the iPrint client icon, properties, password tab and see if the correct credentials are listed.

4a. If not, enter credential on the screen, let print and when finish check again if credentials are now visible on iPrint icon

4b. If they're, close the authentication screen without entering nay credentials, delete the credential from the password tab and close the iprint client icon. Then at the command prompt type:

iprntcmd -S <iPrintAppliance IP Address>.

like:

iprntcmd -S 10.10.10.10

5. Reboot Pc and try it again. Is the authentication screen still coming? if yes, check the tray icon, password tab if correct credentials are there.

Then zip the c:/ndps directory and export the windows event viewer  logs for system and application. Named the file gonzalo.zip and upload it to ftp://ftp.novell.com/incoming and let me know when it is there and at what day and time you did this test.

Thanks

1. Is the OES client installed? if it is, i is version 24.4? if not, -please install it

No, this is the appliance and we have NO oes in our environment, nor will we ever again. We are passing authentication from the Active directory windows client, via iCM to the iprint client. has worked perfectly for about 7+ years until Windows 24H2

2. Is iPrint client version 6.25? if not please install it

Yes, tried lower, and this client. Currently 6.25 is installed.

3. Enable IPPtrace on workstation. 

Open a Command prompt in "Run as Administrator" mode and type:

IPRNTCFG TRACE

Check the "Enable iPrint Trace" option. Click OK.
At a Command prompt, type

NET STOP SPOOLER
NET START SPOOLER

iprntctl TRAY_ICON

(I will do this when I get a free moment)

4. Try to print to make the credential screen to appear. Do not enter anything. While screen is on top, go to the iPrint client icon, properties, password tab and see if the correct credentials are listed.

No problem to do this at all, as soon as the workstation is 24H2 the credentials screen will ALWAYS come up. I will report back on this.

4a. If not, enter credential on the screen, let print and when finish check again if credentials are now visible on iPrint icon

This works for a short time, and then breaks on reboot, this is not a dependable way to print from the iPrint client on Windows 24H2....sadly. So its not a good work around.

4b. If they're, close the authentication screen without entering nay credentials, delete the credential from the password tab and close the iprint client icon. Then at the command prompt type:

iprntcmd -S <iPrintAppliance IP Address>.

like:

iprntcmd -S 10.10.10.10

Okay, I Can try that......

5. Reboot Pc and try it again. Is the authentication screen still coming? if yes, check the tray icon, password tab if correct credentials are there.

From what I can see, the credentials are never passed from Windows Authentication and iCM again, once can put it in manually and but it will not work dependably. iCM is NOT passing the credentials from the WIndows Authentication screen any more. If no credentials are entered, the iprint client iwll just ask for them forever.

Then zip the c:/ndps directory and export the windows event viewer  logs for system and application. Named the file gonzalo.zip and upload it to ftp://ftp.novell.com/incoming and let me know when it is there and at what day and time you did this test.

Okay, I will do this test today and pass you the results, please hang tight.

Hi Matthew

It seems that with latest Windows update, the EnableMPRNotifications policy is disabled by default which may be causing this issue.

We need to enable this policy so that we can get the necessary windows password for seamless login.

Request you to enable this policy using gpedit

or you can create/edit an entry in registry

of type DWORD "EnableMPRNotifications"

under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Set the values as 1

Request you try this and let us know if it helps.

Thanks