Sponsored Content
Operating Systems AIX Users Are Getting Kicked out of 2Hr Sessions Post 302128190 by sysgate on Monday 23rd of July 2007 09:56:28 AM
Old 07-23-2007
I'm not sure why you posted this AIX question in Solaris section, maybe a mistake ? Smilie Anyways, I've had this problem before, well, sort of, but I'm not sure whether will help you.
I've been establishing many remote sessions to a servers located outside of our office in VPN environment. After a while, I got disconnected Smilie. I finally found out that it's a firewall issue. To describe my situation, I will use this quote from the net :
Quote:
NAT firewalls like to time out idle sessions to keep their state tables clean and their memory footprint low. Some firewalls are nice, and let you idle for up to a day or so; some are gestapo and terminate your session after 5 minutes.
So I added "ServerAliveInterval 60" into /etc/ssh/ssh_config file, which means that my machine will send keep-alive requests every 60 seconds, thus keeping the connection online.
Once again, I'm not sure if this could be related with your case, but you have to make sure that you've checked firewall configs, and any network related service. Also, did the users noticed being disconnected after exactly 2 hours, or approximately ? This should be clear, because if this is firewall or another network rule, it will be stated somewhere in exact digits, e.g. 3600 secs. Otherwise, if the drops vary at their times, something else is the issue.
HTH.
 

10 More Discussions You Might Find Interesting

1. Programming

C programming sessions

Hey guys, i'm in trouble, i'm high school teacher, and a student ask me for help, he want's to know where he can study C language for his application exam. Somebody could help us? (1 Reply)
Discussion started by: eleia
1 Replies

2. AIX

Locking a file when using VI to prevent multiple-edit sessions by diff users

At the office, we often have to edit one file with VI. We are 4-6 workers doing it and sometimes can be done at the same time. We have found a problem and want to prevent it with a file lock. Is it possible and how ? problem : Worker-a starts edit VI session on File-A at 1PM Worker-b... (14 Replies)
Discussion started by: Browser_ice
14 Replies

3. Solaris

Password accepted but kicked out

The Sun Solaris x86 system seemed to accept my username and password when I do SSH, but then the login prompt went away or hang. What happened? (8 Replies)
Discussion started by: conandor
8 Replies

4. Solaris

Switching between sessions

Unix sys admin in training here and I was performing a rollout of java code. While rolling out my connection to the server was broken. I logged back on to the box and performed a ps -ef | grep 'user' . I could see that session and pid number. My question is was there anyway to resume or... (1 Reply)
Discussion started by: vedder191
1 Replies

5. AIX

Users kicked out after changing their password in an ssh session

Hi I have experienced this for years and just put up with it. However a client of mine now wants to stop this happening to their users. I have scoured the internet but can find no reference to the problem. I tried switching to PAM authentication thinking this might help but it made no... (6 Replies)
Discussion started by: johnf
6 Replies

6. Solaris

To restrict the users not to change the passwords for NIS users

Hi All, How to restrict the NIS users not to change their passwords in for NIS users?? and my NIS user is unable to login to at client location what could be the problem for this ? Any body can help me. Thanks in advance. (1 Reply)
Discussion started by: Sharath Kumar
1 Replies

7. Shell Programming and Scripting

Kill sessions

Hi , I am connecting to the linux redhat machine as user : APPS I would like to know how i can kill -9 , all APPS sessions beside me . Please advice Thanks (2 Replies)
Discussion started by: yoavbe
2 Replies

8. HP-UX

Users getting kicked out of sessions

We have an old (11.11) HP-UX system. A couple of months ago, our customers started having problems with their logins. After sitting idle for roughly an hour, their screens would lock up and they would be kicked out of the system. This happens if they are in the application or on the command... (2 Replies)
Discussion started by: slkdnichols
2 Replies

9. Shell Programming and Scripting

Create multiple users with individual passwords to users

hi, i am new to shell scripts i write a shell script to create multiple users but i need to give passwords to that users while creating users, command to write this script (1 Reply)
Discussion started by: DONFOX
1 Replies

10. AIX

Telnet sessions stay as idle users

Hi The telnet sessions stay as idle users. It is not getting kicked out. Please advise what could be the issue. only when we reboot the server these telnet sessions goes. Below is the current output from the server. we rebooted the server three days ago: pmut6:/> uptime 04:21PM... (8 Replies)
Discussion started by: newtoaixos
8 Replies
FINGER(1)						      General Commands Manual							 FINGER(1)

NAME
finger - user information lookup program SYNOPSIS
finger [ -lmsp ] [user [@host] ...] DESCRIPTION
The finger command has two basic output formats providing essentially the same information. The -s option of finger displays the user's login name, real name, terminal name and write status (as a ``*'' after the terminal name if write permission is denied), idle time, login time, office location and office phone number. Idle time is in minutes if it is a single integer, hours and minutes if a ``:'' is present, or days if a ``d'' is present. Login time is displayed as month, day, hours and minutes, unless more than six months ago, in which case the year is displayed rather than the hours and minutes. Unknown devices as well as nonexistent idle and login times are displayed as single asterisks. The -l option produces a multi-line format displaying all of the information described for the -s option as well as the user's home direc- tory, home phone number, login shell, and the contents of the files ``.plan'' and ``.project'' from the user's home directory. If idle time is at least a minute and less than a day, it is presented in the form ``hh:mm''. Idle times greater than a day are presented as ``d day[s] hh:mm''. Phone numbers specified as eleven digits are printed as ``+N-NNN-NNN-NNNN''. Numbers specified as ten or seven digits are printed as the appropriate subset of that string. Numbers specified as five digits are printed as ``xN-NNNN''. If write permission is denied to the device, the phrase ``(messages off)'' is appended to the line containing the device name. One entry per user is displayed with the -l option; if a user is logged on multiple times, terminal information is repeated once per login. The -p option prevents the -l option of finger from displaying the contents of the ``.plan'' and ``.project'' files. Note that some fields may be missing, in either format, if information is not available for them. If no operands are specified, finger will print an entry for each user currently logged into the system. If no options are specified, fin- ger defaults to the -l style output if operands are provided, otherwise to the -s style. User is usually a login name; however, matching will also be done on the users' real names, unless the -m option is supplied. All name matching performed by finger is case insensitive. Finger may be used to look up users on a remote machine. The format is to specify a user as ``user@host'', or ``@host'', where the default output format for the former is the -l style, and the default output format for the latter is the -s style. The -l option is the only option that may be passed to a remote machine. SEE ALSO
chpass(1), w(1), who(1), getpwent(3) 4th Berkeley Distribution May 18, 1989 FINGER(1)
All times are GMT -4. The time now is 04:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy