• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 254
  • Last Modified:

Unable to register DNS when the systems are directly connected to the internet if ISA 2004 client is installed

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 ( 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.
  • 2
1 Solution
Is the TCP/IP Properties of the network connection setup to Obtain DNS server addresses automatically?  This is the setting beneath the Obtain IP addresses automatically.  It is possible to get a DHCP IP Address, but not the DHCP DNS servers that way.
BigflicksAuthor Commented:
Yes the setup is as u said
Have you looked through this MS article at all?  It explains the correct way to setup the autodetect settings for ISA 2004 and the FWC.


Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

WEBINAR: GDPR Implemented - Tips & Lessons Learned

Join the WatchGuard team on Thursday, March 29th as we recount some valuable lessons learned in weighing the needs of a business against the new regulatory environment, look ahead at the two months left before implementation, and help you understand the steps you can take today!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now