Telnet session disconnects abruptly Post: 302951679

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

telnet session timeout

hi, we can set something such that if the user has been idle for a while, it will auto disconnect. where to do so? thanks

2. Shell Programming and Scripting

Telnet session does not expire

Dear friends.. Our project has a module that runs on handheld devices. Through the handheld we telnet to solaris where the application actually runs. I noticed that after starting a session through the handheld, if i go out of range or if i remove and replace the battery in the handheld, the...

3. Shell Programming and Scripting

Telnet Session

{ sleep 2 echo "$user" sleep 2 echo "$password" sleep 2 echo " ls" sleep 10 echo "exit" }| telnet $server I have a machine x and i have executed the above script on machine 'x'. i entered the...

4. UNIX for Dummies Questions & Answers

Unix Telnet session

Hi Is there any way whilst in a telnet session you can view your client machine name that you are using to connect to the Unix box ? :eek:

5. AIX

aix telnet disconnects

We're having problems getting disconnected from AIX with our telnet sessions. I can't ping the server when this happens, either. Other serves can be pinged at the same time. This happens both at unix and within the database. Database locks remain when editing files. unix logins remain after...

6. UNIX for Dummies Questions & Answers

Telnet Session to AIX

Hello, I have AIX 5.3 at home connected to netgear router. Port Forwarding has been enabled on the router. Problem is that if I want to telnet, I have to try 2 or 3 times before I can get a logon prompt. It times out for first or second time (Connection to session <IP_Address> failed: Connection...

7. AIX

Telnet disconnects on handheld device AIX

I have intermec handheld device which is connecting to AIX Server on port 12431 or whatever. ( oracle application ) The handheld device connects for few seconds and then disconnects from the AIX server. Once it disconnects the handheld device automatically switches off. Are there any...

8. HP-UX

ssh session getting hung (smilar to hpux telnet session is getting hung after about 15 minutes)

Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also?

9. Solaris

How do I keep an X session alive when my VPN/ssh disconnects so I can reconnect later?

Hi, Sorry if this question has been asked before, however, I have tried looking in the forum (and google in general) and I haven't found an answer, so I thought I'd ask here. I am trying to use a GUI application in Solaris 10. Normally I connect with a VPN then SSH and use Xming to...

LEARN ABOUT DEBIAN

emp_hub

emp_hub(6)							   Games Manual 							emp_hub(6)

NAME

       emp_hub - Empire multiplexer

SYNOPSIS

       emp_hub [-persistent] [-debug] [-help] [-mirror] host port localport

DESCRIPTION

       emp_hub	allows	multiple  clients  to  simultaneously  connect to a single Empire country.  This allows you to use both a fast and a smart
       client simultaneously.  It also permits multiple corulers to log in at once.

   Parameters
       host	   Hostname of the upstream server.

       port	   TCP/IP port number the empire server is running on.

       localport   TCP/IP port number the emp_hub should listen to for incoming client connections.

       -mirror	   Copy commands and replies to all clients using new protocols.  Currently only the lafe client  is  aware  of  these	protocols,
		   though most clients will ignore them.

       -persistent Normally  emp_hub  exits  after  the  last  client  disconnects.  With this option emp_hub does not exit, and will wait for new
		   clients to connect.	emp_hub must be killed by the user using the kill command.

       -help	   Brief usage information.

       -debug	   Print lots of messages, including everything sent and received by a client.	Useful when debugging either emp_hub ,	a  client,
		   or the server.

SEE ALSO

       emp_server(6), emp_client(6), emp_hub(6), pei(6), eif(6), http://www.empire.net/~harmless/guide.html, http://empire.idlpaper.com/

BUGS

       Due  to	the  nature  of  the empire protocol, only one client may have input focus at one time.  If a client pauses at a context sensitive
       prompt from the server, all other clients will be unable to send data.

AUTHOR

       This manual page was written by Drake Diedrich <Drake.Diedrich@anu.edu.au>

																	emp_hub(6)