- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- %TCPIP-F-SSH_FATAL error from TCPIP$CONFIG.COM
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
Forums
Discussions
Discussions
Discussions
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
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
03-02-2005 12:59 AM
03-02-2005 12:59 AM
I was able to get SSH working on two of three similarly configured systems without much trouble. On the third, however, I get an error when I try to enable and start the SSH server using TCPIP$CONFIG.COM. When the script attempts to generate new keys by invoking SSH_KEYGEN2, it gives this error message:
%TCPIP-F-SSH_FATAL, non-specific fatal error condition
How helpful that is! There's no other text to indicate what might be going on.
Using Google I've found other references to TCPIP-F-SSH_FATAL but none that offered any insight into this problem.
Any help will be greatly appreciated.
(I already took care of the issue with /FLAG=TCPIP needing to be removed from the SET SERVICE SSH command in TCPIP$CONFIG.COM)
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2005 07:18 AM
03-02-2005 07:18 AM
SolutionPlease check that there is a valid UIC identifier that matches your username. Simplest check is SHOW PROCESS. Your "User Identifier" should look like:
User Identifier: [your-username]
or
User Identifier: [group-ident,your-username]
If the identifier shows up as a numeric UIC value, then create the correct identifier with:
$ MCR AUTHORIZE ADD/IDENT/USER=your-username
If it shows up as some other username, then you need to resolve the conflict (or just login as a privileged user with matching identifier to do your SSH install).
In general, the default expectation is username and matching UIC identifier name are the same string. However, for most purposes you do not need an identifier matching your username(*), BUT security related products tend to be picky. They also have a tendancy to obscure real error messages so as to not give away too many clues to people trying to break them.
(*)in some cases it may not be possible to have username=identifier. For example, a username can be all numeric, but an identifier name must start with an alphabetic character.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2005 10:33 PM
03-02-2005 10:33 PM
Re: %TCPIP-F-SSH_FATAL error from TCPIP$CONFIG.COM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2005 01:54 AM
03-04-2005 01:54 AM
Re: %TCPIP-F-SSH_FATAL error from TCPIP$CONFIG.COM
Your tip was exactly the right thing to check. There was no UIC identifier for the account that was running TCPIP$CONFIG. Adding one fixed the problem.
Thanks,
Galen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2005 01:57 AM
03-04-2005 01:57 AM