Operating System - OpenVMS
1752780 Members
6251 Online
108789 Solutions
New Discussion юеВ

Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem

 
John Abbott_2
Esteemed Contributor

VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem

Related closed call...

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1057983

seen it (thanks), tested out the solution, but the supplied fix (copy *IPC_SHR.EXE) DOES NOT work on all our systems (I've checked IPC_SHR images installed via SDA, I am using the ECO 5 ones).

So far, systems with BIND disabled appear fine, those with BIND enabled do not. The problem is intermittent on the enabled ones, mostly every other ftp connect fails, but sometimes I get more than one failure to connect in a row.I need to test further... so far

$ ftp dns_name(local or resolved from primary DNS (wintel)) OR specifying an IP_ADDR fails, examples:

Reply from an ftp command to a softer_os gives:
$ ftp dns_name OR ip_addr
421 Service not available, Remote server has closed the connection

Alpha reply:
$ ftp dns_name or ip_addr
TCPIP-E-FTP_NETERR, I/O error on network device
-SYSTEM-F-REJECT, connect to network object rejected

Did anyone get an offical reply/solution from HP from the previous call I've linked to ? I don't think the ECO6 kit has been re-mastered.

Thanks in advance.
John.
Don't do what Donny Dont does
20 REPLIES 20
John Abbott_2
Esteemed Contributor

Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem

Update. Problem system is a 3 note system, common system disk. One node can ftp connect 100%, the two others have 82~85% failure rate. Routing looks fine, smtp and telnet fine. *IPC_SHR.EXE images are is sys$common:[syslib]
Don't do what Donny Dont does
John Abbott_2
Esteemed Contributor

Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem

The TCPIP$*.DAT files are in sys$common:[sysexe] (i.e ther's nothing in sysroot or anything obvious for that makes one node work and the other not).
Don't do what Donny Dont does
Volker Halle
Honored Contributor

Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem

John,

can you debug the BIND resolver by using:

$ DEFINE TCPIP$BIND_RES_OPTIONS "debug"

Then issue your IP commands...

Volker.
John Abbott_2
Esteemed Contributor

Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem

Hi Volker, looks like the reverse lookup debug output is missing on a failure. I include an attachment (with ubstituted ip and dns names) that gives two examples both from an node with intermittent ftp connects (the first works, the second that fails).

If I define the remote_system.co.uk name on the local host then I get no dns debug output and still ad-hoc failure.
Don't do what Donny Dont does
Volker Halle
Honored Contributor

Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem

John,

as the IP connection to the FTP server seems to fail, there will be no reverse lookup in case of the failing attempt.

Does the problem also happen with TELNET ? If so, you could use 'Monitoring Socket Activity' feature of TCPIP:

$ DEFINE TCPIP$SOCKET_TRACE 1
$ DEFINE TCPIP$SOCKET_TRACE - SYS$LOGIN:TCPIP$SOCKET_TRACE.LOG
$ TELNET node-or-IP-address

$ TYPE SYS$LOGIN:TCPIP$SOCKET_TRACE.LOG

The next step after this would be a TCPTRACE of the packets to/from the remote node.

Volker.
John Abbott_2
Esteemed Contributor

Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem

Hi Volker, I tried this before, I could not get a TELNET connect to fail.
Don't do what Donny Dont does
Volker Halle
Honored Contributor

Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem

John,

slight correction:

$ DEFINE TCPIP$SOCKET_TRACE 1

will show trace on SYS$OUTPUT

or

$ DEFINE TCPIP$SOCKET_TRACE - SYS$LOGIN:TCPIP$SOCKET_TRACE.LOG

will put trace in file.

http://h71000.www7.hp.com/doc/732final/6631/6631pro_003.html#socket_trace_sec

Volker.
Volker Halle
Honored Contributor

Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem

John,

if I try a TCPIP$SOCKET_TRACE with FTP, I get the following error (TCPIP V5.5):

$ DEFINE TCPIP$SOCKET_TRACE 1
$ ftp i64vms
Error opening trace log file: i/o error
220 i64vms.xxx.xxx FTP Server (Version 5.5) Ready.
Connected to I64VMS.
Name (I64VMS:halle):

It works with TELNET.

A TCPTRACE should not pose a big problem, it's just a couple of packets to be traced.

Volker.
John Abbott_2
Esteemed Contributor

Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem

Hi Volker thanks for your help so far,

I include the output for a TCPTRACE remote_node/FULL/OUTPUT=file.txt

14:13:12 entries are from the failure (error 421)
14:13:31 are from a good connect

again using $ ftp remote_dns_node_name
first one failed, up arrow, and 2nd attempt connected.

John.
Don't do what Donny Dont does