I have an ISA setup as our gateway to the internet and i am trying to use the web publishing feature but i am having a few problems with it. When i try and access an internal web server from the actual ISA server it cannot find the page, therefore the web publishing for that site doesnt work. Does anybody have any idea why the ISA cannot access the internal web pages. Both the ISA and the web server can see and access each other e.g. through file shares/ping etc.. but just cant access the actual web page.
The ISA has two network cards in, one internal and one external
172.16.0.10 IP Address
NO Default Gateway
172.16.0.1 Primary DNS
172.16.0.3 Secondary DNS
External - DETAILS SUPPLIED BY LEA
10.15.80.14 IP Address
10.15.3.254 Default Gateway
10.15.250.160 Primary DNS
10.15.250.161 Secondary DNS
Every thing else seams to work internet access is fine, its just accessing the internal web servers and web publishing that im having problems with
Originally Posted by mattstevenson2005
You should not use DNS servers on the external NIC but instead configure forwarders to point to your ISP's DNS servers on your internal DCs to answer or relay the DNS queries.
You will need an access to to allow DNS protocol from your internal DC (the one with the forwarders set) to external or your ISP's DNS server.
Believe me it will solve a lot of other problems that you have not encountered yet.
Thanks for the answer, im not quite sure what you mean. Because of the way our internet is supplied by the local council our internal DCs cannot 'see' any 10.15 address. We use the ISA to NAT all traffic from the 10.15 network to our internal network. I already have a forwarder setup to point to an external DNS server on our main DC which is also our primary DNS server
Thanks, i have worked it out. It was because the default web chaining rule was forwarding all requested up to the upstream LEA proxy and not resolving local addresses internally LOL my fault