| Title: | Digital PATHWORKS 32 |
| Moderator: | SPELNK::curless |
| Created: | Fri Nov 01 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 337 |
| Total number of notes: | 1612 |
I have a large Pathworks client who is not able to get Pathworks 5.0E
to assure that passwords are SYNCHRONIZED between Domain and OVMS.
They are becoming very frustrated with continued attempts to make this
work reliably with a Lanman 2.1 on OVMS.
I have suggested they consider Pathworks32 with password assistant to
provide a single password and to sync security between apps on NT and
file access on OVMS.
1. Will this really provide password synchronization?
2. Will this synch really work on the OVMS server so that the
passwords remain?
3. Is there any other way to sync passwords for 500 desktops with a
requirement to run apps off WNT and file access to OVMS files?
If a user changes his password, it must be changed in both places.
Cheers,
Sandy
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 177.1 | VMSNET::S_VORE | Smile - Mickey's Watching! | Mon Mar 24 1997 07:36 | 11 | |
Password Assistand does NOTHING to synchronize passwords. It is a
"lockbox" on the PC which holds passwords that are then used in
aplications which can access that storage place - currently VT320 and
PowerTerm.
Perhaps you mean the SINGLE SIGNON feature available in OpenVMS (7.1?)
and PATHWORKS for OpenVMS 5.0E? This provides the capability for
OpenVMS to use a password that's authenticated in a different place -
an NT PDC for example.
| |||||
| 177.2 | REplicate passwords in lanman2 | SLOVAX::NEWMAN | Tue Mar 25 1997 17:17 | 30 | |
Yes, I am referring to replication of password changes within the
domain, where OVMS is in the same domain as WinNT.
It appears that since OVMS is lanman 2, that WinNT does not always
reliably replicate password changes made by an NT User to the OVMS
system causing the NT User to not be able to access files on the
OpenVMS System.
I guess Microsoft knows about this but is not going to fix it.
People should move to lanman 3 which isn't available on OVMS.
The other option is to move OVMS out of the domain. This would work ok
but feels like you are hiding from the problem and causes other issues
such as passwords must be entered to access shares on the OVMS system.
About 80% of the time you are ok but when you are not, you need to take
action to make this work.
If you change the OVMS system using NET ACCOUNTS to change the role,
sometimes you can get the passwords sync between systems.
Other times you cannot, and it appears that you cannot stop net logging
on one of the node in the cluster. Some steps are ok but painful to
users.
Any help would be appreciated.
Sandy
| |||||
| 177.3 | Try this ? (WELPCP is 16.183.48.114) | WOTVAX::16.194.208.3::warder.reo.dec.com::sharkeya | Who am I now ? | Tue Mar 25 1997 17:43 | 4 |
\\WELPCP\WINPASS Alan | |||||
| 177.4 | VMSNET::S_VORE | Smile - Mickey's Watching! | Wed Mar 26 1997 08:23 | 2 | |
and raise this question in the OpenVMS(LAN Manager) Server notesfile;
PATHWORKS 32 isn't involved in this topic at all.
| |||||