I have installed ISA server as a Firewall within my small network basically to test out it's possibilities which I could later on apply at my custommers.
I have set-up the configuration on a network with 3 pc's; the ISA Server is directly connected to the Internet ... all the rules I have set-up work perfectly on the 2 other pc's on the network ... but somehow I'm not able to get the ISA Server to use these rules.
I have for example set-up a rule to allow my private IP range to connect to a pop3 server and download new mail ... this works fine for the 2 pc's in the network, but not for the ISA Server itself!
Could anyone explain me why this is the case and how I can resolve this?
which setting do I have to specify on the "Local Computer" Tab of my custom packet filter:
This Filter applies to: a. default ip address(es) on the external interface b. the ISA server's external IP address c. this computer (on the perimeter network) d. these computers (on the perimeter network)
and ... do I need to stop and start the service for this filter to start working?
Tnx in advance,
quote:Originally posted by tshinder: Hi QwiQ,
For applications that are run on the ISA Server itself, you must create packet filters that will allow access for the application that connect to Internet resources.
For example, if you want to allow the ISA Server itself to communicate with a POP3 Server, you would configure the following packet filter:
Type: Custom IP Protocol: TCP Direction: Outbound Local Port: Dynamic Remote Port: Fixed Port Remote Port Number: 110
You would need to configure similar packet filters for other applications/protocols that need access from the ISA Server itself.