Bulldog13
Golden Member
I have about 10 users who use an application via terminal services on windows 2k.
Basically, the users remote desktop into a server and run the application. Terminal Services then creates an instance of whatever printers are mapped to lpt ports on the user's pc.
The problem is the printer in question (Ricoh Aficio 1035) is passworded. Normally, for printing non-terminally served apps (word excel blah blah) I login with the user's name and just set the password a few screens into the printer properties. That works great.
Unfortunately, when doing it with terminally served apps, the password does not *stick*. Even after I set it in the printer instance on the server, logged in as that user, after a few days the password must be input again. This is a too much for the users.
I know it is a long shot, but does anyone have any idea on how to make it stick ?
Basically, the users remote desktop into a server and run the application. Terminal Services then creates an instance of whatever printers are mapped to lpt ports on the user's pc.
The problem is the printer in question (Ricoh Aficio 1035) is passworded. Normally, for printing non-terminally served apps (word excel blah blah) I login with the user's name and just set the password a few screens into the printer properties. That works great.
Unfortunately, when doing it with terminally served apps, the password does not *stick*. Even after I set it in the printer instance on the server, logged in as that user, after a few days the password must be input again. This is a too much for the users.
I know it is a long shot, but does anyone have any idea on how to make it stick ?
