- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Access Control Violation
Operating System - OpenVMS
1753795
Members
6739
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО11-12-2008 01:23 AM
тАО11-12-2008 01:23 AM
Re: Access Control Violation
Aculisse,
in your first entry, you said that this problem is only happening on one of your 4 nodes in the same cluster. Do these system share a common OpenVMS environment, like same system disk or at least all common files set up correctly ? Does the proxy access work to any of the 4 nodes ?
You need to add the proxy only on the destination system. Be aware that the various session control applications can have attributes set to disable outgoing or incoming proxy access. Check with MC NCL SHO SESS CONTROL APP FAL ALL
The correct statement to add your porxy for a DECnet connection would be:
UAF> add/proxy local:.sahara::test test/def
but just using sahara::test might work as well.
Does access work, if you explicitly specify username and password for your test account, i.e.
$ dir node"username password"::
Volker.
in your first entry, you said that this problem is only happening on one of your 4 nodes in the same cluster. Do these system share a common OpenVMS environment, like same system disk or at least all common files set up correctly ? Does the proxy access work to any of the 4 nodes ?
You need to add the proxy only on the destination system. Be aware that the various session control applications can have attributes set to disable outgoing or incoming proxy access. Check with MC NCL SHO SESS CONTROL APP FAL ALL
The correct statement to add your porxy for a DECnet connection would be:
UAF> add/proxy local:.sahara::test test/def
but just using sahara::test might work as well.
Does access work, if you explicitly specify username and password for your test account, i.e.
$ dir node"username password"::
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2008 01:56 AM
тАО11-12-2008 01:56 AM
Re: Access Control Violation
thanks volker...
i have checked with MC NCL, it is in true state
for all.
actually we have four different openvms cluster
but each cluster in different place. In my cluster having 4 alpha nodes. one of my alpha nodes having this problem but SAHARA is the another clusters node.
SAHARA::TEST user only trying to access my node.
i have checked with MC NCL, it is in true state
for all.
actually we have four different openvms cluster
but each cluster in different place. In my cluster having 4 alpha nodes. one of my alpha nodes having this problem but SAHARA is the another clusters node.
SAHARA::TEST user only trying to access my node.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2008 02:55 AM
тАО11-12-2008 02:55 AM
Re: Access Control Violation
Acullise,
discussing and troubleshooting such a problem requires precise configuration information - otherwise it becomes more of a guesswork.
You need to supply information about the source node or cluster from which the access originates and also information about the destination node or cluster. And provide information about what exactly has been changed.
If the access is only happening from one explicit node in the source cluster to one explicit node in the destination cluster, then try from another node or to another node in those clusters. If access is to a DECnet cluster alias, things may just be wrong on node node. First try access by explicitly specifying the correct username and password. Find out whether that works as expected. Then look at NET$SERVER.LOG in the default directory of the destination account and find out the source node information from there. Is it like what you expect ?
Volker.
discussing and troubleshooting such a problem requires precise configuration information - otherwise it becomes more of a guesswork.
You need to supply information about the source node or cluster from which the access originates and also information about the destination node or cluster. And provide information about what exactly has been changed.
If the access is only happening from one explicit node in the source cluster to one explicit node in the destination cluster, then try from another node or to another node in those clusters. If access is to a DECnet cluster alias, things may just be wrong on node node. First try access by explicitly specifying the correct username and password. Find out whether that works as expected. Then look at NET$SERVER.LOG in the default directory of the destination account and find out the source node information from there. Is it like what you expect ?
Volker.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP