I’m having a problem with accounts that one of my OD client machines will not authenticate accounts if the password looks like **** ***** but will work if it actually has an encrypted password. I have 2 other client machines that are connected to the same OD server and have no problems authenticating the accounts with **** as their password. Could someone please point me in the right direction of solving this issue? I’m stumped. Examples of accounts are below. Thanks in advance!
example of account that does work:
Dictionary: “D-0x00321e00”
_lookup_agent: DSAgent
_lookup_validation: 1124889345
gid: 1027
home: /web/other/ipu
name: ipu IPU
passwd: {CRYPT}gRAhY0VmZlFCg gRAhY0VmZlFCg
realname: IPU
shell: /bin/tcsh
uid: 119
+ Category: user
+ Time to live: 0
+ Age: 0 (expires in 0 seconds)
+ Negative: No
+ Cache hits: 0
+ Retain count: 2
example of account that doesn’t work:
Dictionary: “D-0x003205b0”
_lookup_agent: DSAgent
_lookup_validation: 1124889345
gid: 20
home: /web
name: staff staff
passwd: {CRYPT}******** ********
realname: staff
shell: /bin/tcsh
uid: 1026
+ Category: user
+ Time to live: 0
+ Age: 0 (expires in 0 seconds)
+ Negative: No
+ Cache hits: 0
+ Retain count: 2