- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-18-2006 10:05 PM
тАО10-18-2006 10:05 PM
VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-18-2006 10:45 PM
тАО10-18-2006 10:45 PM
Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-18-2006 10:53 PM
тАО10-18-2006 10:53 PM
Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-18-2006 11:09 PM
тАО10-18-2006 11:09 PM
Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem
can you debug the BIND resolver by using:
$ DEFINE TCPIP$BIND_RES_OPTIONS "debug"
Then issue your IP commands...
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2006 12:15 AM
тАО10-19-2006 12:15 AM
Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2006 12:37 AM
тАО10-19-2006 12:37 AM
Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2006 12:42 AM
тАО10-19-2006 12:42 AM
Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2006 12:43 AM
тАО10-19-2006 12:43 AM
Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2006 12:54 AM
тАО10-19-2006 12:54 AM
Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2006 01:23 AM
тАО10-19-2006 01:23 AM
Re: VMS V7.3-2 TCPIP 5.4 ECO5 to ECO6 FTP problem
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,
John.