'dnscmd' not reconized
From: Cleve S. (tropchev_at_NOSPAMbellsouth.net)
Date: 02/18/04
- Next message: Joe Ross: "Re: Inability to resolve names across domains"
- Previous message: Joe Ross: "Re: Inability to resolve names across domains"
- Next in thread: Herb Martin: "Re: 'dnscmd' not reconized"
- Reply: Herb Martin: "Re: 'dnscmd' not reconized"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 18 Feb 2004 16:23:10 -0500
I've determined that my DNS servers are suffering from the problem referred
to in KB828731. I ran 'dnscmd /Config /EnableEDnsProbes 0' from the command
prompt. It ran fine from the 1st server and I no longer seem to be getting
the following error.
-------------------------------------------------------
Event Type: Information
Event Source: DNS
Event Category: None
Event ID: 5501
Date: 2/18/2004
Time: 6:29:52 AM
User: N/A
Computer: TROPCHEV06
Description:
The DNS server encountered a bad packet from 10.3.48.252. Packet processing
leads beyond packet length. The event data contains the DNS packet.
-----------------------------------------------------
When I run the same command on the other server I receive this message.
----------------------------------------------------
'dnscmd' is not reconized as an internal or external command operable
program or batch file.
----------------------------------------------------
I see where it adds a new DNS Paramenter DWORD Value of EnableEDnsProbes. I
have to do some maintenance this weekend so I was thinking of adding the new
parameter before I restart. Does anyone think this will work or cause a
problem? Any ideas why the command works on one server & not the other?
Thanks for the ideas.
-- Cleve S.
- Next message: Joe Ross: "Re: Inability to resolve names across domains"
- Previous message: Joe Ross: "Re: Inability to resolve names across domains"
- Next in thread: Herb Martin: "Re: 'dnscmd' not reconized"
- Reply: Herb Martin: "Re: 'dnscmd' not reconized"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
