Nut upsuser - Feb 2022 - NUT Client Not Working, Server OK

On Wed, 16 Feb 2022, William Cole via Nut-upsuser wrote:
> I ran telnet on both machines:
> ?? First from the server [235] to the client [236]
> ?? Then from the client [236] to the server [235]
> 
> The result in both cases:
> ?? Trying 192.168.1.xxx
> ?? telnet: Unable to connect to remote host: Connection refused.
This makes it clear that the problem is not with nut, but rather the basic 
setup of network 192.168.1/24   Google proposes plenty of help for Connection 
refused, but start with command

  netstat -lntp

For example, I see

  Active Internet connections (only servers)
  Proto Recv-Q Send-Q Local Address   Foreign Address  State   PID/Program name
  tcp        0      0 0.0.0.0:22      0.0.0.0:*        LISTEN  832/sshd
  ...
  tcp        0      0 0.0.0.0:3493    0.0.0.0:*        LISTEN  3066/upsd

Roger

On Wed, Feb 16, 2022 at 10:40 AM Roger Price <roger at rogerprice.org>
wrote:
>
> On Wed, 16 Feb 2022, William Cole via Nut-upsuser wrote:
>
> > I ran telnet on both machines:
> >    First from the server [235] to the client [236]
> >    Then from the client [236] to the server [235]
> >
> > The result in both cases:
> >    Trying 192.168.1.xxx
> >    telnet: Unable to connect to remote host: Connection refused.
>
> This makes it clear that the problem is not with nut, but rather the basic
> setup of network 192.168.1/24   Google proposes plenty of help for
Connection
> refused, but start with command
>
>   netstat -lntp
>
> For example, I see
>
>   Active Internet connections (only servers)
>   Proto Recv-Q Send-Q Local Address   Foreign Address  State   PID/Program
name
>   tcp        0      0 0.0.0.0:22      0.0.0.0:*        LISTEN  832/sshd
>   ...
>   tcp        0      0 0.0.0.0:3493    0.0.0.0:*        LISTEN  3066/upsd
I'm going to guess there's a default firewall in place on these
machines...