• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 278
  • Last Modified:

copy files to linux

i have a linux server and sun solaris wks (old version). i need to copy one complete file system from solaris to my linux server. both are in the same network.

i tried rsync but it was giving connection refused error.

the objective is to keep a backup of that particular solaris filesystem in linux server. solaris hardware is very old which i have.
0
kurajesh
Asked:
kurajesh
  • 6
  • 5
  • 3
  • +3
4 Solutions
 
Milind KoyandeCommented:
Did you checked firewall or ACL (hosts.allow) on Linux system?
0
 
kurajeshSenior Systems AnalystAuthor Commented:
i just checked the cd/root/.sshd and vi known_hosts, deleted all entries and restarted sshd service. but still same error while oding rsync (connection refused)
0
 
Milind KoyandeCommented:
Can you please provide the screenshot or paste the complete error. Also what is in the logs of Linux Server?
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
kurajeshSenior Systems AnalystAuthor Commented:
iam attaching the screenshot herewith
Untitlederror.png
0
 
Robert SaylorSenior DeveloperCommented:
Port 22 is being blocked. Turn your Linux firewall off or by any change is the port to SSH something other then port 22? If so, pass the proper port number in the rsync command.

I think it's '-P xxxx'
0
 
kurajeshSenior Systems AnalystAuthor Commented:
the linux firewall is already off and port 22 is for ssh alone.
0
 
Robert SaylorSenior DeveloperCommented:
when you try to connect with rsync have another SSH open on the other server and tail /var/log/messages and post what comes over.
0
 
MazdajaiCommented:
Can you post the output of the following in plain text-

ssh -vvv 192.10.10.1
traceroute 192.10.10.1

Open in new window

0
 
Milind KoyandeCommented:
what is the output of telnet

telnet 192.10.10.1 22

Open in new window

0
 
kurajeshSenior Systems AnalystAuthor Commented:
login as: root
root@192.168.0.213's password:
[root@aaddev ~]# ssh -vvv 192.10.10.1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.10.10.1 [192.10.10.1] port 22.
debug1: connect to address 192.10.10.1 port 22: Connection refused
ssh: connect to host 192.10.10.1 port 22: Connection refused
[root@aaddev ~]#
[root@aaddev ~]# traceroute 192.10.10.1
traceroute to 192.10.10.1 (192.10.10.1), 30 hops max, 40 byte packets
 1  192.10.10.1 (192.10.10.1)  0.157 ms * *
[root@aaddev ~]#

telnet 192.10.10.1 22
Trying 192.10.10.1...
telnet: connect to address 192.10.10.1: Connection refused
telnet: Unable to connect to remote host: Connection refused
[root@aaddev ~]# telnet 192.10.10.1
Trying 192.10.10.1...
Connected to 192.10.10.1 (192.10.10.1).
Escape character is '^]'.


able to connect to 192.10.10.1 through telnet (not with 22)
0
 
Robert SaylorSenior DeveloperCommented:
Post your sshd.conf file. Looks like you will have to goto local console to get it.
0
 
Robert SaylorSenior DeveloperCommented:
Also try flushing iptables
0
 
MazdajaiCommented:
Can you post the following from the server?

netstat -ant

Open in new window

0
 
serialbandCommented:
If you're ssh'ing to root, or using root for ssh, you need to make sure that you don't have.

PermitRootLogin no

in
/etc/ssh/sshd_config

Set it to yes.
PermitRootLogin yes
0
 
kurajeshSenior Systems AnalystAuthor Commented:
#ListenAddress 0.0.0.0
#ListenAddress ::

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 768

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
SyslogFacility AUTHPRIV
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6

#RSAAuthentication yes
#PubkeyAuthentication yes
#AuthorizedKeysFile     .ssh/authorized_keys

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
PasswordAuthentication yes

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
GSSAPIAuthentication yes
#GSSAPICleanupCredentials yes
GSSAPICleanupCredentials yes

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication mechanism.
# Depending on your PAM configuration, this may bypass the setting of
# PasswordAuthentication, PermitEmptyPasswords, and
# "PermitRootLogin without-password". If you just want the PAM account and
# session checks to run without PAM authentication, then enable this but set
# ChallengeResponseAuthentication=no
#UsePAM no
UsePAM yes

# Accept locale-related environment variables
AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#ShowPatchLevel no
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no
#ChrootDirectory none

# no default banner path
#Banner /some/path

# override default of no subsystems
Subsystem       sftp    /usr/libexec/openssh/sftp-server
[root@aaddev ssh]# more sshd_config
#       $OpenBSD: sshd_config,v 1.73 2005/12/06 22:38:28 reyk Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options change a
# default value.

#Port 22
#Protocol 2,1
Protocol 2
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 768

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
SyslogFacility AUTHPRIV
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6

#RSAAuthentication yes
#PubkeyAuthentication yes
#AuthorizedKeysFile     .ssh/authorized_keys

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
PasswordAuthentication yes

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
GSSAPIAuthentication yes
#GSSAPICleanupCredentials yes
GSSAPICleanupCredentials yes

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication mechanism.
# Depending on your PAM configuration, this may bypass the setting of
# PasswordAuthentication, PermitEmptyPasswords, and
# "PermitRootLogin without-password". If you just want the PAM account and
# session checks to run without PAM authentication, then enable this but set
# ChallengeResponseAuthentication=no
#UsePAM no
UsePAM yes

# Accept locale-related environment variables
AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#ShowPatchLevel no
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no
#ChrootDirectory none

# no default banner path
#Banner /some/path

# override default of no subsystems
Subsystem       sftp    /usr/libexec/openssh/sftp-server
[root@aaddev ssh]#
puttylog
0
 
Robert SaylorSenior DeveloperCommented:
Try turning x11 forward off and change the port to 222 then open that port. Then try ssh on port 222 instead of 22
0
 
MazdajaiCommented:
As mentioned, you have to make sure the ports are listening -

netstat -ant
0
 
kurajeshSenior Systems AnalystAuthor Commented:
i will update the results asap
0
 
bigtone58Commented:
You need to check what your version of ssh has for the default setting of "PermitRootLogin". I think it is defaulting to "no" as the lines in your /etc/ssh/sshd_config file are commented out (the hash at the beginning of the line) as below.

#PermitRootLogin yes

You should take the hash off the line to activate the explicit setting of the parameter and restart the ssh daemon.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

  • 6
  • 5
  • 3
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now