[Nut-upsuser] NUT Client Not Working, Server OK

Matus UHLAR - fantomas uhlar at fantomas.sk
Wed Feb 16 16:03:03 GMT 2022

>> 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.

>On Wed, Feb 16, 2022 at 10:40 AM Roger Price <roger at rogerprice.org> wrote:
>> 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*        LISTEN  832/sshd
>>   ...
>>   tcp        0      0*        LISTEN  3066/upsd

On 16.02.22 10:52, Kevin P. Fleming wrote:
>I'm going to guess there's a default firewall in place on these machines...

I guess default firewall on most OSes causes connection timeout, not 

but yes, running "iptables -L -n -v" on the server could help us
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"They say when you play that M$ CD backward you can hear satanic messages."
"That's nothing. If you play it forward it will install Windows."

More information about the Nut-upsuser mailing list