Solved

Connection Time Out - LINUX

Posted on 2011-02-25
6
459 Views
Last Modified: 2012-05-11
Hello Experts
I login to my server via putty. After exactly 180 sec I cannot access the server via putty as it gives me
"Network Error: Software connection abort". So where in the server should this be set. I am running RHEL4

-Steve
0
Comment
Question by:mnis2008
6 Comments
 
LVL 9

Expert Comment

by:jeremycrussell
ID: 34980978
Is it after 180 seconds idle, or will it disconnect after 180 seconds whether the connection is idle or not?
0
 
LVL 5

Expert Comment

by:balasundaram_s
ID: 34981605
Goto 'Putty configuration' --> 'connection' and change the value

"Seconds between keep alives" - 15 or 60 or any value ( 15 seconds or 60 seconds ).

This would prevent putty being closed by firewall due to being inactive.  

If the Linux server is configured with the TMOUT like below:

export TMOUT=180 ( it might be configured in the profile)

Then, the client sessions gets terminated being inactive for 180 seconds.

0
 

Author Comment

by:mnis2008
ID: 34983104
I dont have the TMOUT variable set. I think its something to do with the SSH configurations. I tried to change the putty configuration but it didnot work also one more strange thing.

When I open putty and give my DMZ server name its takes couple of sec to show the login and after typing my login it takes couple sec for the password....

Once I am in the server command executions are fast....

-Steve
0
VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

 
LVL 2

Expert Comment

by:maxalarie
ID: 34983283
Probably an  iptable rule that drops the connection after 180 seconds.

Can you  post the output of
iptables -L -n ?
0
 

Author Comment

by:mnis2008
ID: 34983332
Yes, Here is the output

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain RH-Firewall-1-INPUT (2 references)
target     prot opt source               destination
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           icmp type 255
ACCEPT     esp  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     ah   --  0.0.0.0/0            0.0.0.0/0
ACCEPT     udp  --  0.0.0.0/0            224.0.0.251         udp dpt:5353
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:631
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:631
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:5600
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:10010
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:10011
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:10012
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:10013
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:10014
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:10015
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:14141
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:20012
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:22
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:21
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited
0
 
LVL 2

Accepted Solution

by:
maxalarie earned 500 total points
ID: 34983441
I dont see any timouts. But you're accepting all ip adresses to log on your server..

I saw here: http://ocaoimh.ie/how-to-fix-ssh-timeout-problems/

that maybe it is set in your ssh config file.

Check your   /etc/ssh/sshd_config, and what  is the value of this parameter: ClientAliveInterval  ?
0

Featured Post

Master Your Team's Linux and Cloud Stack

Come see why top tech companies like Mailchimp and Media Temple use Linux Academy to build their employee training programs.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Rate limit for DNS queries 7 84
Penetration Testing home based work 3 91
Linux VM 6 101
parallel rsync issues with Ubuntu 1 26
Daily system administration tasks often require administrators to connect remote systems. But allowing these remote systems to accept passwords makes these systems vulnerable to the risk of brute-force password guessing attacks. Furthermore there ar…
Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question