Trial and error. I'd start with making sure sshd is running on the
target machine. Usually (depending on distro),
# /etc/init.d/sshd status
will tell if it's running or not. If it's not running,
# /etc/init.d/sshd start
should start it up, but only until the next reboot. The method of making
it persistent depends on the distro.
Josef Lowder wrote:
> So how do I determine which is the problem
> and how do I fix or get around that?
>
> On 10/23/08, Eric Shubert <ejs@shubes.net> wrote:
>> Josef Lowder wrote:
>> > Well, I think I'm finally getting closer, now that I understand
>> > what the actual syntax should look like with real data in it.
>> > This is what I tried:
>> >
>> > $ scp /home/joe/mydata/track2 joe@192.168.1.66:/home/joe/mydata/track2
>> >
>> > That seemed to almost work ... except I got this reply:
>> >
>> > ssh: connect to host 192.168.1.66 port 22: Connection refused
>> > lost connection
>> >
>> > So why would that connection be refused, and how do I fix that?
>>
>>
>> Either a firewall is blocking port 22, or sshd isn't running on the
>> target machine?
>>
>>
>> --
>> -Eric 'shubes'
>>
--
-Eric 'shubes'
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)