Months ago we moved DHCP to a new server
Thanks for the lead will check it out

-----Original Message-----
From: Bill Monicher [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 13, 2008 9:02 AM
To: NT System Admin Issues
Subject: Re: Errors I have never seen before!!

I just went through this myelf.
Have you changed or altered DHCP server lately?  In our case, this
went on for perhaps years with no one noticing, since the workstations
all function properly.  You just can't see them using DNS.

See: http://technet.microsoft.com/en-us/library/cc787034.aspx

It is to early for me to state unequivocally that our problem is
cured, but it seems to be declining.  One of the computers
experiencing these symptoms I "fixed" by deleting the PTR record
(there was no host record) then doing ipconfig /release, then
rebooting.  ipconfig /registerdns had no effect -- other than to
occasionally grow a new crop of event as described.

OTOH, I have two W2K workstations that don't get A records in DNS.

On Thu, Nov 13, 2008 at 7:58 AM, David L Herrick
<[EMAIL PROTECTED]> wrote:
> Have several XP boxes running scheduled jobs 24/7  have been stable
for
> years. We cannot figure out what has changed
>
> Starts with a event view message like:
>
>
>
> The system failed to register host (A) resource records (RRs) for
network
> adapter
>
> with settings:
>
>
>
>    Adapter Name : {E34F4C11-E89C-4A88-9D4A-631EB25F56F4}
>
>    Host Name : NIN0036
>
>    Primary Domain Suffix : NINCAL.COM
>
>    DNS server list :
>
>                 10.10.30.1, 10.10.30.22
>
>    Sent update to server : 10.1.1.1
>
>    IP Address(es) :
>
>      10.10.30.38
>
>
>
>  The reason the system could not register these RRs was because the
DNS
> server failed the update request. The most likely cause of this is
that the
> authoritative DNS server required to process this update request has a
lock
> in place on the zone, probably because a zone transfer is in progress.
>
>
>
>  You can manually retry DNS registration of the network adapter and
its
> settings by typing "ipconfig /registerdns" at the command prompt. If
> problems still persist, contact your DNS server or network systems
> administrator.
>
>
>
> Sometimes "ipconfig /registerdns works or a release and renew --- more
often
> the machine reports it cannot do it (insufficient resources or some
such)
> and a reboot is required
>
> Note I have not a clue as to where the 10.1.1.1 address is coming from
L
>
> Additionally if a job was active we get something like:
>
>
>
>
>
> Windows cannot access the file \\NTS0\c\apps\plb\code\plbwin.exe for
one of
> the following reasons:  there is a problem with the network
connection, the
> disk that the file is stored on, or the storage  drivers installed on
this
> computer; or the disk is missing.  Windows closed the program
plbwin.exe
> because of this error.
>
>
>
> Program: plbwin.exe
>
> File: \\NTS0\c\apps\plb\code\plbwin.exe
>
>
>
> The error value is listed in the Additional Data section.
>
> User Action
>
> 1. Open the file again.  This situation might be a temporary problem
that
> corrects itself when the program runs again.
>
> 2.  If the file still cannot be accessed and
>
>                 - It is on the network,  your network administrator
should
> verify that there is not a problem with the network and that the
server can
> be contacted.
>
>                 - It is on a removable disk, for example, a floppy
disk or
> CD-ROM, verify that the disk is fully inserted into the computer.
>
> 3. Check and repair the file system by running CHKDSK. To run CHKDSK,
click
> Start, click Run, type CMD, and then click OK. At the command prompt,
type
> CHKDSK /F, and then press ENTER.
>
> 4. If the problem persists, restore the file from a backup copy.
>
> 5. Determine whether other files on the same disk can be opened. If
not, the
> disk might be damaged. If it is a hard disk, contact your
administrator or
> computer hardware vendor for  further assistance.
>
> Additional Data
>
> Error value: C000009A
>
> Disk type: 1
>
>
>
>
>
> Thanks in advance for any clues
>
>
>
>
>
> David
>
> This email and any attached files are confidential and intended solely
for
> the intended recipient(s). If you are not the named recipient you
should not
> read, distribute, copy or alter this email. Any views or opinions
expressed
> in this email are those of the author and do not represent those of
Names
> in the News. Warning: Although precautions have been taken to make
sure no
> viruses are present in this email, the company cannot accept
responsibility
> for any loss or damage that arise from the use of this email or
attachments.
>
>
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~


This email and any attached files are confidential and intended solely for the 
intended recipient(s). If you are not the named recipient you should not read, 
distribute, copy or alter this email. Any views or opinions expressed in this 
email are those of the author and do not represent those of the Names in the 
News company. Warning: Although precautions have been taken to make sure no 
viruses are present in this email, the company cannot accept responsibility for 
any loss or damage that arise from the use of this email or attachments.

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to