HP OpenVMS Systems

ask the wizard
Content starts here

FTP network object connect timeout?

» close window

The Question is:

My Question is:
I'm experiencing the same problem as another enquirer as below
however my settings are as you already recommend.
I can ftp to an older VAX with no problem.
The problem exists between two alpha servers of the same specification.
550-Network READ failure.
550 connect to network object timed-out or failed
TCPIP> sysconfig -q inet tcp_mssdflt
tcp_mssdflt = 536
TCPIP> sho ver
  Compaq TCP/IP Services for OpenVMS Alpha Version V5.1 - ECO 3
  on a COMPAQ AlphaServer DS20E 666 MHzP running OpenVMS V7.3
Previous Question by another enquirer was:
Every time we make an ftp  between two VAX of large files (> 100 Mb) we have
 this error message which appears
550-Network READ failure.
550 connect to network object timed-out golden failed
We have no problem for the small files and the transfer takes place well. We
 have no network problem and we can make a transfer of large files between 2
 machines NT.
Please, could you please check may cause the problem.
$ tcpip sho version
  Compaq TCP/IP Services for OpenVMS Alpha Version V5.1 - ECO 4
  on a AlphaServer DS20 500 MHz running OpenVMS V7.2-1
File Transfer Protocol (FTP):
  TCPIP$FTP_CHILD;1         	 V5.1-15E         24-AUG-2001
  TCPIP$FTP_CLIENT;1		 V5.1-15I         17-APR-2002
  TCPIP$FTP_SERVER;1	V5.1-15E         24-AUG-2001  SYS$COMMON:[SYSEXE]
  TCPIP$TFTP;1           		V5.1-15A         27-APR-2001
The Answer is :
  This could be a known interaction between TCP/IP V5.1 ECO 4 and a
  unitary MTU setting that is occasionally found after upgrades from
  older IP releases.
  Intervening firewalls can also potentially be involved.
  If tcp_mssdflt is set to 1, consider resetting it to the typical 536.
  After having invoked the following:
  Use the following to display the current tcp_mssdflt value:
    sysconfig -q inet tcp_mssdflt
  And -- if set otherwise -- use the following to reset the value:
    sysconfig -r inet tcp_mssdflt=536
 answer written or last revised on ( 30-DEC-2002 ) ; close window

The Answer is :

  The referenced topic is (8215).
  You do not have the version referenced in (8215), as you have an
  older ECO kit loaded.
  Please ensure you have the current TCP/IP Services version and the
  current ECO loaded -- you are presently running an older TCP/IP
  Services version -- and please then contact the support center for
  assistance should the problem persist.
  As of this writing, TCP/IP Services V5.3 -- with ECO -- is current.

answer written or last revised on ( 27-JAN-2003 )

» close window