Control Unit Problems... -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hi Folks,

 

We are using Perle 494 control units connecting over a frame relay network
and they are connected via TCP/IP (Ethernet card in each controller).

 

We have been having trouble with Nachi (the Port 135 and Port 445 nightmare)
so we have put ACL's (Access Control Lists) on our routers. They are all the
same and here is what one looks like:

 

Extended IP access list 130

    deny icmp any any echo

    deny icmp any any echo-reply

    deny tcp any any eq 4444

    deny udp any any eq tftp

    deny tcp any any eq 707

    deny tcp any any eq 135 

    deny tcp any any eq 137

    deny tcp any any eq 138

    deny tcp any any eq 139

    deny tcp any any eq 193

    deny tcp any any eq 445

    deny tcp any any eq 593

    deny tcp any any range 666 765

    permit ip any any

 

well if a control unit fails it will NOT attach again. We found that
removing the ACL it would pop RIGHT back up. So something in this is
blocking something the Perle needs. Does any have any idea what port(s) the
Perle is using ? PC's that are attached at each site and connect through the
router are FINE so it is something to do the ACL and the Perle.

 

Thanks in advance !

 

Chuck

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.