I have an IBM x330 with RedHat 7.3 that I recently built that appeared to be working fine, but now I appear to have problem connecting via telnet.
No matter which machine I try to use( I have tried this with SuSE 8.1 and W2K Pro), I cannot log into my RedHat machine via telnet. I can ping my... (2 Replies)
I am trying to find the following information regarding the logging of telnet sessions within a Solaris 10 environment:
(1) How can I tell if the logging of telnet sessions is enabled on a Solaris 10 machine?
(2) Assuming that the logging of telnet sessions is not enabled, what is the... (1 Reply)
Somewhat long story:
I have a simple Perl CGI script that uses Expect to Telnet to a device and grab some data, and then spits it back to Perl for display on the Webpage.
This works for many devices I've tried, but one device just fails, it keeps rejecting the password on this device, only... (1 Reply)
hi,
what is the difference between logging into unix through f-secure ssh client and telnet
is there any more security check is involved
can any one explain
thanks in advance (1 Reply)
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)
Hi I am working in Solaris 10 and I want to monitor logs for every telnet/ssh session that tries to connect to the server. I need these logs to be generated in a file that I can fetch using ftp.
I am a new user and a stepwise detail will be great
BR
saGGee (3 Replies)
hello guys, Does anybody know how I can log all the telnet sessions for a specific IP.
For instance, anybody who make a telnet to IP x.x.x.x this session will be logged. the purpose of it is that I need to know every command that people are running on this node.
Any help ?
Thanks. (1 Reply)
Hi,
My requirement - for security purpose -
I want all root logins to my solaris servers are done by a script kept
in a separate unix box. This script will telnet into remote solaris server with
root user and log every session via log file.
Now my purpose is to log every telnet session... (3 Replies)
I can connect to the UNIX box using a TCP/IP Telnet session but the UNIX does not respond with the login prompt.
The box responds to a PING and the Telnet session actually connects, but no prompt of any sort is recieved back.
I can connect via the console, get the login prompt and can login. ... (3 Replies)
When unlocking a Linux server's console there's no event indicating successful logging
Is there a way I can fix this ?
I have the following in my rsyslog.conf
auth.info /var/log/secure
authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies
LEARN ABOUT HPUX
nstrtel
nstrtel(5) File Formats Manual nstrtel(5)NAME
nstrtel - specifies the number of telnet device files the kernel can support for incoming telnet sessions
VALUES
Failsafe
Default
Allowed values
(Subject to available physical memory.)
It is best to use the default value, and there should not be any need to lower it. However, if the simultaneous telnet connection load is
very high, then the value of could be increased.
Recommended values
(Default value.)
DESCRIPTION
The telnet daemon uses two STREAMS-based pseudo-terminal drivers and The kernel parameter, can be used to tune the number of pseudo-termi-
nals. specifies the number of kernel data structures that are created at system boot time that are required to support the device files
used by incoming telnet sessions on a server. If the command or SAM is used to create more telnet device files, the value of must be
increased accordingly or the device files cannot be used because there are no kernel data structures available for communicating with the
system.
Who Is Expected to Change This Tunable?
Anyone.
Restrictions on Changing
Changes to this tunable take effect at the next reboot.
When Should the Value of This Tunable Be Raised?
When there is an increase in the load of telnet connections and there are no device files available to open telnet connections, then this
kernel parameter should be increased.
When the error is encountered, then the device files have been exhausted and should be raised. Once the value of is raised, should be run
to create new device files. (If SAM is used to raise the value of is run automatically.)
What Are the Side Effects of Raising the Value of This Tunable?
More resources would be consumed. Extra kernel data structures, and extra device files may clog the system.
When Should the Value of This Tunable Be Lowered?
It is not advisable to lower the tunable value from the default value. Consult HP Support before lowering this tunable from the default
value.
What Are the Side Effects of Lowering the Value of This Tunable?
Though not recommended, there would not be any side effects.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
SEE ALSO insf(1M), telnetd(1M), telm(7), tels(7).
Tunable Kernel Parameters nstrtel(5)