<html><head></head><body>It's been a very long time since I have seen a Linux distro enable telnetd to allow telnet connections proper. Test using telnet to the nut port number ("telnet xxx.yyy.zzz.kkk portno") and see if that connects, or try somethhing like ssh . . . <br><br><div class="gmail_quote">On February 17, 2022 11:39:41 AM CST, William Cole via Nut-upsuser <nut-upsuser@alioth-lists.debian.net> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr"><div>Thank you all for your offerings. Here are some results. All were run on the Pi server [235] except the change to the firewall setting which was run on the Mint machine.<br></div><div><br></div><div><i>sudo netstat -lntp</i></div><div><i>Active Internet connections (only servers)</i></div><div><i>Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name<br></i></div><div><i>tcp 0 0 <a href="http://0.0.0.0:22">0.0.0.0:22</a> 0.0.0.0:* LISTEN 501/sshd</i></div><div><i>
tcp 0 0 <a href="http://0.0.0.0:631">0.0.0.0:631</a> 0.0.0.0:* LISTEN 28384/cupsd</i></div><div><i>
tcp 0 0 <a href="http://0.0.0.0:445">0.0.0.0:445</a> 0.0.0.0:* LISTEN 1011/smbd <br></i></div><div><i>
tcp 0 0 <a href="http://0.0.0.0:3493">0.0.0.0:3493</a> 0.0.0.0:* LISTEN 499/upsd
</i></div><div><i>
tcp 0 0 <a href="http://0.0.0.0:139">0.0.0.0:139</a> 0.0.0.0:* LISTEN 1011/smbd</i></div><div><i>
tcp6 0 0 :::22 :::* LISTEN 501/sshd
</i></div><div><i>
tcp6 0 0 :::631 :::* LISTEN 28384/cupsd
</i></div><div><i>
tcp6 0 0 :::445 :::* LISTEN 1011/smbd</i>
</div><div><i>
tcp6 0 0 :::139 :::* LISTEN 1011/smbd
</i></div><div><i>
tcp6 0 0 :::00 :::* LISTEN 530/apache2</i></div><div><br></div><div>and the second output:</div><div><br></div><div><i>sudo iptables -L -n -v</i></div><div><i>Chain INPUT (policy ACCEPT @ packets, 0 bytes)</i><i><br></i></div><div><i> pkts bytes target prot opt in out source destination<br></i></div><div>
<div><i>Chain FORWARD (policy ACCEPT @ packets, 0 bytes)<br></i></div><div><i> pkts bytes target prot opt in out source destination</i></div>
</div><div><i>
</i><div><i>Chain OUTPUT (policy ACCEPT @ packets, 0 bytes)<br></i></div><div><i> pkts bytes target prot opt in out source destination</i></div>
</div><div><br></div><div>As to firewalls, the Mint 20 that handles Linux network devices uses <i>Gufw</i>. <br></div><div>The Windows networked devices use<i> Windows Defender's</i> built-in firewall.</div><div><br></div><div>I added port 23 for telnet to the Gufw firewall and restarted the Mint machine and both of the Pis. Then ran:<br></div><div><br></div><div><i>sudo telnet 192.168.1.236</i> from the 235 Pi</div><div><i>sudo telnet 192.168.1.235</i> from the 236 Pi</div><div><br></div><div>Result in both cases:</div><div><br></div><div><i>Trying 192.168.1.xxx ...</i></div><div><i>telnet: Unable to connect to remote host: Connection refused</i>.<br></div><div><br></div><div>If it makes a difference, all the devices are tied together with Plume mesh network devices which are connected to FiOS.<br></div><div><br></div><div>Bill<br></div><div><br></div><div>-- </div><div><br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><font face="arial,sans-serif">Fredericksburg, VA</font><br></div></div></div></div>
</blockquote></div><div style='white-space: pre-wrap'><div class='k9mail-signature'>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</div></div></body></html>