Subject: Re: FTP failed bad or no setup
To: Stanley Reynolds <firstname.lastname@example.org>
From: John <email@example.com>
Date: 07/15/2001 14:01:30
> Need to transfer image file from windows PC to vax.
That's your problem there - Windows.
If you wanted us to help diagnose a problem with an FTP daemon running on
the VAX, that'd be fine, but there are too many possible reasons why an
FTP service would fail on Windows. It's not a finite state system.
You should uncomment the ftp line in /etc/inetd.conf, reHUP inetd, and use
an FTP client on the Windows machine.
But looking at this:
> local: vxt2000.SYS remote: vxt2000.SYS
> 502 Unrecognized or unsupported command
> 227 Listening on (90,0,0,32,4,19)
> 150 Opening data connection
> 500 File transfer failed
> Sun Jul 15 11:39:40 2001 0 Incoming connection
> request on interface 22.214.171.124
> Sun Jul 15 11:39:40 2001 0 Connection request
> accepted from 126.96.36.199
> Sun Jul 15 11:39:40 2001 0 USER anonymous
> Sun Jul 15 11:39:40 2001 0 SYST
> Sun Jul 15 11:39:40 2001 0 PWD
> Sun Jul 15 11:39:40 2001 0 TYPE I
> Sun Jul 15 11:40:25 2001 0 SIZE vxt2000.SYS
> Sun Jul 15 11:40:25 2001 0 EPSV
This is where the "502 Unrecognized or unsupported command" comes from -
extended passive mode.
> Sun Jul 15 11:40:25 2001 0 PASV
> Sun Jul 15 11:40:25 2001 0 Connection with data
> socket accepted.
> Sun Jul 15 11:40:25 2001 0 RETR vxt2000.SYS
> Sun Jul 15 11:40:25 2001 0 Unable to open file:
> pö*†JŸ×ì contains an invalid path.
Everything looks fine up until here. The file request happens successfully
- the remote system asks for vxt2000.SYS. However, "p*^FJ^_^W^^^C" comes
from the Windows end. This certainly doesn't come from the VAX.
This is probably the result of problems in mapping the long file names to
the 8.3 filesystem that Windows runs on. Try running scandisk, then try
putting this into a path that doesn't use more than 8.3 (like c:\files\).
> Loaded the VS4000/60 from 1.5 iso image.
> Configured the le0 interface but no other setup.
> I'am new to netbsd so my problem is most likely in the
> setup. Could the vax ip be set for 6 hex address and
> the PC 4 hex address ? But why does ping work ?
No to the addresses. I don't know what the ,4,19 is for, but I'd guess
it's some sort of notation for what dataport will be used for FTP transfer
(4*256 + 19, perhaps). But I'd say it's a safe bet that the path on the
Windows side is what's screwed up, so I wouldn't worry about the ,4,19.
Again, allow ftp connections to your 4000/60 and rely on Windows as little