<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ftp issues. in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231459#M328716</link>
    <description>Hi Dennis,&lt;BR /&gt;The file systems are local to the system.&lt;BR /&gt; &lt;BR /&gt;For automounter, I agree, the only way to free this up is to reboot. &lt;BR /&gt;Thanks,&lt;BR /&gt;Tom.</description>
    <pubDate>Fri, 11 Jul 2008 10:56:42 GMT</pubDate>
    <dc:creator>Tom Marting</dc:creator>
    <dc:date>2008-07-11T10:56:42Z</dc:date>
    <item>
      <title>ftp issues.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231453#M328710</link>
      <description>Hello,&lt;BR /&gt;I'm running HP-UX 11.11 on an rp4440.&lt;BR /&gt;&lt;BR /&gt;I am able to ftp to the rp4400 without issues, I can cd to certain filesystems (/opt, /root, /var, /home etc) and list their contents. But, when a try to cd into other directories such as /app (on internal disk) or /app2 (EMC disk) the ftp session hangs. It eventually comes back with the error:&lt;BR /&gt;&lt;BR /&gt;421 Service not available, remote server has closed connection&lt;BR /&gt;&lt;BR /&gt;A little background that may or may not be related to the ftp issues. Early this morning it appears automounter hung. Any process or session that tries to list or access /net hangs. We attempted to stop automounter by setting automounter=0 in nfsconf and stopping then starting  nfs.core,client and server. This did not work, automouter won't go away. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Tom.</description>
      <pubDate>Thu, 10 Jul 2008 16:33:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231453#M328710</guid>
      <dc:creator>Tom Marting</dc:creator>
      <dc:date>2008-07-10T16:33:08Z</dc:date>
    </item>
    <item>
      <title>Re: ftp issues.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231454#M328711</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If an FTP server won't allow logins, it is probably configured correctly, but the problem is probably with authorizing users at login. FTP servers in current distriubtions often authorize users with the Pluggable Authentication Modules library, in which case there should be an authorization file /etc/pam.d/ftp. A generic authorization file looks like this. (The line break on the first "auth" line is for readability. The entry is actually a single, long line). &lt;BR /&gt;&lt;BR /&gt;#%PAM-1.0 &lt;BR /&gt;auth required /lib/security/pam_listfile.so item=user \ sense=deny file=/etc/ftpusers onerr=succeed auth required /lib/security/pam_pwdb.so shadow nullok auth required /lib/security/&lt;BR /&gt;pam_shells.so &lt;BR /&gt;account required /lib/security/pam_pwdb.so &lt;BR /&gt;session required /lib/security/pam_pwdb.so &lt;BR /&gt;&lt;BR /&gt;Also, make sure the /etc/ftpusers file, or whatever users file is named in the first "auth" line, is configured correctly. &lt;BR /&gt;&lt;BR /&gt;BR/&lt;BR /&gt;Yaqub</description>
      <pubDate>Thu, 10 Jul 2008 16:39:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231454#M328711</guid>
      <dc:creator>YAQUB_1</dc:creator>
      <dc:date>2008-07-10T16:39:58Z</dc:date>
    </item>
    <item>
      <title>Re: ftp issues.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231455#M328712</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;1) I think this is a good thing. ftp is a bad tool to be using, as authentication and data stream are pretty much in the clear.&lt;BR /&gt;2) That being said, check the ftpaccess file for configuration to chroot the user or prevent full access. &lt;BR /&gt;3) /var/adm/syslog/syslog.log might give you an error message pointing to the source of the problem.&lt;BR /&gt;4) Perhaps use HP's openssh implementation known as Secure Shell available at &lt;A href="http://software.hp.com" target="_blank"&gt;http://software.hp.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 10 Jul 2008 16:42:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231455#M328712</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-07-10T16:42:39Z</dc:date>
    </item>
    <item>
      <title>Re: ftp issues.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231456#M328713</link>
      <description>does not look like Tom uses pam authentication!!</description>
      <pubDate>Thu, 10 Jul 2008 16:45:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231456#M328713</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2008-07-10T16:45:16Z</dc:date>
    </item>
    <item>
      <title>Re: ftp issues.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231457#M328714</link>
      <description>Unfortunately the application, managed by a 3rd party, requires ftp. The server also doesn't have an ftpaccess file and syslog.log has been of no help.</description>
      <pubDate>Thu, 10 Jul 2008 16:48:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231457#M328714</guid>
      <dc:creator>Tom Marting</dc:creator>
      <dc:date>2008-07-10T16:48:40Z</dc:date>
    </item>
    <item>
      <title>Re: ftp issues.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231458#M328715</link>
      <description>&amp;gt;when a try to cd into other directories such as /app (on internal disk) or /app2 (EMC disk) the ftp session hangs.&lt;BR /&gt;&lt;BR /&gt;This hang would make sense if they were NFS.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;We attempted to stop automounter by setting automounter=0 in nfsconf and stopping then starting nfs.core,client and server. This did not work&lt;BR /&gt;&lt;BR /&gt;You may have to reboot but that may fix the automounter anyway.</description>
      <pubDate>Fri, 11 Jul 2008 05:03:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231458#M328715</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2008-07-11T05:03:19Z</dc:date>
    </item>
    <item>
      <title>Re: ftp issues.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231459#M328716</link>
      <description>Hi Dennis,&lt;BR /&gt;The file systems are local to the system.&lt;BR /&gt; &lt;BR /&gt;For automounter, I agree, the only way to free this up is to reboot. &lt;BR /&gt;Thanks,&lt;BR /&gt;Tom.</description>
      <pubDate>Fri, 11 Jul 2008 10:56:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-issues/m-p/4231459#M328716</guid>
      <dc:creator>Tom Marting</dc:creator>
      <dc:date>2008-07-11T10:56:42Z</dc:date>
    </item>
  </channel>
</rss>

