[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference lassie::ucx

Title:DEC TCP/IP Services for OpenVMS
Notice:Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System
Moderator:ucxaxp.ucx.lkg.dec.com::TIBBERT
Created:Thu Nov 17 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5568
Total number of notes:21492

5069.0. "Directory exporting on OVMS 6.2 for UCX 3.2 " by XKOV01::BIPLAB () Sun Dec 29 1996 05:20

T.RTitleUserPersonal
Name
DateLines
5069.1here are the stepsBACHUS::ROELANDTSWa d'es ma da ve ne stuutSun Dec 29 1996 08:3526
5069.2PCNFS mapping problem.XKOV01::BIPLABMon Dec 30 1996 10:0342
5069.3UTRTSC::KNOPPERSOswald KnoppersMon Dec 30 1996 10:1314
5069.4LASSIE::CORENZWITstuck in postcrypt queueMon Dec 30 1996 10:504
5069.5DRHOOK::TONYTue Jan 14 1997 09:1017
5069.6UTRTSC::KNOPPERSOswald KnoppersTue Jan 14 1997 09:514
5069.7DRHOOK::TONYTue Jan 14 1997 10:315
5069.8win 95 connecting to OVMS ucx nfs exprXKOV01::BIPLABMon Feb 03 1997 09:1141
    Hi Tony,
    
    I think I should let you all know the solution for the problem I was
    facing. I was trying to connect Win95 client having Hummingbird PC-NFS
    loaded to connect to OVMs v6.2 with UCX 3.2 NFS exported directories.
    
    The following things are to be done -
    
    1.Upgrade UCX 3.2 to 4.0.
    
    2. For adding vms style exports
    
    ucx> set config map "/VMSDiskName" VMSDiskName
    ucx> map "VMSDiskname" VMSDiskName
    ucx> add export "VMSDiskName" /Host=*    # for all hosts to connect
    					       from any where
    for adding host
    
    ucx> set host "host name"/address=IP Address  # host name is to be
    						    maintained as of the
    						    client names are.
    add proxy
    
    ucx> add proxy vmsusername /uid= /gid=  /host=* # the uid & gid should
    	                                              be as of the VMS user
                                                      uic
    
    ucx> add proxy system/uid=0/gid=1/host=*
    
    Then browse the network from the Windows Explorer or Windows network
    Neighbourhood and connecte to the respective directories ( i.e
    sys$login directory, don't forget to give 
     world: read;write;execute;delete permission to the sys$login directory
    of the respective users.)
    
    Anyone is free to correct me if I am missing some thing on the security
    front.
    
    Biplab