Pre 2k4 build (ISA 2000)

AD domain ------ (internal address: gate = blank) ISA Server(external address : gate = Watchguard)) ------- Watchguard Firewall


AD (ISA as forwarder, recursion) <-------> ISA (Stub zone, do not use recursion, forward ti ISP DNS) <-----------> tEh interweb
     (DHCP hands out ISA as DNS server AD as secondaries)

Ok..Ive been having random connection issues, during logging ive seen some odd thing. on a RARE occasion DNS timeout, and some packets dropped. I think I may have found ouit what it is but was gonna ask before I proceed. For some reason..when I removed ISA 2k and put in 2k4, DNS was uninstalled from the ISA server. So, AD forwards to ISA that it seems does not have DNS anymore. ShouldI just plop DNS back on and reset my stub zone or, since im in the process, should I redo the whole DNS setup or will it matter. I just dont wanna install DNS and have som M'soft knowdge base come up and bite me in the ass
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Keith AlabasterEnterprise ArchitectCommented:
This is just a suggestion but it has worked on all of my ISA installs. I do not use DNS on ISA2004. Ever. (ISA2000 was different of course). I point the internal ISA NIC at the AD DNS servers so that the AD boxes perform the DNS requests on ISA's behalf. ISA2004 is then told to allow DNS to pass out to the ISP dns servers or to a dns server (if you have one) in the DMZ/perimeter.

ISA2004 does not require DNS installed but it does not uninstall DNS so not quite sure what would have happened there.

Let me know if you want more info; I can talk on this for hours.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Tennessee_PrideAuthor Commented:
I just didnt uninstall DNS console didnt like to connect to it. I redid my DNS conbsole on my machine and it worked. I was just all confusified.
So. I could uninstall DNS out if ISA, have the AD boxes do all the resolution (they all point to themselves as primary)...what..just change the forwarders to the external ISP DNS on the AD sytems?
Tennessee_PrideAuthor Commented:
Ok heres how I set it up

                                                              Clients (AD is Primary DNS)
               (self primary DNS, forward ISP)  AD  <-----------------> ISA (AD is primary DNS)
                                                                    <-----------------------------------> Internet

thats how I set it up now. Ill come back with the 411 after it runs for a bit.
Firewall Management 201 with Professor Wool

In this whiteboard video, Professor Wool highlights the challenges, benefits and trade-offs of utilizing zero-touch automation for security policy change management. Watch and Learn!

Tennessee_PrideAuthor Commented:
Im still getting some slowness and seeing entries in logging like this (using my ip as a filter)

8080      http proxy      Closed Connection            0x80074e21 FWX_E_ABORTIVE_SHUTDOWN

also port 8080 denied 0xc0040017 FWX_E_TCP_NOT_SYN_PACKET_DROPPED
and still strange DNS (port 53) timeout me as client and ISA as destination when all I have is AD as my DNS. Ill give it some time and get some user reactions
Keith AlabasterEnterprise ArchitectCommented:
lol, just realised whose post this was; hello again :)

Yes. If you think abot it, ISA has no real reason to need to ask for dns resolution itself. It can use the same DNS resolvers as the clients do; your internal DNS servers.

port 8080 denied 0xc0040017 FWX_E_TCP_NOT_SYN_PACKET_DROPPED

This error is saying that a packet hit the ISA server that was not part of an existing conversation and therefore it was dropped. This can be caused in a number of ways although this is not an exhaustive list by any means....

1. You have set your internal networks in the local lat but not included all of them. For example, the internal lat MUSt be made up of classful subnets  ie you can't have - ISA will then think that and are external and will behave a little peculiarly.

2. ISA is doing its job. In the GUI, select configuration - general - Enable intrusion detection and there are other checks you an enable/disable.

Tennessee_PrideAuthor Commented:
works for me...and..thanks again
Keith AlabasterEnterprise ArchitectCommented:
Welcome :)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software Firewalls

From novice to tech pro — start learning today.

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.