| View previous topic :: View next topic |
| Author |
Message |
equaeghe
l33t
Joined: 22 Feb 2005
Posts: 637
|
 Posted: Mon Nov 30, 2015 10:22 am Post subject: [solved] Cannot print to password-protected print server |
 |
|
I want to print to a print server (smb, but https access is also possible) that requires a specific username and password to work. The username is different from my (computer) login.
I have configured the printer through CUPS and it is recognized.
I have tried both
| Code: | | smb://username:password@url/for/server/queue |
pre-setting authentication data, and
| Code: | | smb://url/for/server/queue |
having OS present an authentication dialog, but this only pops up an authentication window when printing from chromium; printing from KDE applications does not pop up an authentication window.
In both cases, I get an error:
| Code: | | Session setup failed: NT_STATUS_LOGON_FAILURE |
So it seems clear something is wrong with the authentication.
What should I do?
My preferred setup would be to have kwallet store the authentication info. If that is not possible, it is acceptable to have the authentication info in CUPS configuration files (which are not user-readable).
Last edited by equaeghe on Thu Dec 03, 2015 11:03 am; edited 1 time in total |
|
| Back to top |
|
 |
equaeghe
l33t
Joined: 22 Feb 2005
Posts: 637
|
| Posted: Thu Dec 03, 2015 11:03 am Post subject: Re: Cannot print to password-protected print server |
|
|
| equaeghe wrote: | | Code: | | smb://username:password@url/for/server/queue |
| Code: | | Session setup failed: NT_STATUS_LOGON_FAILURE |
|
It had to be | Code: | | smb://DOMAIN/username:password@url/for/server/queue |
I urlencoded DOMAIN/username and password to avoid trouble with 'difficult' characters (so the / after DOMAIN got replaced by %2F)
| equaeghe wrote: | | My preferred setup would be to have kwallet store the authentication info. If that is not possible, it is acceptable to have the authentication info in CUPS configuration files (which are not user-readable). |
This would still be nice; i.e., more secure than putting the password in the config file. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
