Password expire issue over ssh

[Daryl Much]

Hi, I am somewhat new to HP-UX. We are running HP-UX 11.11. Here is a brief synopsis of what is occurring.

A user whose password age in expired used putty to open a session with the server. They get prompted for a user name and hit enter. Then they the get a banner message and the prompt for a password. The user types the password and BAM a window with putty fatal error pops up saying server unexpectedly closed network connection.

Any ideas is much appriciated.

[Avinash20]

How about telnet/rlogin.
Did you try to login via Reflection-X etc.

Why I am saying is to eliminate the issue from putty software

[Daryl Much]

Ok, so it is not Putty, I tried to login vi -Exceed-X and it did the same thing:

Connection to someserver closed by remote host.
Connection to someserver closed.

[Avinash20]

This is the issue with Login Retries.

The t_maxtries in the /tcb/files/auth/system/default file applies only to terminals and modems connected to a serial or mux card.

The u_maxtries in the /tcb/files/auth/system/default file specifies the maximum number of consecutive unsuccessful login attempts to the account
that are permitted until the account is locked.

To change either from the command line you would run the following. You can verify that it's been changed by doing a more on the default file. There are no man pages for either of these commands.

1) For t_maxtries:
Example:
/usr/lbin/modprterm -m tmaxtries=5

2) For u_maxtries:
Example:
/usr/lbin/modprdef -m umaxlntr=5

From SAM's help screen for t_maxtries:
Unsuccessful Login Tries Allowed

When someone attempts to log in and gives an incorrect login name or password, the attempt fails. The person trying to log in may be an authorized regular system user who forgot the account password, or an unauthorized person attempting to break into the system by trying various login names and passwords. Setting a hard limit on the number
of failed login attempts through a terminal or modem device provides a degree of protection against attacks by unauthorized users of that device as well as a highly visible means of discovering such attacks so
they can be traced. Of course, locking a port due to login errors is inconvenient for other users who need access to that terminal or modem, so a reasonable balance between user convenience and system security is important.

Use this field to specify the maximum number of login attempts allowed, on a given terminal or modem port, system-wide, by typing the desired value in the field labeled Unsuccessful Login Tries Allowed. Use the [Back space] and the right- and left-arrow keys to correct any typographical errors.

NOTE: The login tries limit applies only to terminals and modems connected through a serial interface card or MUX. It does not provide protection against attacks through LAN connections being accessed from remote
systems.

[Mel Burslan]

In which case, where do you get the information of password expiration as the subject of your message indicates ? Are *YOU*, not the user, able to login to the system via ssh and using putty ? Or is this a problem for everyone trying to login via ssh ?

Also,if you are able to login to the system, try to run this command and watch the live output while the user is attempting his login process:

tail -f /var/adm/syslog/syslog.log

you might notice the reason why the server is unexpectedly closing the connection. It might be due to numbe of things.