Sponsored Content
Full Discussion: linux login issue
Operating Systems Linux Red Hat linux login issue Post 302690305 by thmnetwork on Wednesday 22nd of August 2012 07:55:05 PM
Old 08-22-2012
Couple things could be happening:

1) The host could be having name resolution issues. You can verify this by testing DNS with "host yahoo.com" and seeing how fast it gets back to you and by testing user name resolution by seeing how long "getent passwd" takes to get back.

2) Putty could be trying Kerberos authentication, that can slow down how long it takes to get in. You'll usually see an "Access Denied" message before you put in your password if it's trying that.

3) If the delay happens after you've entered your username/password, it may be a filesystem delaying your entry into the home directory, I would see that's the case by doing a "df -h" once you get in.

I would also check /var/log/messages and /var/log/secure for the times around when you're logging into the machine to see if anything relevant is getting printed.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Unix Login Issue

Guys .. I got my user ID created in a production system of my organisation. the problem I got is my HOME directory in environment has been mis-spelt. Like: I should be logging into unix using ID: freakegs My home directory should be : /users/freakygs and echo $HOME should also... (1 Reply)
Discussion started by: freakygs
1 Replies

2. Solaris

Login Issue

Hi, I am not able to login in the system as user.It is showing problem login as: User1 User1@10.xxx.xx.xx's password: Could not chdir to home directory /home/User1: No such file or directory Sun Microsystems Inc. SunOS 5.9 Generic May 2002 $ I have created the User1 and Its... (8 Replies)
Discussion started by: smartgupta
8 Replies

3. Solaris

login issue in solaris5.6

Hi, I have reset the account on solaris 5.6. After resetting, User unable to login and putty gets closed once enter the password. Please suggest ASAP..... Thanks in Advance (6 Replies)
Discussion started by: bpsunadm
6 Replies

4. Linux

How to find remote Linux box login account without login in to that box?

Hi, How to find remote Linux box login account without login in to that box? I don't have login account at my remote Linux box. But I need who are all having login account. How do I findout? Thanks, --Muthu. (3 Replies)
Discussion started by: Muthuselvan
3 Replies

5. Linux

Login issue

Hi, I have created one normal login id . When they have try to login then, They got error msg the permission denied. Please advice on this. Thanks, Mani (3 Replies)
Discussion started by: Mani_apr08
3 Replies

6. UNIX for Dummies Questions & Answers

sudo login issue

I logged in through ssh, but can't re-login as root. sudo login Arch login: root Password: Login incorrect Arch login: But I am sure my password is right. Why? But on local tty1, this works. (2 Replies)
Discussion started by: vistastar
2 Replies

7. Solaris

Login issue

Hello, I'm trying to setup my Solaris 10 servers to authenticate from a OpenLDAP server. I can get the Linux servers to authenticate from a OpenLDAP server, but not server the Solaris servers. Below I have posted some output so you can see my issue. <terminal output> -bash-3.00$ id... (5 Replies)
Discussion started by: bitlord
5 Replies

8. Cybersecurity

SSH password-less login issue between linux and solaris

Hello Gurus, I am trying to set up bidirectional password-less login between a linux and a Solaris. The way I am doing is very simple, which is creating pub/priv key pairs on each host and add the pub key to each other's authorized_keys file: ssh-keygen -t rsa (I tried dsa, and it didn't work... (4 Replies)
Discussion started by: error_lee
4 Replies

9. UNIX for Advanced & Expert Users

Intermitent issue with passwordless login

Hi, I have two users login on my HPUX i.e user1 and user2. Inorder to switch from user1 to user2 without password I generated key pair using keygen command for user id user1 and copied the its public key to the .ssh/authorized_keys file of user2. ssh-keygen -b 2048 -t rsa This... (5 Replies)
Discussion started by: mohtashims
5 Replies

10. Red Hat

SSH login issue

Dear All , recently i have configured sftp for a user for which i have done chroot. but after this , sftp is working fine . but ssh is not working when we connect to the server. When we try to ssh <user>@<server ip> , the below is the error message that we get and not able to login. ... (2 Replies)
Discussion started by: jegaraman
2 Replies
PASSWD(1)						    BSD General Commands Manual 						 PASSWD(1)

NAME
passwd, yppasswd -- modify a user's password SYNOPSIS
passwd [-l] [user] yppasswd [-l] [-y] [-d domain] [-h host] [-o] DESCRIPTION
The passwd utility changes the user's local, Kerberos, or NIS password. If the user is not the super-user, passwd first prompts for the cur- rent password and will not continue unless the correct password is entered. When entering the new password, the characters entered do not echo, in order to avoid the password being seen by a passer-by. The passwd utility prompts for the new password twice in order to detect typing errors. The total length of the password must be less than _PASSWORD_LEN (currently 128 characters). Once the password has been verified, passwd communicates the new password information to the Kerberos authenticating host. The following option is available: -l Cause the password to be updated only in the local password file, and not with the Kerberos database. When changing only the local password, pwd_mkdb(8) is used to update the password databases. When changing local or NIS password, the next password change date is set according to ``passwordtime'' capability in the user's login class. To change another user's Kerberos password, one must first run kinit(1) followed by passwd. The super-user is not required to provide a user's current password if only the local password is modified. NIS INTERACTION
The passwd utility has built-in support for NIS. If a user exists in the NIS password database but does not exist locally, passwd automati- cally switches into yppasswd mode. If the specified user does not exist in either the local password database or the NIS password maps, passwd returns an error. When changing an NIS password, unprivileged users are required to provide their old password for authentication (the rpc.yppasswdd(8) daemon requires the original password before it will allow any changes to the NIS password maps). This restriction applies even to the super-user, with one important exception: the password authentication is bypassed for the super-user on the NIS master server. This means that the super-user on the NIS master server can make unrestricted changes to anyone's NIS password. The super-user on NIS client systems and NIS slave servers still needs to provide a password before the update will be processed. The following additional options are supported for use with NIS: -y Override passwd's checking heuristics and forces it into NIS mode. -l When NIS is enabled, the -l flag can be used to force passwd into ``local only'' mode. This flag can be used to change the entry for a local user when an NIS user exists with the same login name. For example, you will sometimes find entries for system ``placeholder'' users such as bin or daemon in both the NIS password maps and the local user database. By default, passwd will try to change the NIS password. The -l flag can be used to change the local password instead. -d domain Specify what domain to use when changing an NIS password. By default, passwd assumes that the system default domain should be used. This flag is primarily for use by the superuser on the NIS master server: a single NIS server can support multiple domains. It is also possible that the domainname on the NIS master may not be set (it is not necessary for an NIS server to also be a client) in which case the passwd command needs to be told what domain to operate on. -h host Specify the name of an NIS server. This option, in conjunction with the -d option, can be used to change an NIS password on a non- local NIS server. When a domain is specified with the -d option and passwd is unable to determine the name of the NIS master server (possibly because the local domainname is not set), the name of the NIS master is assumed to be ``localhost''. This can be overrid- den with the -h flag. The specified hostname need not be the name of an NIS master: the name of the NIS master for a given map can be determined by querying any NIS server (master or slave) in a domain, so specifying the name of a slave server will work equally well. -o Do not automatically override the password authentication checks for the super-user on the NIS master server; assume ``old'' mode instead. This flag is of limited practical use but is useful for testing. FILES
/etc/master.passwd the user database /etc/passwd a Version 7 format password file /etc/passwd.XXXXXX temporary copy of the password file /etc/login.conf login class capabilities database SEE ALSO
chpass(1), kinit(1), login(1), login.conf(5), passwd(5), kerberos(8), kpasswdd(8), pam_passwdqc(8), pw(8), pwd_mkdb(8), vipw(8) Robert Morris and Ken Thompson, UNIX password security. NOTES
The yppasswd command is really only a link to passwd. HISTORY
A passwd command appeared in Version 6 AT&T UNIX. BSD
February 14, 2014 BSD
All times are GMT -4. The time now is 01:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy