I've understood that Steven Schweda posts his answers as attachments because this community has some issues on the OS platform he uses.
SFTP is an extension of the SSH protocol, so a basic SSH connection is a necessary requirement for SFTP.
(It is possible to configure the server to reject non-SFTP connections, but to do that, the server must first accept the connection and check the client's protocol request. The server cannot know if the client wants SFTP or SSH until it has accepted the connection and completed at least a part of the SSH protocol negotiation.)
By the netstat listings you posted, both SCP1 and SCP2 hosts seem to have something (most likely a sshd daemon) listening on port 22.
What is noteworthy is that you seem to have multiple sockets listening on port 22, with local address specified as "*.22". Your netstat output also tells me that your SCP1 and SCP2 systems both have multiple IP addresses configured... apparently you have multiple network interfaces, or multiple IP addresses on the same physical interface?
Perhaps 10.16.2.82, the IP addres you're testing, was configured on SCP2 after sshd was already started on SCP2. In this case, the sshd daemon might not detect newly configured interfaces until it is restarted.
So you might want to try restarting sshd first. On HP-UX, the name of the sshd start-up script is not necessarily obvious:
sh /sbin/init.d/secsh stop
sh /sbin/init.d/secsh start
Unless you have a very old version of SSH, restarting the sshd daemon should be safe: it restarts only the "master" daemon that listens for incoming connections. Any existing SSH connections will not be interrupted.
The addresses 10.16.2.81 and 10.16.2.82 do not appear in your netstat snippets at all. Are they really configured to SCP1 and SCP2, or are they just some VPN/NAT/proxy addresses you're using to connect to the actual server? If the latter, the VPN/NAT/proxy/whatever might not be configured to pass through SSH/SFTP connections to SCP2.
MK
