Unable to register DNS when the systems are directly connected to the internet if ISA 2004 client is installed
Posted on 2008-10-07
Setup: Windows Domain
Server: 2003 RC2 Std (With AD, DNS, ISA 2004)
Clients: Win XP (desktop and Laptop)
Internal IP range: 10.82.4.x
Internet: Leased line, connected directly to Win Server on 2nd NIC., Shared thru ISA Server 2004 with FWC installed on all clients except a few laptops. Those few laptops have the gateway as this server.
Those laptops with the FWC installed, when taken outside office premises and connected onto a different ISP for internet, gets connected, but the DNS still points to the office Win server (private IP). Hence, the IPs do not get resolved and cannot browse except if you know the IP addresses. The laptops ping to all public IP. There is no change even when the FWC is uninstalled. The ipconfig/all shows the public DNS servers of the dialup connection but the nslookup points to the office DNS (10.82.4.4). Corruption is ruled out as all the laptops with FWC are in the same situation.
Those laptops where the FWC was never installed, work fine on the above scenario.