- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: pathworks external authentications troubleshoo...
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
тАО07-24-2008 05:51 AM
тАО07-24-2008 05:51 AM
Details: OpenVMS v7.3-2 Alpha, PW v6.1 I think, at least that is what PWVERSION command gives.
When its not working, when one tries to login, you get the username prompt, a long pause then the password prompt that always fails to work.
No error messages in any logs, other then bad password.
Any tips, hints????
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-24-2008 06:00 PM
тАО07-24-2008 06:00 PM
SolutionThe pause sounds like a network problem talking to the authentication system. Maybe a DNS translation problem? Do PING and NSLOOKUP work?
Might be interesting to try logging in at the console.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 06:54 AM
тАО07-25-2008 06:54 AM
Re: pathworks external authentications troubleshooting?
to troubleshoot:
$ define/system/exec sys$single_signon 80000001
$ reply/enable=security
The error could help a lot or a little.
If PATHWORKS is having problems communicating with a domain controller (you didn't indicate what role - PDC, BDC, or Member server of the PATHWORKS server) to authenticate a user, it's pretty good about logon NETLOGON messages in its System event log:
$ admin show events/full/since[=
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 10:25 AM
тАО07-25-2008 10:25 AM
Re: pathworks external authentications troubleshooting?
13:21:00.16: SYS$LOGONW - ACME state = 80000005
13:21:00.16: Function = ACME$_MAP_TO_USERNAME
13:21:00.16: Attempting to map Userid "NRPE"
13:21:00.16: Userid found in SYSUAF
13:21:00.16: User does not have ExtAuth set
13:21:00.16: Username = NRPE
13:21:00.16: IOSB status follows:
13:21:00.16: %SYSTEM-S-NORMAL, normal successful completion
13:21:00.16: IOSB devdepend follows:
13:21:00.16: %NONAME-W-NOMSG, Message number 00000000
When I try the admin logon, it works fine but I did notice it logs into the bdc and not the pdc. I'll talk to the domain admin and see what he can find out in his logs.
The usuall fix it to putts around, removing and adding the node to the domain, and/or rebooting, neither is always effective, sometimes just waiting a day or two will magically fix itself. No real answer.
Again, thanks for the tips, if I can pin it down I will post the answer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 10:36 AM
тАО07-25-2008 10:36 AM
Re: pathworks external authentications troubleshooting?
You stated:
...when a user attempts to login, I see and error that indicated the userid is invalid( it not ), the error returned is:
13:21:00.16: SYS$LOGONW - ACME state = 80000005
13:21:00.16: Function = ACME$_MAP_TO_USERNAME
13:21:00.16: Attempting to map Userid "NRPE"
13:21:00.16: Userid found in SYSUAF
13:21:00.16: User does not have ExtAuth set
The error returned was "User does not have ExtAuth set" or did you just post the wrong screen area?
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 10:57 AM
тАО07-25-2008 10:57 AM
Re: pathworks external authentications troubleshooting?
13:56:16.70: SYS$LOGONW - ACME state = 80000005
13:56:16.70: Function = ACME$_MAP_TO_USERNAME
13:56:16.70: Attempting to map Userid "CORDILLJ"
13:56:16.70: Userid found in SYSUAF
13:56:16.70: ExtAuth is set for user
13:56:40.74: Return status from ACME map routine follows:
13:56:40.74: %ACME-E-NOSUCHUSERID, user-id does not exist or is invalid
13:56:40.74: ACME reason code = 2221
13:56:40.74: IOSB status follows:
13:56:40.74: %SYSTEM-F-INVUSER, no such user
13:56:40.74: IOSB devdepend follows:
13:56:40.74: %ACME-E-NOSUCHUSERID, user-id does not exist or is invalid
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2008 11:39 AM
тАО07-25-2008 11:39 AM
Re: pathworks external authentications troubleshooting?
Ok. Can't recall if PATHWORKS v6.1 only seeks out the domain PDC for extauth or if it seeks out any domain controller.
You might want to check if it can at least find the PDC:
$ @sys$startup:pwrk$define_commands
$ nbshow knbstatus
If there's no obvious NETLOGON error seen by $ ADMIN SHOW EVENTS/FULL/SINCE then you may need to resort to getting a network trace:
$ @sys$startup:tcpip$define_commands
$ tcpdump -s1518 -w a.cap port 53 or 137 or 138 or 139
Duplicate the extauth failure and then stop the trace with Ctrl+C. I think you can attach the capture file here and we can download for analysis but may want to zip it first with "-V" to retain file attributes...
Paul
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-03-2008 07:46 AM
тАО09-03-2008 07:46 AM