12-09-2007
I assume in this case we are deailing with a terminal concentrator of some kind. Usually they have an admin option available to disconnect/reset a connection on a given port. We have ~100 terminal concentrators here and they all ( several different brands ) have this option.
9 More Discussions You Might Find Interesting
1. Programming
Hello Experts,
Happy New Year to all of us,
In AIX 4.3.3 I am trying to figure out how is possible to find out the IP address that a telnet session - user uses to login in to host machine. My objective is by finding the login IP address to allow the user to login or not.
All users uses the... (6 Replies)
Discussion started by: sszago
6 Replies
2. UNIX for Dummies Questions & Answers
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 (6 Replies)
Discussion started by: yls177
6 Replies
3. Shell Programming and Scripting
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... (1 Reply)
Discussion started by: deepsteptom
1 Replies
4. Shell Programming and Scripting
{
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... (6 Replies)
Discussion started by: pathanjalireddy
6 Replies
5. UNIX for Dummies Questions & Answers
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: (2 Replies)
Discussion started by: mlucas
2 Replies
6. UNIX for Dummies Questions & Answers
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... (1 Reply)
Discussion started by: bluebee
1 Replies
7. Shell Programming and Scripting
I'm looking at allowing remote telnet into my server.
like any security-minded administrator, I want to log what my users type on the telnet session.
I'm using the script command to generate transcripts of the users session.
I have /etc/profile set to automatically start the script command... (2 Replies)
Discussion started by: ramnet
2 Replies
8. HP-UX
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? (1 Reply)
Discussion started by: yoda9691
1 Replies
9. Solaris
Hi,
I would appreciate some help.
I remotely access, across a VPN, an M5000 and when I connect to the XSCF I can then access the OS using console -d0 and then I can get to the console.
The problem I have is that I need to run something which will take many hours and I can't run it in the... (6 Replies)
Discussion started by: giles.cardew
6 Replies
LEARN ABOUT ULTRIX
rlogind
rlogind(8c) rlogind(8c)
Name
rlogind - remote login server
Syntax
/etc/rlogind
Description
The server is used for the program. The server provides a remote login facility with authentication based on privileged port numbers.
The server is invoked by when it receives a connection on the port indicated in the login service specification. For further information,
see When a service request is received, the following protocol is initiated:
1. The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection.
2. The server checks the client's source address and requests the corresponding host name. If the hostname cannot be determined, the dot-
notation representation of the host address is used.
Once the source port and address have been checked, allocates a pseudo terminal and manipulates file descriptors so that the slave half of
the pseudo terminal becomes the stdin, stdout, and stderr for a login process. For further information, see
The login process is an instance of the program, invoked with the option. The login process then proceeds with the authentication process
as described in but if automatic authentication fails, it reprompts the user to log in on a standard terminal line.
The parent of the login process manipulates the master side of the pseudo terminal, operating as an intermediary between the login process
and the client instance of the program. In normal operation, the packet protocol described in is invoked to provide ^S/^Q type facilities
and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and terminal type, as
found in the environment variable, TERM. For further information see
The screen or window size of the terminal is requested from the client, and any changes in the window size from the client are sent to the
pseudo terminal.
Restrictions
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but it is
useful in an open environment.
Diagnostics
All diagnostic messages are returned on the connection associated with the stderr, after which any network connections are closed. An
error is indicated by a leading byte with a value of 1.
Hostname for your address unknown
No entry in the host name database existed for the client's machine.
Try again
A fork by the server failed.
/bin/sh: ...
The user's login shell could not be started.
See Also
rlogin(1c), inetd(8c)
rlogind(8c)