Re: identifying my LInux machine on my LAN

On 2/17/21, Marc Auslander wrote: > Paul Scott writes: > >> >>ssh and Bitvise still fail t o connect >> >>Paul > /var/log/auth.log may show what's happening if the request gets that far. I started to respond to this thread the other day then signed me out when I tried to save my answer as a dra

Re: identifying my LInux machine on my LAN

Paul Scott writes: > >ssh and Bitvise still fail t o connect > >Paul /var/log/auth.log may show what's happening if the request gets that far.

Re: identifying my LInux machine on my LAN - some success

On 2/17/21 10:03 AM, IL Ka wrote: paul@Joy4:~/music/pima$ systemctl status ssh`` ● ssh.service - OpenBSD Secure Shell server   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)   Active: active (running) since Tue 2021-02-16 11:53

Re: identifying my LInux machine on my LAN

> > > paul@Joy4:~/music/pima$ systemctl status ssh`` > > ● ssh.service - OpenBSD Secure Shell server > Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor > preset: enabled) > Active: active (running) since Tue 2021-02-16 11:53:13 MST; 21h ago > Docs: man:sshd(8) >

Re: identifying my LInux machine on my LAN

On 2/16/21 1:07 PM, IL Ka wrote: systemctl status ssh`` paul@Joy4:~/music/pima$ systemctl status ssh`` ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2021-02-16 11:5

Re: identifying my LInux machine on my LAN

> > > paul@Joy4:~$ sudo iptables -L > [sudo] password for paul: > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source

Re: identifying my LInux machine on my LAN

On 2/16/21 11:57 AM, Paul Scott wrote: On 2/16/21 10:50 AM, Kenneth Parker wrote: On Tue, Feb 16, 2021, 11:56 AM IL Ka > wrote: Check that * connection is not blocked by firewall: ``sudo iptables -L`` paul@Joy4:~$ sudo iptables -L [sudo] password

Re: identifying my LInux machine on my LAN

On 2/16/21 10:50 AM, Kenneth Parker wrote: On Tue, Feb 16, 2021, 11:56 AM IL Ka > wrote: Check that * connection is not blocked by firewall: ``sudo iptables -L`` paul@Joy4:~$ sudo iptables -L [sudo] password for paul: Chain INPUT (policy ACCEPT) tar

Re: identifying my LInux machine on my LAN

On 2021-02-16 16:49, Paul Scott wrote: My LAN used to have 1 or two computers and/or debices and my Debian Linux machine on it.  I used to be able to log in either on the LAN from my wife's Windows computer or from outside the LAN with my Debian laptop with ssh or Windows machines on which I had

Re: identifying my LInux machine on my LAN

On Tue, Feb 16, 2021, 11:56 AM IL Ka wrote: > Check that > * connection is not blocked by firewall: ``sudo iptables -L`` > * your ssh is listening for port 22: ``ss -l -t`` > * your ip address is correct: ``ip addr`` > I would add: Check if openssh-server is installed. > > On Tue, Feb 16, 2021

Re: identifying my LInux machine on my LAN

Check that * connection is not blocked by firewall: ``sudo iptables -L`` * your ssh is listening for port 22: ``ss -l -t`` * your ip address is correct: ``ip addr`` On Tue, Feb 16, 2021 at 7:50 PM Paul Scott wrote: > My LAN used to have 1 or two computers and/or debices and my Debian > Linux mac

identifying my LInux machine on my LAN

My LAN used to have 1 or two computers and/or debices and my Debian Linux machine on it.  I used to be able to log in either on the LAN from my wife's Windows computer or from outside the LAN with my Debian laptop with ssh or Windows machines on which I had installed putty or Bitvise. I have d