 |
The Question is:
I have just installed Open-VMS on a VAX4200 and have configured it identically
to a 3900 with
Digital TCP/IP Services for OpenVMS VAX Version V4.2 - ECO 3
on a VAX 4000-200 running OpenVMS V7.1
Telnet, nfs, rlogin are working fine. I can FTP from the 4200 to the 3900 ok,
but when I FTP
from the 3900 to the 4200 I get the following errors on the 4200.
SYSTEM>ftp waib20
%%%%%%%%%%% OPCOM 14-AUG-2000 15:48:25.43 %%%%%%%%%%%
Message from user INTERnet on WARH01
INTERnet ACP Process creation success
%%%%%%%%%%% OPCOM 14-AUG-2000 15:48:25.46 %%%%%%%%%%%
Message from user INTERnet on WARH01
INTERnet ACP FTP Accept Request from Host: 192.168.198.20 Port: 1026
%%%%%%%%%%% OPCOM 14-AUG-2000 15:48:25.97 %%%%%%%%%%%
Message from user AUDIT$SERVER on WARH01
Security alarm (SECURITY) and security audit (SECURITY) on WARH01, system id: 14
977
Auditable event: Network login failure
Event time: 14-AUG-2000 15:48:25.94
PID: 20200126
Process name: UCX$FTPD
Username: UCX$FTP
Process owner: [UCX$AUX,UCX$FTP]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE
Status: %RMS-E-FLK, file currently locked by another user
%%%%%%%%%%% OPCOM 14-AUG-2000 15:48:26.21 %%%%%%%%%%%
Message from user INTERnet on WARH01
INTERnet ACP detected UCX$FTPD exiting before 'accept'
%%%%%%%%%%% OPCOM 14-AUG-2000 15:48:26.22 %%%%%%%%%%%
Message from user INTERnet on WARH01
INTERnet ACP AUXS error during process exit Status = %RMS-E-FLK
%FTP-E-NETERR, I/O error on network device
-SYSTEM-F-REJECT, connect to network object rejected
SYSTEM>
I have looked at all your recommendations and as far as I can determine all
rights and permissions are exactly as the 3900.
the enable watch/class=all file does not give me anything more useful than the
output ablove.
Where do I go from here?
The Answer is :
Your message references OpenVMS on various VAX systems, but lists the
platform as OpenVMS Alpha -- the OpenVMS Wizard will assume that this
is an OpenVMS VAX system, not an OpenVMS Alpha system. (But if this
is an OpenVMS Alpha system, the use of OpenVMS Alpha V7.1-2 or V7.2-1
is recommended, as is the use of TCP/IP Services V5.0A or later.)
A file necessarily accessed by LOGINOUT is being held locked, and is
preventing the operation from completing. This could be the system
authorization file, a log file, or otherwise.
The (undocumented) SET WATCH/CLASS=class FILE provides information
only on the XQP activity in the local process, and not to the XQP
activity within the process that has invoked the LOGINOUT image.
The output from SHOW DEVICE/FILE might be interesting, looking for
applications that are holding SYSUAF.DAT, RIGHTSLIST.DAT or similar
file open, and looking for applications or operations or configurations
that would prevent a log file creation or an audit entry or other similar
file operation from completing, or potentially by problems accessing the
SYLOGIN or LOGIN.COM procedure.
|
|
|
|
|
