| Thanks for your response Alan,
> There is an entry in LANMAN.INI on the server which tells the server what
> string to display (look in Appendix D of the sevrer admin guide). This may
> help (it may not).
I think you mean the srvcomment field? I can't believe netpass would check
this.
> Alternatively, use my WinPass program which does the same thing under
> Windows (\\WELPCP\WINPASS)
> \\16.183.48.114\WINPASS
This customer would rather not use other software to accomplish this.
According to the SPD it should work without WinPass.
The release notes explain how to set it up so I assume it has been tested and
found to work OK.
Does anyone have this working without WinPass?
Thanks,
Richard Walker.
Taken from 6.1 SPD:
LIMITED NIS PASSWORD PROPAGATION
Changes to users' network password initiated from a PATHWORKS LAN Man-
ager client can be propagated to both the users' associated UNIX ac-
count password and their NIS password.
Taken from 6.1 ECO2 release notes:
1.1.24 NETPASS Requirements
The following are guidelines and restrictions for using the
NETPASS command.
- The NETPASS command requires an activated guest account
on the server with a null password which is active (i.e. not
expired).
- The NETPASS command changes both a user's DIGITAL UNIX
and PATHWORKS Advanced Server password if the hostpasswordsync
keyword in the [lmxserver] section of the lanman.ini file to
is set to yes. The default value for this keyword is no.
- The NETPASS command, on DOS machines, works only when the
password is entered as a quoted string, or when you let the
NETPASS program prompt you for the old password. This is
because DOS automatically converts the old password to an
uppercase string, and DIGITAL UNIX is case sensitive.
To use NETPASS on DOS, you must use the following syntax:
NETPASS \\system_name user_name "oldpassword"
|