Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- From: Gremlin <not.here@xxxxxxxx>
- Date: Mon, 20 Nov 2006 21:57:26 +1100
Hi Dave
I thought about the permissions, but then the account I am running it from (for testing purposes only) has proc/priv=all so I can read/write everything....
Dave Froble wrote:
Gremlin wrote:.
Just confused would be a good answer :)
1. ECO 5
2. [SYSMGR] > ssh -v
debug: Ssh2/SSH2.C:1847: CRTL version (SYS$SHARE:DECC$SHR.EXE ident) is V7.3-2-0
0
debug: SshAppCommon/SSHAPPCOMMON.C:307: Allocating global SshRegex context.
debug: SshConfig/SSHCONFIG.C:3285: Metaconfig parsing stopped at line 3.
debug: SshConfig/SSHCONFIG.C:842: Setting variable 'VerboseMode' to 'FALSE'.
debug: SshConfig/SSHCONFIG.C:3193: Unable to open ssh2/ssh2_config
I don't use this stuff, so I may be far off on this. The first thing that comes to mind is that either there is a missing file, or, you don't have the privilege of opening the file.
Type vax2$dka0:[sys0.syscommon.][sysexe]tcpip$ssh_ssh2.exe -h for help.
I guess this is where the problem lies....
3. Again, don't know - I was hoping that (according to my readin of the manual), it would find that I had no public key and therefore prompt for a password. It doesn't, I just get...
warning: Authentication failed.
Disconnected; connection lost (Connection closed by remote host.).
So, I am not authenticating but neither am I being prompted for a password - and this is doing an ssh on the alpha where the ssh server is installed.
Cheers
Steven M. Schweda wrote:
From: Gremlin <not.here@xxxxxxxx>
Services started and enabled on an Alpha, can connect using FTP, Telnet, web server running etc, scan shows port 22 open, but......I can't make a connection.
Haven't played with the configuration files at all, would appreciate any suggestions.
Suggestion 1. Show the output from "TCPIP SHOW VERSION". "patched"
means less than you seem to think it does.
Suggestion 2. What means "I can't make a connection."? What did you
do, from where did you do it, and what happened when you did it? If
none of that included "ssh -v", then try something which includes "ssh
-v", and publish the results.
Suggestion 3. Disclose whether you were expecting to use public-key,
host-based, or password authentication.
Suggestion 4. "http://h71000.www7.hp.com/doc/tcpip54.html",
"http://h71000.www7.hp.com/doc/732final/aa-rvbua-te/aa-rvbua-te.html".
------------------------------------------------------------------------
Steven M. Schweda sms@antinode-org
382 South Warwick Street (+1) 651-699-9818
Saint Paul MN 55105-2547
- Follow-Ups:
- Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- From: Dave Froble
- Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- References:
- Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- From: Steven M. Schweda
- Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- From: Gremlin
- Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- From: Dave Froble
- Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- Prev by Date: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- Next by Date: Re: F$SEARCH() complications with mixed case filenames
- Previous by thread: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- Next by thread: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
- Index(es):
Relevant Pages
|