"Otto Klemperer" <> wrote in message
news:...
> On Tue, 12 Jan 2010 21:19:58 +0000, Jonathan de Boyne Pollard
> <J.deBoynePollard-> wrote:
>
>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
>><html>
>><head>
>> <meta content="text/html; charset=ISO-8859-1"
>> http-equiv="Content-Type">
>></head>
>><body bgcolor="#ffffff" text="#000000">
>><blockquote cite="mid:" type="cite">
>> <p wrap="">problem is i cant ping the dns server from clients and
>>exchange server,database server,isa server.<br>
>>i cannot ping to my default gateway address from any of the servers.<br>
>> </p>
>></blockquote>
>><p>Then your problem is a network connectivity problem, not a DNS
>>problem. Remember that <a
>> href="http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/nslookup-results-different-to-ping.html"><code>ping</code>
>>is not a DNS diagnosis tool</a>.<br>
>></p>
>><blockquote cite="mid:" type="cite">
>> <p wrap="">users cant access there shared folders and emails.<br>
>>some times it connects and run smoothly for 1 to 2 min ,then suddenly
>>it disconnects.<br>
>> </p>
>></blockquote>
>><p>Solve your basic network connectivity problem first, before looking
>>at application problems.
>></p>
>><blockquote cite="mid:" type="cite">
>> <p wrap="">we have got cisco pix firewall,cisco router, all cables
>>are connected to each other,all green lights are blinking. <br>
>> </p>
>></blockquote>
>><p>So the next thing to look at is the layer immediately above the raw
>>physical connections. Check that the operating systems are
>>recognizing
>>the network interface cards. What does Windows NT on the clients and
>>servers report for the network interfaces? Are they up and
>>connected?
>>Once you've ensured that the network interfaces are up and connected,
>>look at the IP addresses being assigned, the subnet masks, and the IP
>>routing tables.<br>
>></p>
>><p>All of this comes <em>before</em> leaping to the conclusion that
>>there is a DNS problem. Remember: <a
>> href="http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/dns-narrow-problem-locus.html">Prove
>>that
>>your
>>problem
>>really is a DNS problem</a>.<br>
>></p>
>></body>
>></html>
>
> I agree, it looks like a basic connectivity issue. That issue could be
> hiding additional issues further up the stack, but fix the
> connectivity first.
>
It could be an ISA firewall client issue, as well. The poster stated that
ping doesn't work, which could simply mean that ICMP is blocked in a policy
for the installed ISA firewall client, or worse, the LAT is incorrect, or
worse, the ISA firewall client policies are misconfigured, which can
snowball into other issues. However there wasn't enough infrastructure
configuration posted other than reported symptoms to ascertain if this is
the issue.
Ace
Ace
|
Similar Threads
Linear Mode
