|
|
Sponsored Content
Operating Systems
HP-UX
Logging into UNIX via TCP/IP Telnet
Post 302811671 by Newnix on Friday 24th of May 2013 01:57:42 AM
05-24-2013
Logging into UNIX via TCP/IP Telnet
Thank you VBE and Macorval,
I am trying to connect as root.
The "DNS problem because reverse traslate" is ringing a bell from a previous issue we had some years back, will persue that.
thanks.
I am trying to connect as root.
The "DNS problem because reverse traslate" is ringing a bell from a previous issue we had some years back, will persue that.
thanks.
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am new to unix. Currently using solaris 6.8 (i think).
I need to telnet into a remote server, and print out a report to a printer near me, that DOES NOT have a printcap set-up for the printer on the remote server. I was hoping to do this via tcp/ip since the printer does have a static ip... (1 Reply)
Discussion started by: gishfarm
1 Replies
2. UNIX for Dummies Questions & Answers
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)
Discussion started by: Jody
2 Replies
3. Solaris
I want to log tcp-wrapper events Solaris 10. I researched and saw that I could make a syslog entry in the hosts.deny, which I did below. After restarting syslog and having ssh blocking, I see nothing logging. I also do not get the email that should be generated. The file was taken from a... (2 Replies)
Discussion started by: csgonan
2 Replies
4. Solaris
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)
Discussion started by: RobSand
1 Replies
5. UNIX for Advanced & Expert Users
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)
Discussion started by: trichyselva
1 Replies
6. 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
7. UNIX for Dummies Questions & Answers
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)
Discussion started by: saggee
3 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I need to log telnet sessions. Therefor i want to use telnets logging function.
UNIX man pages - telnet: unixhelp.ed.ac.uk/CGI/man-cgi?telnet
Like:
telnet -n /path/to/logfile IP PORT
But it doesn't work. The file is created, but it is an emty file after the session.
I've also googled... (2 Replies)
Discussion started by: JaPatton
2 Replies
9. Solaris
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)
Discussion started by: cerioni
1 Replies
10. Solaris
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)
Discussion started by: rahul_jain250
3 Replies
LEARN ABOUT DEBIAN
fence_baytech
fence_baytech(8) System Manager's Manual fence_baytech(8) NAME
fence_baytech - I/O Fencing agent for Baytech RPC switches in combination with a Cyclades Terminal Server SYNOPSIS
fence_baytech [OPTION]... DESCRIPTION
This fencing agent is written for the Baytech RPC27-20nc in combination with a Cyclades terminal server. The Cyclades TS exports the RPC's serial port via a Telnet interface. Other interfaces, such as SSH, are possible. However, this script relies upon the assumption that Telnet is used. Future features to this agent would allow the agent to work with a multitude of different communication protocols such as Telnet, SSH or Kermit. The other assumption that is made is that Outlet names do not end in space. The name "Foo" and "Foo " are identical when the RPC prints them with the status command. fence_baytech accepts options on the command line as well as from stdin. fenced sends parameters through stdin when it execs the agent. fence_baytech can be run by itself with command line options which is useful for testing. Vendor URL: http://www.baytech.net OPTIONS
-a host IP address or hostname to connect to. -h Print out a help message describing available options, then exit. -l login Username name for the switch. -n port The name of the outlet to act upon. -o action The action required. This can be on, off, status or reboot (default) -p password Password for login. -S path Full path to an executable to generate the password for login. -q Quiet mode: print only error messages. -V Print out a version message, then exit. STDIN PARAMETERS
agent = < param > This option is used by fence_node(8) and is ignored by fence_baytech. host = < hostname | ip > IP address or hostname to connect to. login = < param > Login name. action = < param > The action required. This can be on, off, status or reboot (default) passwd = < param > Password for login. passwd_script = < param > Full path to an executable to generate the password for login. outlet = < param > The name of the outlet to act upon. SEE ALSO
fence(8), fence_node(8) fence_baytech(8)