Posts: 2
Joined: 7.Nov.2004
From: Lone Tree, CO
Status: offline
We recently uninstalled ISA 2000 and installed ISA 2004 using the Edge Firewall template. With ISA 2000, we were running a VPN with no problems. Now, however, when we attempt to enable a VPN, we cannot resolve external DNS addresses. Internal DNS names are alwaysed resolved, however. The DNS server is on another (internal corporate) domain's DC at 192.168.2.250. The ISA box is a DC in it's own domain at 192.168.2.1. Both boxes run Windows 2000 server standard edition. A one-way trust is established between the corporate (trusted) domain and the firewall (untrusted) domain. The DNS server connects as a sNAT client. Both the external and internal NICs on the ISA box have only the internal AD/DC/DNS entered. The DNS server on the ISA box does not have any forwarders entered. It is a repeatable phenomenom that starting RRAS results in the ISA denying external DNS connections. Stopping RAS fixes the problem. With RAS running, neither the ISA box nor the AD/DC/DNS box resolves outside DNS addresses. I have tried configuring RAS to use DHCP-supplied addresses (DHCP server is on corporate DC) and I have tried giving RAS a static pool of ip addresses. Neither configuration solves the problem.
I have attached ipconfig/all from the ISA box.
Any ideas would be greatly appreciated, as I have spent a week trying to resolve this.
Posts: 2
Joined: 7.Nov.2004
From: Lone Tree, CO
Status: offline
Thanks, Tom, for the quick reply.
The DNS server used for both interfaces is our internal DNS server that does resolve both internal and external addresses. The internal interface is listed first in the Adapters and Bindings list. An access rule for DNS has been created. All works fine until the RAS service is started. With RAS running, connections from external DNS servers are denied by ISA.
We *really* need this resolved as we need to get our VPN up and running.