Transfer files from Alpha to PC with ftp connaction

[Steven Schweda]

> $ ftp 'alpha_host_name'

> I had run the test, and it works. but from
> PC no.

> c:\ftp ip_adress
> and i used to be asked to enter username in
> the Alpha.
> but now I got message "connection closed by
> remote host" after 1 minute.

Sounds like a firewall somewhere.

> when I try to connect to alpha with
> Internet Explore (ftp://ip adress), I see
> intranet's directories, but I cant open
> them.

I don't have a good explanation for MSIE
working (as well as it ever does) but the
command-line FTP client not working from the
same PC.

[Steven Schweda]

> Since it works "in-band" it does not neet
> arrangements with any other network devices
> (such as firewalls) in the data path.

And a firewall can't block SSH or Telnet?

Kermit is fine, but it's not a network
panacea.

[Hoff]

> Since it works "in-band" it does not neet arrangements with any other network devices (such as firewalls) in the data path.

Uh, no.

The ftp client can select ACTIVE and send along a local port for the return connection from the ftp server.

The ftp client can also select PASV and receives a port to connect to the ftp server, and connects to that port.

In either case, any intervening firewalls (and there are often at least two) can be set to accept or to reject connections into the ephemeral port range, or can have differing port ranges set. (Hosts can and do have different ranges for ephemeral ports, just to keep it interesting.)

Oh, and ftp exposes your authentication credentials to anyone in the coffee shop or to any malware on any of the LANs you traverse that knows how to use promiscuous-mode monitoring or snort or such.

Use sftp. sftp is rather more secure. And sftp massively easier to punch through intervening firewalls.

[Steven Schweda]

> [...] Alpha v6.2-1H3 [...]

> File: SYS$SYSDEVICE:[UCX$FTP]UCX$FTPD_STARTUP.COM

> Use sftp. [...]

SFTP is fine, too. Does a UCX which is
compatible with VMS V6.2-1H3 offer SFTP?

[Hoff]

Here's the commercial option:

http://www.process.com/tcpip/sshds.pdf

Or upgrade OpenVMS and TCP/IP Services to a more current version.

Or switch to the Process Multinet stack.

Likely other options around, too.

[Thomas Ritter]

Looks like it's time to perform a tcp trace on the vms side and see what's happening.

On our version ucx we have tcptrace.

$tcptrace 'pc' /brief/packet=1000000/protocol=tcp
or the full version
On our version ucx we have tcptrace.
$tcptrace 'pc' /full/packet=1000000/protocol=tcp

'pc' is the IP address as seen by the VMS of your PC. I need to qualify this, because around here IPs get NATed most of the time.

If the trace is available start by tracing a working connection, like initiating ftp on vms to itself. You can them see how it works.

Next trace the pc.

[Aneta]

I could'nt solve the problem and i give up.
I can't connect to Alphe with ftp from PC, but I installed ftp server at my PC and I connects from Alpha To PC and puts the files.
Thank you!!!