· SecureNAT :
It is a LAT host (the client has an IP address configured in the Local Network).In a simple Network, SecureNAT Client has a unique route (default gateway) to the Internet via ISA server, and receives the Default Gateway which is the IP address of ISA server Internal NIC.In a more complex network it may be slightly different, SecureNAT Clients will receive the Default Gateway which is the Interface of the Router behind the ISA server, and the task of these Routers is to point to Internal Interface on ISA.
· Firewall:
As well as being a LAT host, installing the software ISA Firewall client , enabled and the client applications will use it later.
· Web Proxy :
Configured simply through an Application (IE or other Web browsers such as Netscape ., or web-enabled applications) such as Yahoo Messenger, etc., on LAT host use sent proxy requests to the Outbound web listener on ISA server to the Internet.
Configure ISA Server:
It is important that ISA server is properly configured to serve different types of ISA Client.If ISA Server has difficulty resolving the Client to find a Hostname, or accessing Internet services, all Clients can be affected.Repeat the tests for ISA Server during the installation and configuration process, to make sure ISA Server is properly configured.Thus, changes in the configuration parameters will be strictly verified, and if there are mistakes, it will be easy to return to the original state.
· Outgoing Web Requests Listener:
Function as a Web proxy.The Web proxy service (w3proxy) request must be active, Outbound Web Requests Listener must be configured and enabled.See and change this parameter, open ISA Management MMC , open Servers and Arrays,. Right-click and select Properties . Click Outgoing Web Requests tab.
By default ISA Server enables Proxy service on all internal IP IPs (in the previous examples, 192.168.1.200 and 127.0.0.1 (this is for ISA Server if it wants to become a Web Proxy Client of the Web Proxy Service itself). works on it ), at port 8080, this default setup of Proxy service is not related to the operation of other ISA Server modes such as Firewall, Integrated, Cache. To disable the Outgoing Web Requests listener, simply select Configure listeners individually per IP address and do not select any IP addresses for this.
· Auto Discovery listener : This is one of the "problems" for people who love ISA server, when they want to run IIS (web server) on ISA Server itself, even if IIS only uses Internal IPs.See the picture you will see
In this situation, we have 2 applications / services ( WPAD functions and IIS Web service ) for Clients on the same TCP Port, a competition occurs and any of these 2 Services may be 'disadvantaged'.Essentially TCP Port 80 is opened on ISA Server to provide ISA Client with Automatic Discovery (WPAD functionality, which means automatically detecting parameters to connect to Web Proxy Service or ISA firewall Service), but descriptions above will cause Admin to wonder a bit when using this feature.
If you do not want Auto Discovery, do not check Publish automatic discovery information .Thus Port 80 will be freed for Internal IPs on ISA Server
Note:ISA Server in Web proxy server mode only uses 1 NIC (Cache Mode)
· Site and Content Rules :
The rules set out here control the content related to HTTP and FTP when they move to Web Proxy Service (for example, when ISA Clients access 1 HTTP site, Site and Content rules are set.) Rules will look at whether the ISA clients' requests are valid, if valid for the content as well as the destination, the request will be forwarded to the Web Proxy service and to the Internet….) By default Site and Content Rules Prohibit any content (Audio, image, video, applications, compressed file .), and any Site when requesting to send to the Internet. By default, Allow rules are set.If you want to prevent Website / FTPsite Admin from executing Deny here, please set it correctly, otherwise it will be "closed down" all.
· Protocol Rules :
One of the hubs of ISA Server.Enabling LAT hosts (Internal Clients) access Internet resources through rules here .The figure below defines a lot of Protocols that allow LAT hosts to use.For example, if I do not create a rule marked with red, my LAT hosts will not be able to access HTTP Sites.
· IP Routing :
The next issue is to ensure that all traffic flows SecureNAT Clients are not blocked (of course, the rules in Protocol rules above must allow this).The default ISA Server is disabled 'Enable IP Routing' . When Enable New ISA Server allows ICMP (pings) from LAT to Internet.
Open ISA Management MMC , find IP Packet Filtering . Right-click, select Properties and you'll see the picture
See more information Enable IP Routing at: http://support.microsoft.com/kb/q279347/
· HTTP Redirector :
This is where the Admin can control ISA Firewall Clients and SecureNAT Clients when these Clients require Web access.Open ISA Management MMC, select Servers and Arrays , Extensions , Application Filters . Right-click the Redirector Filter HTTP , select Properties . Select Options Admin tab will see as shown in Figure
So here, the Admin can determine how the SecureNAT & Firewall client's Web access requests will be controlled (Note: Normally SecureNAT clients and ISA Firewall Clients will work directly with the ISA Firewall Service for all requests to access all Internet services, but except for HTTP / FTP-Web requests, HTTP Redirector will transfer to Web Proxy service.
In the image above you also see the setting ' If the local service is unavailable .', this setting means that when Web Proxy Service on ISA Server does not work, transfer Web requests directly to the Web Server ' redirect requests to Requested Web Server 'This is convenient for SecureNAT and Firewall clients who still have access to the Internet without considering Web Proxy filtering which is NO ANSWER REQUESTS .
If Admin checks the Send to requested Web Server , SecureNAT and Firewall Clients bypass the Web proxy service for all Web requests, at all times.
However, check here will ignore all Proxy parameters set on IE / Netscape browser of Firewall and SecureNAT clients.
If check Reject HTTP requests from Firewall and SecureNAT clients, the Firewall and SecureNAT clients must set up Web proxy settings at the browser if they do not want to be banned from all Web requests.
· Local Domain Table :
Table identifies Internal Domains.This is key information for both IE and Firewall client.Any domain name given and this table 1 of 2 possibilities can occur as follows:
If Web Proxy and Firewall clients use a DNS server to find the name, they will pass this DNS server to resolve without the related ISA service.
Web Proxy clients will make requests directly to any Server in that Domain, bypassing ISA proxy services.
Note: Also prompt the Admin, to avoid the case that DNS cannot distinguish what is accessing the Internet domain and where to access the internal domain, when creating an Internal Domain to avoid using formats like Internet Domain For example, congty.com may be different instead: int.Domain.tld (here I set the domain name very specifically for my organization : Int.Domain with .tld instead of the current .com / net / edu / org on the Internet)
· Name Resolution :
Determine the correct IP parameters for ISA server absolutely important At least, Admin must provide a DNS server for ISA Server so that ISA can resolve Internet Servers for Web Proxy and Firewall clients, and should also provide it to ISA An internal DNS server serves the Internal Network, if the Network is a Domain.ISA Server 2000 installs on Windows server 2000, and W2K Server is recommended by default to use DNS as the only name query solution, rather than using solutions that may cause headaches for later Administrators such as WINS ( NETBIOS name resolution), and how to resolve the 'classic' name NETBIOS Broadcast.ISA Server provides a solution to find DNS names for itself by creating a DNS Lookup Packet Filter .The Admin should not Desabled this function, because otherwise ISA Server may not correctly resolve Internet DNS names
Proxy Web Proxy and Firewall DNS cache :
Web Proxy and Firewall services on ISA server provide a very basic DNS name resolution solution based on the TCP / IP settings that Admin has configured on the Network Card of ISA server. This basic function will address requests to search for Internet hostnames for Web and Firewall clients. The mechanism to keep resolved DNS names (DNS Name Cache) of ISA server is quite interesting, the existence time of cached DNS records (Time to Live of DNS Records) does not depend on the rules from the remote The DNS server that ISA server sends requests to resolves, that TTL has been specified by ISA server for Web Proxy and Firewall DNS caches has a total duration of 6 hours . This is different from the working mechanism of DNS caching servers , these DNS servers when transferring the request to resolve names to other DNS servers, the TTL of the records is cached on it, depending on the TTL from the DNS servers. plays the role of a query solver and is merely storing (caching) what has been found by another DNS server.Administrators want to refer to the parameters of the DNS name cache mechanism of Web Proxy service and Firewall Service on ISA server.Use the REGEDIT command at the RUN menu and search for entries as follows
Web Proxy:
HKLMSOFTWAREMicrosoftFpcArrays {Array GUID} ArrayPolicyWebProxy
" msFPCDnsCacheSize " = dword: 00000bb8
" msFPCDnsCacheTtl " = dword: 00005460
Firewall :
HKLMSOFTWAREMicrosoftFpcArrays {Array GUID} ArrayPolicyProxy-WSP
" msFPCDnsCacheSize " = dword: 00000bb8
" msFPCDnsCacheTtl " = dword: 00005460
WWW.NEWHORIZONS.COM (New Horizons Computer Learning Centers)
Ho Viet Ha
Training Manager
My Website ( NIS.COM.VN - N etwork Network I have an ecurtiy, My Website Coming soon)