

Cadet 2nd Class
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-11-17
16:41
733 views
Strange problem iPrint Client Mac
Hi,
I have a strange problem with user accounts. The user in question connects to a Windows PC and can print to an iPrint printer normally. But when it connects to a Mac, it is not able to print. The iPrint client does not even allow it to authenticate itself. Yet I have other users for whom they all work normally. I looked at the account configs, but I did not find anything.
Could someone give me a solution track?
Version iPrint Client : 6.03.00
Mac Version : 10.11.6 El Captain
Thanks.
I have a strange problem with user accounts. The user in question connects to a Windows PC and can print to an iPrint printer normally. But when it connects to a Mac, it is not able to print. The iPrint client does not even allow it to authenticate itself. Yet I have other users for whom they all work normally. I looked at the account configs, but I did not find anything.
Could someone give me a solution track?
Version iPrint Client : 6.03.00
Mac Version : 10.11.6 El Captain
Thanks.
1 Reply
roehmdo1

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-11-18
00:59
2 things to check :
1) Case Sensitivity of password....sometimes the novell client ignores the case sensitivity and allows authentication regardless of case... where as the mac is using ldap which does not ignore case
2) Make sure the problem user(s) have a attribute in their edirectory account called uniqueID.. I had a similar issue a few years back with a few accounts that were created a long time ago with nwadmin...which did not create this field on account creation
1) Case Sensitivity of password....sometimes the novell client ignores the case sensitivity and allows authentication regardless of case... where as the mac is using ldap which does not ignore case
2) Make sure the problem user(s) have a attribute in their edirectory account called uniqueID.. I had a similar issue a few years back with a few accounts that were created a long time ago with nwadmin...which did not create this field on account creation