Yes. You should not have Internal Gateway in the ISA. Only the external!!
Main Topics
Browse All TopicsHi there all,
I am having a problem with my ISA box in that I continually get Event 14141 for Microsoft ISA Server Web PRoxy (ISA Server has encountered a proxy chain loop.) and then no one can get on the internet. I have just had to install ISA from scratch and the NIC details are as follows:
Internal NIC:
IP Address : 192.168.0.2
Mask: 255.255.255.0
Gateway : 192.168.0.2
Primary DNS: 192.168.0.1 (internal DNS server and Primary DC)
Seconday DNS : 10.0.0.1 (ip of ADSL router)
External NIC
IP Address: 10.0.0.2
Mask: 255.255.255.0
Gateway: 10.0.0.1
Primary DNS: 10.0.0.1
If anyone has any ideas on what would be causing this problem I would greatly appreciate it. The other thing is I cannot nslookup internal computers from the ISA Server. This Server is a member of our domain.
thanks
Darren
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thanks guys. The internal NIC was set to get an IP address automatically so I changed that and I checked the routing table and it had the route entry in there so I will give it today and see if it continues to get the error.
The other thing is that I have a number of internal websites that are published from this server and their IP address internally is 192.168.0.4 (of the server they are on - I use headers in IIS to get to the right site), but from the ISA box when I NS lookup this website I get the external ip address.
So my question is would this cause a proxy chain loop. I do have to send the requests to the 192.168.0.4 server but was wondering whether this would cause the proxy loop problem.
> but from the ISA box when I NS lookup this website I get the external ip address.
1. remove primary DNS on the external NIC. make sure all DNS requests go to internal DC.
2. PING the internal servers from the DC (192.168.0.1) to see if the internal DNS can address the published servers correctly.
3. if necessary, as you have only a few internal sites to be published, use IP numbers instead of domain names, in the relevant ISA settings such as publishing server or defining firewall rules.
hope it helps,
bbao
Business Accounts
Answer for Membership
by: rslangenPosted on 2009-04-22 at 23:20:55ID: 24212181
Your internal network card shouldn't have a gateway in the nic.
Leave that one empty.
Then on the cmd type route print
Then add the route for your internal netwok
In your case this would be
route add 192.168.0.0 mask 255.255.255.0 192.168.0.2 -p
That is if 192.168.0.2 is your gateway, normally this would be 192.168.1.254