- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: FTP fails to connect
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
тАО07-22-2004 03:17 AM
тАО07-22-2004 03:17 AM
Our new Windows 2000 PC, however, cannot connect to the Alpha. The output is:
C:\ ftp 192.9.200.70
Connected to 192.9.200.70.
Connection closed by remote host.
C:\
Numerous different ftp programs have been tried but to no avail. Our guess is that there is timeout on Windows 2000 that is different to the NT system. Does anyone know how to resolve this? Or know of a diagnostic tool we can use to find out the problem?
Thanks,
Kevin.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2004 03:39 AM
тАО07-22-2004 03:39 AM
Re: FTP fails to connect
the "slow prompt" is typically caused by the inability to resolve the other partners host name. In your situation it most probably is easist to just add entries for the three systems involved in the three local hosts files.
On a larger scale obviously a working DNS would be the solution.
Greetings, Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2004 06:48 PM
тАО07-22-2004 06:48 PM
Re: FTP fails to connect
to try to troubleshoot this problem, first look at the FTP service: $ UCX SHO SERV FTP/FULL
Find out the User_name under which the FTP server is running and look into it's default directory. There should be a .LOG file, possibly containing error messages.
Also do a REPLY/ENABLE and repeat the failing FTP connect from the Windows 2000 PC. Any OPCOM error messages ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2004 10:04 PM
тАО07-22-2004 10:04 PM
Re: FTP fails to connect
If all network traffic is slow, there may be a problem for the network adapter in the Alpha negotiating speed and mode (duplex/noduplex) with the hub. Look at the error counters in
$ mc lancp show device /counters
If there are many alignment errors and/or frame check errors, this would indicate negotiation problems.
To solve these, set the NIC operation mode e.g. to Fast Full Duplex (or, depending on your hubs capabilities, to any other mode, but not Auto). It's best to define this at the Alpha (SRM) console level (e.g. ewa0_mode if your network adapter is ewa0). If shutting down the Alpha is not an option, you can also set the characteristics with
$ mc lancp set device ewa0 /speed=[10|100] /[no]full_duplex
(again assuming your network device is EWA0)
Of course, the respective port on the hub should also receive fixed settings, but minihubs usually aren't manageable...
If you have only the two nodes connected together, you could connect them with a crossover cable and set the line characteristics the same at both ends.
Hope this helps,
Han
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2004 11:37 PM
тАО07-22-2004 11:37 PM
Re: FTP fails to connect
%RMS-E-RNF, record not found
%UCX-E-FTP_GETHST, Error in getting host name
There may also be a complication here as it turns out that at one point the Alpha sat on a LAN with DNS servers. These primary and secondary server IP addresses are still set but no longer exist. Can anyone walk me though using UCX (or @UCX$config) to reconfigure it and add the local hosts?
Thanks,
Kevin.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2004 11:53 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2004 11:53 PM
тАО07-22-2004 11:53 PM
Re: FTP fails to connect
UCX> SET CONFIG NAME /NOSERVER=ip
and
UCX> SET NAME /NOSERVER=ip /SYSTEM
2. To add host entries:
UCX> SET HOST hostname /ADDRESS=ip
cu,
Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-23-2004 12:20 AM
тАО07-23-2004 12:20 AM
Re: FTP fails to connect
Thanks again,
Kevin.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2004 03:56 AM
тАО11-02-2004 03:56 AM
Re: FTP fails to connect
Using FTP.EXE from an NT system on the Windows 2000 server also made the intermittent FTP connection problems go away.
Volker.