Microsoft, Microsoft ISA 2004, 4.0.3445.887, Microsoft Firewall, The connectivity verifier "Secondary DNS" reported an error when trying to connect to . Reason: The request has timed out.

How is your verifier configured? Do you ping the internal DNS Server or connect to it via port 53. What do you have the time out value on the verifier set to?
If you go to the alerts tab on the Monitoring list how often do you lose connection?

Hi..Thank you for your response.
Here are the details ..

There are 5 connectivity verifiers in total. Two to the DC's, Two to the DNS Servers and one to the SUS server.

The one in discussion now ' Secondary DNS' connectivity verifier has 'Establish a TCP connection' , Connect to port > DNS > 53, specified under 'Select the method used to verify the connection'.

The timeout response threshold is 5000 msec (5 secs).
In 'No Connectivity' alert types, I see loss of connection almost everyday, but at no particular time, it's at random periods of time, but does occur everyday..atleast once..

Thanks in advance

Are you getting ANY other connection verifiers dropping at the same / similar times? The reason I ask is that it may be the DNS Server (service) rather than the ISA Server causing the issue.
If this is the case then it may be that you are looking in the wrong place and the ISA Server is a symptom of an issue with the DNS Server.
I have a series of verifiers (AD, DNS and pings) to various servers and do get the odd drop out on JUST the DNS Server. (not every day though)

Hi,

The other Connectivity verifiers for DC's and WSUS as well face the same problem at the same time. So at the same time I also have 'The connectivity verifier "Domain Controller" reported an error when trying to connect to . Reason: The request has timed out' and also 'The connectivity verifier "WSUS" reported an error when trying to connect to . Reason: The request has timed out.'

Hi Kieran..Thank you for all your help..But the fact remains that the networks team do their regular ping tests etc and generate reports for the switch port where the ISA servers are connected and say that all is OK. But it's been going on since a few days..and I'm not gonna give up until we suppress these alerts. I'll keep this issue open for now before I move onto Networks to see if someone else has any more ideas from ISA perspective.

Thanks

Suspect it is indeed network blips causing this, Since at the time I get these errors, I also get disconnected from my RDP Session on the ISA servers.