[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
Notice: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
Moderator: | CPEEDY::KENNEDY |
|
Created: | Fri Dec 18 1992 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4319 |
Total number of notes: | 18478 |
4126.0. "Remote (non-VMS) Authentication" by PHXSS1::MEAGHER (Cube with a view of the blues ..) Fri Jan 24 1997 20:58
Greetings -
My posting concerns a large customer who has a VAX running VMS 6.1,
TCP/IP 4.1, Pathworks 4.1. The answer to his question[s] may include
having to upgrade to Pathworks V5.X, so I'm trying to find an answer
from those knowledgeable at this Conference.
If there's another Pathworks Notesfile you'd recommend, I'm all ears.
Here's essentially the customer's question:
------------
Some of our mutual PC customers would like to mount to NFS exports on
the VAX, but Bill[1] is trying to find a way without the NFS admin
overhead.
Is it possible to use another PCNFS authentication server (UNIX) for
remote authentication and then allow the authenticated users to mount
exported volumes on the VAX? (That way, they could leverage their well
managed UNIX accounts and still get to volumes on the VAX).
Now, while we can mount Netbios shares via NTW[2], there are some
limitations due to the Pathworks version being so old.
If the remote authentication won't work, is there a LOCKD and PCNFSD
for the VAX that would take care of the exports? Is there a way to tie
in the Pathworks ID to NFS GID/UID parameters?
--------------
[1] a fictitious name ;>)
[2] not sure what this means, "NTW"
Thanks for your kind effort ...
Regards / Kent, Sales Support SBU
T.R | Title | User | Personal Name | Date | Lines
|
---|