Sponsored Content
Top Forums UNIX for Advanced & Expert Users Unable to ssh to remote server Post 302882982 by fpmurphy on Friday 10th of January 2014 08:54:47 AM
Old 01-10-2014
You need to talk to your system administrator and get permission to do a network login.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

SSH Remote Server issue

I have a script that connects to remote servers using a public key. Some of the servers are not set up for the public key and I receive the following when I attempt to ssh: The authenticity of host 'XXX' can't be established. RSA key fingerprint is... (1 Reply)
Discussion started by: la_womn
1 Replies

2. Solaris

unable to ssh to remote host

server is ok, I can login on console. however, when I use SSH teachia, there is no repsond. i have check ps-ef | grep ssh, it shows ok. restart ssh too. still not working. Anything else I need to check? # ps -ef | grep ssh root 24706 1 0 Jun 12 ? 0:00... (7 Replies)
Discussion started by: uuontario
7 Replies

3. Red Hat

Unable to SSH into machine - ssh_exchange_identification: Connection closed by remote host

For a few days now I have been experiencing issues when trying to SSH into 1 of my machine. I get the following output when running 'ssh -vvv': server1:/home/mymadq> ssh -l root -vvv server2 OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 debug1: Reading configuration data /etc/ssh/ssh_config... (3 Replies)
Discussion started by: jaapar
3 Replies

4. Solaris

unable to sftp to a remote server from Unix machine

Hi, I get the below when i try to sftp to a remote server $ export SOCKS5C_CONFIG=~/.ssh/socks5c.conf $ sftp -v -s /usr/lib/sftp-server -oPort=2222 -oIdentityFile=~/.ssh/wm_privat> Connecting to ftp01.wmgruppe.de... Sun_SSH_1.1.3, SSH protocols 1.5/2.0, OpenSSL 0x0090704f debug1:... (1 Reply)
Discussion started by: Bigbee
1 Replies

5. Red Hat

unable to connect remote server using ssh

hi all i am unable to connect remote server using ssh but i am able to ping the server ssh service is running. (5 Replies)
Discussion started by: nikhil kasar
5 Replies

6. HP-UX

Unable to ssh to server in HP-UX.

Hello Experts, I'm Unable to ssh to server after killing few processes on /opt filesystems. Can you please help me to resolve this. (3 Replies)
Discussion started by: purushottamaher
3 Replies

7. Shell Programming and Scripting

Unable to check if file exists on remote server using expect

Hi, I need to check if a file exists on remote server using expect. #!/bin/bash ip_addr=10.10.10.10 user=root passwd=Help filename=/root/test expect -c " spawn ssh -n -T -o NumberOfPasswordPrompts=3 -o StrictHostKeyChecking=no $user@$ip_addr expect \"*?assword:*\" send --... (6 Replies)
Discussion started by: temp_user
6 Replies

8. AIX

Unable to ssh or login to AIX server

We are having occasional problems accessing some AIX servers. When this happens we cannot ssh to the server in question or login via HMC console terminal window. We can ssh some commands to the server and get responses but other commands just hang, ssh serverA date returns the date, ssh serverA... (5 Replies)
Discussion started by: Kierong
5 Replies

9. Shell Programming and Scripting

Multi server access through remote server using ssh

Team, Presently I have 5 ip address kept in ip_abc1 file, for each of the ip address listed, i need to login on each ipaddress one at a time and login as below for that specific ip address ssh -p 8101 karaf@<ip.address_for the specific ip address as logged in> password features:list... (4 Replies)
Discussion started by: whizkidash
4 Replies

10. Shell Programming and Scripting

Unable to ssh and list files in local directory from remote.

#!/bin/bash script_work_dir="/home/websys/TEST_dpi_42_file_trnsfer_engine/PORT22/script_work_area" script_config_dir="/home/websys/TEST_dpi_42_file_trnsfer_engine/PORT22/script_config" dpi_sourceServerList=$script_config_dir"/dpi_sourceServerList" dpi_srvr_42="rtm@1.1.1.1"... (8 Replies)
Discussion started by: sadique.manzar
8 Replies
talk(1) 						      General Commands Manual							   talk(1)

Name
       talk, otalk - talk to another user

Syntax
       talk person [ttyname]

       otalk person [ttyname]

Description
       The command is a visual communication program which copies lines from your terminal to that of another user.

       If  you	wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on another
       host, then person is of the form :
       host!user
	or
       host.user
	or
       host:user
	or
       user@host
       The form user@host is perhaps preferred.

       If you want to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal name.

       When first called, it sends the message
       Message from TalkDaemon@his_machine...
       talk: connection requested by your_name@your_machine.
       talk: respond with: talk your_name@your_machine

       to the user you wish to talk to. At this point, the recipient of the message should reply by typing
       talk  your_name@your_machine

       It doesn't matter from which machine the recipient replies, as long as his login-name is the same.  Once communication is established,  the
       two parties may type simultaneously, with their output appearing in separate windows.  Typing Ctrl-L will cause the screen to be reprinted,
       while your erase, kill, and word kill characters will work in talk as normal.  To exit, just type your interrupt character; then moves  the
       cursor to the bottom of the screen and restores the terminal.

       Permission to talk may be denied or granted by use of the mesg command.	At the outset talking is allowed.  Certain commands, in particular
       and disallow messages in order to prevent messy output.

       In order to use the program with machines on your network that may be running earlier versions of ULTRIX, you must initiate a session  with
       the  command (/usr/ucb/otalk) instead of the command You must also respond to a request from a machine running an older version of the pro-
       gram with the command. See the Restrictions section.

Examples
       The following example demonstrates how to use the command.  In this case, user1, whose system (system1) is running ULTRIX V2.2 initiates  a
       session with user2, whose system (system2) is running ULTRIX V3.0.  User1 types the following:
       system1> talk user2@system2
       The following message appears on the screen of user2:
       Message from Talk_Daemon@system2 at 12:37 ...
       talk: connection requested by user1@system1.
       talk: respond with:  otalk user1@system1
       To establish the connection user2 follows the instructions from the Talk_Daemon and types the following at the system prompt:
       system2> otalk user1@system1

Restrictions
       The  version  of  released  with ULTRIX V3.0 uses a protocol that is incompatible with the protocol used in earlier versions. Starting with
       ULTRIX V3.0, the program communicates with other machines running ULTRIX, V3.0 (and later), and machines running 4.3  BSD  or  versions	of
       UNIX based on 4.3 BSD.

       The command is not 8-bit clean. Typing in DEC Multinational Characters (DECMCS) causes the characters to echo as a sequence of a carets (^)
       followed by the character represented with its high bit cleared. This limitation makes unusable if you want to communicate using a language
       which has DECMCS characters in its alphabet.

Files
       to find the recipient's machine

       to find the recipient's tty

See Also
       mail(1), mesg(1), who(1), write(1), talkd(8c)

																	   talk(1)
All times are GMT -4. The time now is 04:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy