- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: S/KEY sequence?
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
тАО09-27-2006 09:01 AM
тАО09-27-2006 09:01 AM
S/KEY sequence?
S/KEY sequence not found
User authorization failure
right after I enter my user name but before I can enter a password, and then the session is disconnected. I'm guessing this is something like I have to tell it what networks to trust, but I don't know how to do so. Any help appreciated.
yrs., BH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2006 09:33 AM
тАО09-27-2006 09:33 AM
Re: S/KEY sequence?
you're using. Google suggests that it may be
MultiNet, as that one seems to offer some
S/Key stuff (about which I know nothing). If
so, it might pay to pore over the MultiNet
Administrator's Reference manual, and/or look
for MultiNet-specific support channels.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2006 12:46 AM
тАО09-28-2006 12:46 AM
Re: S/KEY sequence?
$ mu conf/serv
SERVER-CONFIG> disable access
SERVER-CONFIG> exit
$ subm/user=system/nolog multinet:start_server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2006 02:46 AM
тАО09-28-2006 02:46 AM
Re: S/KEY sequence?
Yes, it's Multinet. Sorry, I should have mentioned that. I have a lot more experience with Unix, Cisco, Adtran, etc., and don't always know what info is relevant with OpenVMS.
I can log in via console, and from anywhere on the same network as the MicroVax. If I disable the service, won't I only be able to log in from the console?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2006 03:34 AM
тАО09-28-2006 03:34 AM
Re: S/KEY sequence?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-29-2006 05:40 AM
тАО09-29-2006 05:40 AM
Re: S/KEY sequence?
Username: [me]
Error opening connection to Secure/IP authentication server
User authorization failure
Username:
So, now I'm looking for a Secure/IP manual. At least I've still got console and LAT access.
BH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-29-2006 06:21 AM
тАО09-29-2006 06:21 AM
Re: S/KEY sequence?
I suspect that the implemtation of this service may involve a dedicated server process. If that was the case then restarting the master server would not impact it. You should examine the output of SHOW SYSTEM and see if there is something called ACCESS_SERVER or similar. If so you'll need to terminate it - there may also be associated system logical names that need deassigning. If this is the case you might find it simplest to reboot (unless you can find the correct "MU NETC ACCESS SHUT" or whatever incantations to politely shut it down). With the service disabled and the startup file renamed or deleted a reboot should put you back in the state you desire. Sorry I can't be definitive here... without actually observing what you've got my memory isn't good enough.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-29-2006 12:31 PM
тАО09-29-2006 12:31 PM
Re: S/KEY sequence?
Google led me to:
http://www.process.com/tcpip/mndocs/MN%20v5.0%20Admin%20Reference/Pref.htm
http://www.process.com/tcpip/mndocs/MN%20v5.0%20Admin%20Reference/httoc.htm
http://www.process.com/tcpip/mndocs/MN%20v5.0%20Admin%20Reference/Ch02.htm
http://www.process.com/tcpip/mndocs/MN%20v5.0%20Admin%20Reference/Ch08.htm
Of course, I don't know your MultiNet version,
so this may be the wrong manual for you, but I
assume that there's more to be found at
process.com.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-30-2006 12:02 PM
тАО09-30-2006 12:02 PM
Re: S/KEY sequence?
If you find that there is a hook defined for MultiNet's ACCESS service then you can disable it on the fly by
$ mcr sysgen
SYSGEN> set LGI_CALLOUTS 0
SYSGEN> write active
SYSGEN> exit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2006 02:00 AM
тАО10-02-2006 02:00 AM
Re: S/KEY sequence?
MULTINET_ACCESS_CLIENT_ONLY
MULTINET_ACCESS_SERVER_ADDRESS
MULTINET_ACCESS_SERVER_PORT
MULTINET_ACCESS_LOCAL_DEVICES
MULTINET_LOGIN
MULTINET_ACCESS_NETWORK_LOGIN
MULTINET_ACCESS_MUTUAL_AUTHENTICATION
MULTINET_ACCESS_FTP
MULTINET_ACCESS_ALLOW_DECNET_LOGIN
MULTINET_ACCESS_ALLOW_DECTERM_LOGIN
MULTINET_ACCESS_TICKET_LIFETIME
MULTINET_ACCESS_ALLOW_SHOW_KEY
MULTINET_ACCESS_CALLOUTS_DEBUG
MULTINET_ACCESS_KERBEROS_PRINCIPAL
LGI$LOGINOUT_CALLOUTS
MULTINET_LGISHR
As mentioned above, the sysgen parameter lgi_callouts can be set.
From the problem description so far, I would guess that the access server is no longer reachable. The system could have been set up to function as its own access server.
$ MULTINET CONFIGURE/ACCESS
ACCESS-CONFIG>show server-address
If that shows your old IP address, then you can change it to the new address (or 127.0.0.1) and follow the instructions on restarting the access server.