I've got an odd problem. Our library needs certain ports open on our
firewall - we're using ISA 2K.
When I create a protocol rule to open those specific ports, it doesn't work.
When I open the firewall completely, it works. When I open all ports except
the ones in question, it works.
The protocol is Z39.50 - apparently it's used quite a bit in library
applications.
I've looked at our protocol rules - everything seems in order. And other
libraries have their firewall configured in this fashion.
Weird Port Problems - Opening and Closing ... When I create a protocol rule to open those specific ports,... When I open the firewall completely, ...libraries have their firewall configured in this fashion. ... (microsoft.public.isa.configuration)
Re: Ports getting hammered? ... >>> If your Watchguard can't stop outbound traffic...... >>> Would not the Windows XP firewall do exactly the same work? ... >> protocol analysis to see if protocols are being broken only a IDS ... > permitted ports and protocols. ... (comp.security.firewalls)
Re: MS Netmeeting pass through ... When Microsoft developed NetMeeting 3.0 they chose to use the existing ... h.323 video conferencing protocol.... NetMeeting uses DYNAMIC PORTS instead ... Putting a web server behind a firewall means opening a single small ... (comp.security.firewalls)
router rules ... i am very new to firewall concepts.... allow always if destination port=443 & protocol = tcp ... looked up a port list of protocols and allowed them via destined ports.... (Security-Basics)
[fw-wiz] UNSUBSCRIBE ... (Paul D. Robertson) ... > fixup protocol icmp error... >> isn't about the security properties of the control, ... errors in the firewall, configuration errors, and it then takes physical ... (Firewall-Wizards)
