The ISA server that was configured many times before, whether it is joined to the domain controller or joined the file server, has not had any problems, but recently, after installing the ISA server to the client, it found that the ISA has a "route (chain) error. "The problem is prompted.
Then, after the prompt, the access website cannot be accessed, and the intranet users cannot ping the internal network card of ISA. The ISA local host also cannot ping the internal host. However, the ISA can ping the external network and can resolve to the domain name (the DNS is set to the local host). At the same time, there is such an end in the ISA error message: "ISA Server detected a proxy chain loop. There is a problem with the configuration of the ISA Server routing policy."
Through analysis, it is certainly not a configuration problem inside the server. It must be caused by ISA itself or by conflicts in ISA software. I searched the Internet and found no effective solution to similar cases. It seems that now, only the exclusion method is used to solve the problem.
First, I will delete all ISA policies first, and then add a full-to-all full-open strategy. Then experimented, the problem still exists. Checked that the Routing and Remote Access Service in the service did not find it started (ISA Firewall built-in routing). Checked the DNS settings, IIS settings, there are no problems with settings and conflicts.
In desperation, I chose to reinstall ISA (this time because I did not install it), I suspect that it was a mistake when my colleague installed it. However, the problem remains after reloading.
What is the problem? Look at the problem prompt, it is a routing error. However, I used route print to view the route, which is normal. There are no problems with routing loops.
In the case of feeling that it is going to collapse, suddenly, I seem to feel that something is wrong. After careful inspection, I found the Kabbah icon on the lower right foot. Are they all the faults of Kabbah? Everyone knows that in addition to anti-virus capabilities, Kabbah version 6.0 also has simple port monitoring. Will this monitoring function conflict with the port monitoring of IISA?
It turns out that my idea is right. After all the ports in the port settings on Kabbah are deleted, everything is back to normal. In the same situation, similar problems can occur if the rest of the network firewall or port restriction software is also installed on the ISA. I have not experimented specifically. Interested friends can try it.
Summary: The port monitoring function of the ISA server is already very strong, so it is best not to install the software of the remaining control ports on the server to prevent accidents.
SNMP (Simple Network Management Protocol, simple protocol for server operation and maintenance, serv
Friends who have a certain understanding of the network or server may see FTP related knowledge, and
-E Each packet intercepted shows the link layer header: source MAC address > d
There are already a lot of homes with more than two desktops, and the old machines that have been re
Planning server virtualization should consider the top ten issues
Logging in to the server with a certificate
Configuring Windows Server 2008 Firewall - Allowed to be Ping
How the Data Center Prevents Electrostatic Discharge
An example of IE access to IIS FTP timeout failure
What is the external host channel? The
Failed to deploy the WCF server from the assembly "System.ServiceModel, Version=3.0.0.0 problem
Install IIS 7 on Windows Vista
Connection may not be enabled or the computer is too busy (resolving remote desktops cannot connect)
How to use the calculator with win10 system
How to retrieve the lost search function of Win7 in order to quickly find the file
Smart Win7 system search does not leave traces of history
Win7 Ultimate opens "C:\\Documents and Settings"
TechNet subscribers receive a one-year free Office365
Three small coups of Thunder death to prevent user privacy
Windows XP login password loss response strategy
Netizen measured: Windows 7 compatible online game "Jian Wang 3"