On 03/12/2018 23:12, Samuel Sieb wrote:
On 12/3/18 1:25 PM, John Pilkington wrote:
'systemctl start sshd' and 'ssh john@192.168.1.66' gives me the
expected prompt.
Make sure you do "systemctl enable sshd" as well if you want to be able
to use it after your next reboot. "systemctl enable --n
On 12/3/18 1:25 PM, John Pilkington wrote:
'systemctl start sshd' and 'ssh john@192.168.1.66' gives me the
expected prompt.
Make sure you do "systemctl enable sshd" as well if you want to be able
to use it after your next reboot. "systemctl enable --now" is a
shortcut to enable and start th
On 12/3/18 1:07 PM, John Pilkington wrote:
> On 03/12/2018 19:19, Rick Stevens wrote:
>> On 12/3/18 10:16 AM, John Pilkington wrote:
>>> On 03/12/2018 17:30, Rick Stevens wrote:
On 12/3/18 8:15 AM, John Pilkington wrote:
> Hi: I have two boxes connected to the same router. One runs SL7.5
On 03/12/2018 20:08, Samuel Sieb wrote:
On 12/3/18 8:15 AM, John Pilkington wrote:
I can ssh and rsync from F28 to SL7, but permission is denied in the
opposite direction. Port 22 is open. I now have copies of both
versions of /etc/sshd and intend to examine diffs.
We would need the exact e
On 03/12/2018 19:19, Rick Stevens wrote:
On 12/3/18 10:16 AM, John Pilkington wrote:
On 03/12/2018 17:30, Rick Stevens wrote:
On 12/3/18 8:15 AM, John Pilkington wrote:
Hi: I have two boxes connected to the same router. One runs SL7.5,
from tomorrow probably SL7.6, which is an el7 clone, and
On 12/3/18 2:47 PM, Tom Horsley wrote:
> ssh -v -v -v user@remote
>
> Is often a good command to use. It tells you everything
> it is trying so you can see what all it failed on.
>
> I've never had any problems with CentOS 7 and new fedora
> systems though. They talk to each other just fine for me.
On 12/3/18 8:15 AM, John Pilkington wrote:
I can ssh and rsync from F28 to SL7, but permission is denied in the
opposite direction. Port 22 is open. I now have copies of both
versions of /etc/sshd and intend to examine diffs.
We would need the exact error message to give you a good answer.
On 12/3/18 11:46 AM, Tom Horsley wrote:
> ssh -v -v -v user@remote
>
> Is often a good command to use. It tells you everything
> it is trying so you can see what all it failed on.
>
> I've never had any problems with CentOS 7 and new fedora
> systems though. They talk to each other just fine for
ssh -v -v -v user@remote
Is often a good command to use. It tells you everything
it is trying so you can see what all it failed on.
I've never had any problems with CentOS 7 and new fedora
systems though. They talk to each other just fine for me.
Some very very old systems are trying to use depre
On 12/3/18 10:16 AM, John Pilkington wrote:
> On 03/12/2018 17:30, Rick Stevens wrote:
>> On 12/3/18 8:15 AM, John Pilkington wrote:
>>> Hi: I have two boxes connected to the same router. One runs SL7.5,
>>> from tomorrow probably SL7.6, which is an el7 clone, and the other runs
>>> Fedora 28.
>>
On 03/12/2018 17:30, Rick Stevens wrote:
On 12/3/18 8:15 AM, John Pilkington wrote:
Hi: I have two boxes connected to the same router. One runs SL7.5,
from tomorrow probably SL7.6, which is an el7 clone, and the other runs
Fedora 28.
I can ssh and rsync from F28 to SL7, but permission is deni
On 12/3/18 8:15 AM, John Pilkington wrote:
> Hi: I have two boxes connected to the same router. One runs SL7.5,
> from tomorrow probably SL7.6, which is an el7 clone, and the other runs
> Fedora 28.
>
> I can ssh and rsync from F28 to SL7, but permission is denied in the
> opposite direction. P
12 matches
Mail list logo
