- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Not authorized for terminal access -- see Syst...
Operating System - Tru64 Unix
1748181
Members
3675
Online
108759
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
Go to solution
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
тАО03-13-2007 02:52 AM
тАО03-13-2007 02:52 AM
Hello all,
I have a Sun workstation at my desk that I used to administer the servers in the data center. From the Sun login screen, I can choose Options -> Remote Login -> Enter Host Name and enter the name of a Tru64 box on the LAN.
If I connect as a non-root user, I authenticate and run a CDE session just like I was at a local graphics terminal. If however, I try the same thing as root, I get the error message serving as the title to this thread.
Here is what I have done so far.
1) I know my root account works because I can ssh into the box via putty with no problems.
2) I have verified that there is a ptys
as well as an entry for my workstation in /etc/securettys.
After reading the man page for login(1), I found that my exact error message is addressed. The reason according to the man page is:
"You are not on the authorized user list for the terminal."
So my question: Where is the authorized terminal list? I thought that's what /etc/securettys did?
Thanks.
I have a Sun workstation at my desk that I used to administer the servers in the data center. From the Sun login screen, I can choose Options -> Remote Login -> Enter Host Name and enter the name of a Tru64 box on the LAN.
If I connect as a non-root user, I authenticate and run a CDE session just like I was at a local graphics terminal. If however, I try the same thing as root, I get the error message serving as the title to this thread.
Here is what I have done so far.
1) I know my root account works because I can ssh into the box via putty with no problems.
2) I have verified that there is a ptys
as well as an entry for my workstation in /etc/securettys.
After reading the man page for login(1), I found that my exact error message is addressed. The reason according to the man page is:
"You are not on the authorized user list for the terminal."
So my question: Where is the authorized terminal list? I thought that's what /etc/securettys did?
Thanks.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 03:11 AM
тАО03-13-2007 03:11 AM
Solution
Is this a 'trusted' setup?
>> If I connect as a non-root user, I authenticate and run a CDE session just like I was at a local graphics terminal.
Good check. Now do a 'who' and see how your workstation is reported. Simple nodename? Fully qualified node name? numeric address?
Use that exact syntax in securettys or ttys.
Or fix the name to be as desired (/etc/hosts? /etc/networks?)
>> 1) I know my root account works because I can ssh into the box via putty
So that suggests that /etc/securettys is in place with the ptys entry operational. Good.
>> After reading the man page for login(1), I found that my exact error message is addressed. The reason according to the man page is:
"You are not on the authorized user list for the terminal
Ah, that text is in a section described with:
"If you have enhanced security installed ..."
So you'll also need to deal with the ttys file.
Here is an online man page for that:
http://btrcx1.cip.uni-bayreuth.de/cgi-bin/manpages/ttys/4
Also, did you check this earlier topic?
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1057838
hth,
Hein van den Heuvel
>> If I connect as a non-root user, I authenticate and run a CDE session just like I was at a local graphics terminal.
Good check. Now do a 'who' and see how your workstation is reported. Simple nodename? Fully qualified node name? numeric address?
Use that exact syntax in securettys or ttys.
Or fix the name to be as desired (/etc/hosts? /etc/networks?)
>> 1) I know my root account works because I can ssh into the box via putty
So that suggests that /etc/securettys is in place with the ptys entry operational. Good.
>> After reading the man page for login(1), I found that my exact error message is addressed. The reason according to the man page is:
"You are not on the authorized user list for the terminal
Ah, that text is in a section described with:
"If you have enhanced security installed ..."
So you'll also need to deal with the ttys file.
Here is an online man page for that:
http://btrcx1.cip.uni-bayreuth.de/cgi-bin/manpages/ttys/4
Also, did you check this earlier topic?
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1057838
hth,
Hein van den Heuvel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 03:31 AM
тАО03-13-2007 03:31 AM
Re: Not authorized for terminal access -- see System Administrator
Fixed.
My problem was that my entry in /etc/securettys was:
hostname.network.tld:0.0
When I log in as my non-root user and run 'who', I see my source connection just listed as:
hostname
So I changed the entry in /etc/securettys to:
hostname:0.0
That still didn't work. I tried dropping the '.0'. So, now my entry looks like:
hostname:0
Now I am able to login just fine.
Thanks for your help!
My problem was that my entry in /etc/securettys was:
hostname.network.tld:0.0
When I log in as my non-root user and run 'who', I see my source connection just listed as:
hostname
So I changed the entry in /etc/securettys to:
hostname:0.0
That still didn't work. I tried dropping the '.0'. So, now my entry looks like:
hostname:0
Now I am able to login just fine.
Thanks for your help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 03:32 AM
тАО03-13-2007 03:32 AM
Re: Not authorized for terminal access -- see System Administrator
Fixed.
My problem was that my entry in /etc/securettys was:
hostname.network.tld:0.0
When I log in as my non-root user and run 'who', I see my source connection just listed as:
hostname
So I changed the entry in /etc/securettys to:
hostname:0.0
That still didn't work. I tried dropping the '.0'. So, now my entry looks like:
hostname:0
Now I am able to login just fine.
Thanks for your help!
My problem was that my entry in /etc/securettys was:
hostname.network.tld:0.0
When I log in as my non-root user and run 'who', I see my source connection just listed as:
hostname
So I changed the entry in /etc/securettys to:
hostname:0.0
That still didn't work. I tried dropping the '.0'. So, now my entry looks like:
hostname:0
Now I am able to login just fine.
Thanks for your help!
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