Login Incorrect

[aam_1]

Hi friends. Iam trying to enter as user root (and any other user) from cde and using telnet too, but the answer is Login Incorrect.
It allows me to enter the user name but when I enter the password it doesn't display ***. In short it login fails. Is there any way to solve this issue???

Thanks a lot...

[pap]

Hi,
Your problem is $HOME/.dtprofile file.
Open that file and go to the last line of the file.
There is some variable named
SOURCEDTPROFILE=TRUE or 1 I do not remember it correctly.

If this line is commented, please remove it.
If it is not commented then put comment there.

I think your login should work now.,

Thanks,

-Piyush.

[Animesh Chakraborty]

<>>

Hi,
Are you using Hp workstation ?It is normal when it is in screen saver mode.Just type root passwd(it will not show ****)
Hope you are typing correct password :)

[Sanjay_6]

Hi,

Make sure you are not restricted from logging in as root using telnet. It is possible root is allowed to login only from console. From all other points, you can login as some other user and do a su - to change to root. Look for a file /etc/securetty and if the entry console exist in this file, you can login as root only from console.

Hope this helps.

Regds

[harry d brown jr]

In the past 15 years, I've never seen telnet display any asterisks (*) for telnet passwords. Are you talking about the CDE login screen? Are you on a workstation that is locked up? Can you login via telnet from a PC?

live free or die
harry

[Peter Kloetgen]

Hi,

this is absolutely normal behaviour for UNIX- loginscreens. You see what you enter if you insert your username, but for reasons of security you see nothing ( also no asterix ) when you enter your password. The cursor is set to invisible mode when you do so. So don't worry about this fact. If this would not be done, everybody who stands behind you could count the number of characters of your password and UNIX avoids this.

Allways stay on the bright side of life!

Peter

[Alex Glennie]

CDE uses login to authenticate a user and if as you seem to say telnet also fails I don't think this can be just a CDE issue.

I'll assume the caps lock key is not on ;) ...

has this system been trusted ?

can you log into a CDE failsafe session ?

What is the exact syntax of what you see when telneting to the system ?

How long has this been occurring & what has changed recently, system rebooted , installed patches.

What's the O/S and H/W ?

Lastly I'd suggest it might be necessary to bring the system down and change the root passwd at single user mode .... I'd answer the above first though so we know exactly what we're dealing with here .....

[Domenico_5 · Accepted solution]

Hi aam,

If all suggestion doesn't work, is possible that you can have a not correct passwd.

You can reboot the machine, interrupt when you can see the message:"Press any key....".
Write "bo" and after respond Y to the question Interactive?.

When you receive the prompt, write hpux -is.

after boot, you can do mount -a and vi /etc/passwd.

In this way you can control if this file is correct

[John Carr_2]

Hi

before you reboot try this:

at the CDE login pick the option for command line login. If you can login do so.

now if logged in do command vipw then exit the password file this will check the password file for errors.

If you cant login try the reboot in single user mode as already outlined

good luick
John.

[K.Vijayaragavan.]

Hi,

Are you able to login using command line login?

If yes,

check the permission for the file /etc/hosts

check the /etc/nsswitch.conf for the name service swithc order or check it in sam.

check the /etc/securetty file.

If no,

boot in single user mode and run sam to check if the account is locked or disabled?

-K.Vijay

[aam_1]

Hi Friends. Thanks for your answers. I am in the system using the comand bo and then hpux -is. I check with sam the file passwd, and is OK. But the problem persist:
login: root
login incorrect
login

And never ask me for the password (in terminal mode).
In CDE I can give the login and then, the password but the message is the same, waht other file I need verify?
Thanks a lot

[K.Vijayaragavan.]

Hi,

Seems to be IP Conflict (Just a thought),there may be a nother system with duplicate IP. If possible disconnect your system from network and try to ping the ip ofyour srever from some other pc / host to find the conflicting system.
-Vijay

[Sandip Ghosh]

boot at single user mode, mount all the filesystem, do a vi on /etc/passwd file and remove the passwd section for root. Then reboot. Now the passwd is null. After rebooting change the password through passwd command.

Sandip

[aam_1]

Ok guys. I take off * from /etc/passwd for user root, and I tried to login and the problem persist.
I disconnect the HP from the Network, and then I made ping from my PC to this IP addres, and not found.
What you thing that is happen?
Thanks

[pap]

Hi aam,
Try to login as another user.
If the problem still persist?

[Patrick Wallek]

Since you have a * in the passwd field, you are on a Trusted system.

It could be a problem with your /tcb directory structure.

What are the permissions on the /tcb and directories below it? What are the permissions for the /tcb/files/auth/r/root file?

What you could try is to un-trust the system. To do this do a:

# /usr/lbin/tsconvert -r

Now try logging in again.

If you want to convert back to a trusted system do:

# /usr/lbin/tsconvert

[Domenico_5]

hi aam

what?? you have take off * from root? i don't understand! if you have an * in passwd would means that this user can't login.

the correct string with no password is:

root::0:3::/:/sbin/sh

have you this??

from console you can login in the system?

and /dev/null must be rw for all check this and send the response

bye.

[aam_1]

Patrick, Pap:
The problem persist with all users.
I untrust the system, and made login: doesnt work.
The directory /tcb not exist.
After untrust the system is ask 3 times for login, and then start in single user mode:
login: user-1
login incorrect
login: user-2
login incorrect
login: root
login incorrect
INIT: SINGLE MODE USER
...

thanks for any help guys

[Patrick Wallek]

Did the /tcb directory structure exist before you untrusted the system?

What does the /etc/passwd file look like now? Can you post a line or 2 from it?

Try running the command 'pwck'. This checks the password file and reports any errors it finds.

[aam_1]

Domenico, after untrust the system, /etc/passwd have some users with * (as adm, lp) and other with the password encrypted.
/dev/null have rw permission for everybody. What other thing I need check?
Thanks a lot.

[Domenico_5]

aam the other users like www lp adm and so on must have *, but from console (serial device or web or lan console),

can you login in the system?

[aam_1]

The command pwck not show any error for passwd file. Here examples in passwd:
root:Foaq/oJXqvh:0:3::/:/sbin/sh
daemon:*:1:5::/:/sbin/sh

I dont know if /tcb exist before untrust the system.
Thanks

[aam_1]

Domenico, I can not login in the system from any part: console, telnet, etc). I only can in single user mode(When start the system pressing key, giving bo, then hpux -is).
Thanks

[Domenico_5]

aam
incredible, sorry for the stupid question, but in /sbin sh exist, correct???

[aam_1]

Yes /sbin/sh exist and have execute permission for everybody. Thanks