| Title: | "ASK THE WIZARDS" |
| Moderator: | QUARK::LIONEL |
| Created: | Mon Oct 30 1995 |
| Last Modified: | Mon May 12 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1857 |
| Total number of notes: | 3728 |
Return-Path: "VMS001::WWW"@vms001.das-x.dec.com Received: by vmsmkt.zko.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX); Mon, 27 Jan 1997 18:08:30 -0500 Received: from vms001 by mail11.digital.com (8.7.5/UNX 1.5/1.0/WV) id RAA23416; Mon, 27 Jan 1997 17:58:37 -0500 (EST) Date: Mon, 27 Jan 1997 17:58:44 -0500 Message-Id: <[email protected]> From: "VMS001::WWW"@vms001.das-x.dec.com (27-Jan-1997 1758) To: [email protected], [email protected], [email protected] Subject: Ask the Wizard: '[email protected]' X-VMS-To: [email protected] Remote Host: (null) Browser Type: Mozilla/3.01 (Win95; I) Remote Info: <null> Name: Drew McMillon Email Address: [email protected] CPU Architecture: Alpha Version: v 6.2 Questions: Dear Mr. Wizard, How are TCP/IP Services for VMS V3.3 (UCX) configured for Passive ftp (OpenVMS Alpha V6.2)? FTP works for some of our VAX and Alpha internet clients. They are sending us files using FTP. Other clients are presented with the message "Can't build data connection for node xxx.xxx.xxx.xxx" (xxx.xxx.xxx.xxx is the clients internet address.) Does this error message ring a bell? Current theories are that this message comes from Multinet/TGV TCP/IP software. Or the remote client may have some security enabled. (Remote System Management is minimal.) The unsuccessful ftp clients are able to invoke ftp to our system, enter a username and a password successfully. The error message appears when they enter the put <filename> command. Thanks for listening. Drew McMillon
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1562.1 | Details Lacking | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Tue Feb 11 1997 13:54 | 30 |
The current release of Digital TCP/IP Services (UCX) is V4.1 ECO 3
(or later). Please upgrade.
The exact failure sequence is not clear from your note -- if these
are inbound or outbound FTP connections, and what IP packages other
than UCX are involved, and if there is any pattern to the failure.
You will need to become familar with the network topography at the
sites that are failing -- are there firewalls involved? -- and try
to determine why the sites are failing.
Also be aware that recent versions of OpenVMS and UCX support the
COPY/FTP command, when configured per the documentation.
And look in the SYS$SYSDEVICE:[UCX$FTP]UCX$FTPD.LOG -- check the SYSUAF
for the receiving (remote?) system for the exact location -- for any
errors reported by the receiving system. (Or look in the log file for
whatever IP package is running on the remote system.)
The FTP codes use the following general rule for the portion of the
connection processing that generates the error:
1XX - "preliminary", setup codes
2XX - "completion", final (ending) codes
3XX - "continue", dialogue type codes
4XX - "transient", codes not related to anything really
5XX - "error", final (error) codes
| |||||