23 Apr
2010
23 Apr
'10
2:48 p.m.
Rob Jarratt [robert.jarratt at ntlworld.com] wrote:
Very interesting now. I booted up another VAX, also
running
7.3, and I was able to FTP to that one no problem at all. I
can telnet to the "bad" VAX no problem. Pinging is fine. I
can use DECnet fine between both VAXen. I can ping between both VAXen.
So basic connectivity is OK, you just have an FTP problem.
When you say run a packet capture on the VMS end do
you mean
run a sniffer program actually on the VAX? If so I don't know
of any software for that, do you have a recommendation? I can
run a sniffer on the PC, which is connected to the same
switch (not a hub), as this is all on single segment.
I'm running UCX 4.0 and my UCX experience is limited, but on
my box "HELP TCPIPTRACE" is the place to start. For today's
problem, however, it's unlikely to help as you'll see an
attempted connection and a failure (SYN from PC, RST from VAX
at a wild guess). It might be worth a shot as it might
show that the initial connection works and something goes
wrong later on.
If I try to run UCX FTP on the good VAX to connect to
the bad
VAX this is what I get:
That sounds like nothing is listening for FTP.
Try:
$ UCX
UCX> SHOW SERVICE
Does that list FTP?
Antonio
conn 192.168.0.106
%TCPIP-E-FTP_NETERR,
I/O error on network device
-SYSTEM-F-REJECT, connect to network object rejected