Problem with DNS in Active directory, anyone con help!!!

  • Thread starter Thread starter Whitesnake
  • Start date Start date
W

Whitesnake

Informational 16.2.2006 13:00:40 Capture started
Minor 16.2.2006 13:00:41 Expert: HTTP Slow Response Time (289 ms from
pkt 1), Packet 19 (10.168.1.10, 10.168.1.103)
Minor 16.2.2006 13:00:41 Expert: Slow Server Response Time (499 ms from
pkt 8), Packet 63 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:41 Expert: Slow Server Response Time (485 ms from
pkt 64), Packet 84 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:42 Expert: Slow Server Response Time (499 ms from
pkt 85), Packet 138 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:42 Expert: Broadcast Storm, Packet 176
Minor 16.2.2006 13:00:42 Expert: Slow Server Response Time (500 ms from
pkt 139), Packet 177 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:43 Expert: Slow Server Response Time (485 ms from
pkt 178), Packet 192 (10.168.1.234, 10.168.1.10)
Major 16.2.2006 13:00:42 Expert: DNS Server Error (Server Failure),
Packet 151 (10.168.1.10, 10.168.1.3)
Major 16.2.2006 13:00:42 Expert: DNS Server Error (Server Failure),
Packet 153 (10.168.1.10, 10.168.1.50)
Minor 16.2.2006 13:00:43 Expert: Slow Server Response Time (469 ms from
pkt 193), Packet 214 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:44 Expert: Slow Server Response Time (499 ms from
pkt 215), Packet 239 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:44 Expert: Slow Server Response Time (485 ms from
pkt 240), Packet 245 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:45 Expert: Slow Server Response Time (486 ms from
pkt 246), Packet 296 (10.168.1.234, 10.168.1.10)
Major 16.2.2006 13:00:44 Expert: DNS Server Error (Server Failure),
Packet 248 (10.168.1.10, 10.168.1.3)
Major 16.2.2006 13:00:44 Expert: DNS Server Error (Server Failure),
Packet 250 (10.168.1.10, 10.168.1.50)
Minor 16.2.2006 13:00:45 Expert: Slow Server Response Time (499 ms from
pkt 297), Packet 326 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:46 Expert: Slow Server Response Time (500 ms from
pkt 327), Packet 331 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:46 Expert: Slow Server Response Time (485 ms from
pkt 332), Packet 352 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:47 Expert: Slow Server Response Time (469 ms from
pkt 354), Packet 374 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:47 Expert: Slow Server Response Time (427 ms from
pkt 375), Packet 383 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:48 Expert: Slow Server Response Time (432 ms from
pkt 384), Packet 422 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:48 Expert: Slow Server Response Time (485 ms from
pkt 423), Packet 450 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:49 Expert: Slow Server Response Time (499 ms from
pkt 451), Packet 457 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:49 Expert: Slow Server Response Time (485 ms from
pkt 458), Packet 467 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:50 Expert: Inefficient Client, Packet 480
(10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:50 Expert: Slow Server Response Time (500 ms from
pkt 468), Packet 480 (10.168.1.234, 10.168.1.10)
Minor 16.2.2006 13:00:50 Expert: Inefficient Client, Packet 488
(10.168.1.234, 10.168.1.10)
 
In Whitesnake <[email protected]> stated, which I commented on below:

Hard to tell. Why? First of all, the limited info you provided, second of
all, it can depend on a number of things, such as configuration, what's
running in terms of services and apps, bad NIC or driver, spyware, viruses,
switch misconfigured, bad switch port, bad NIC port, bad wire, etc. It could
be due to numerous issues and can't tell with the limited info you provided.

Perform a perfmon log for a few hours if it's that bad, selecting the four
basic objects, and if there are any servicse or apps running, add those
objects to the log as well and see if there's any correlation between a lack
of bandwidth and high CPU usage and what app is running.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.

Not sure how? It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.

The only thing in life is change. Anything more is a blackhole consuming
unnecessary energy.
===========================
 
Back
Top