Re: * 1058 and 1030




I do not know if you are still listening but I had the same issue but it
was from one of my DCs which was also a DNS server. I do not know why
but when I checked my DNS settings, I found that my one DC\DNS server
was not allowing zone transfers. Once I configured it to allow, the
messages went away. I was also not capable from the server itself, to
access \\servername\sysvol, \\servername\d$ or c$.

wrote:
> *I'm not sure how much time you have to resolve this
> issue. There is a quick work around that would allow you
> to look at this in greater detail at a time when things
> don't seem so hectic. The five minute event posting is
> normal, under the circumstances that you're experiencing.
> I'm assuming that this is happening on one of two domain
> controllers?! The DC looks for Group Policy information
> in SYSVOL, via \\yourdomain\SYSVOL. I'm sure on the
> offending DC, if you type \\yourdomain\SYSVOL, you'll get
> an error stating that the specified path is unavailable.
> It's not likely a DNS issue directly responsible for the
> failure. Remember, Group Policy processing occurs
> locally. The information must be up to date so that it
> can be shared. DNS, can cause issues related
> to "Replication", however, if you're having such issues
> you would of likely reported "Failed replication
> attempts", or something like this. FRS, File Replication
> Services is responsible for maintaining the SYSVOL. What
> it sounds like, Active Directory is not allowing it to
> publish, because it is out of sync. I bet you can get to
> the SYSVOL share locally, by typing \\YourDC and not by
> typing \\yourdomain? FRS can fail for a number of
> reasons. I usually see this when someone begins to
> utilize Distributed File Services, with too large of
> files. Under this scenario, the staging area fills up,
> FRS stops functioning, which later leads to the error
> you're having now. There are other issues with FRS that
> can cause the same issue.
>
> The quick fix, is not something you really should be
> performing, unless you had some serious issue relating to
> something like, no one can logon?!
> >-----Original Message-----
> >We keep on getting error in event log on our 2003 Server
> >DC. The error 1058 Windows caanot access the file
> >gpt.ini for GPO CN={AED8...} ... The file must be
> present
> >at the location... (Access is denied). Group Policy
> >processing aborted. Then acompanied by error 1030
> >Windows cannot query for the list of Group Policy
> >Objects...
> >
> >This errors keep on recurring every 5 minutes. We tried
> >fixing it by performing the steps in Knowledge Base
> >Article 830676 (dfsutil /PurgeMupCache) but it did not
> >resolve the problem. We also put the following entries
> >in HOSTS file:
> >192.168.1.xxx domain.com (first DC)
> >192.168.1.xxx domain.com (second DC)
> >but still did not resolve the problem. When we use "net
> >use * \\server\sharedname" command it prompt us to enter
> >user id and password, but could not map the network
> drive.
> >
> >We searched the Internet and at this point there seems
> to
> >be no resolution this problem. Does anyone have any
> idea?
> >
> >John
> >.
> > *



--
trex0314
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message786077.html

.



Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: how do i move primary DC from one machine to another
    ... Test omitted by user request: DNS ... Connecting to directory service on server WIN2003DC. ... Replication Site Latency Check ...
    (microsoft.public.windows.server.general)
  • Re: error 8254 DNS Lookup failure
    ... FYI, I repointed the DNS to one server, deleted the contents of _MSDCS ... > in the same site, Replication has been fine up until yesterday, the ... > Starting test: CrossRefValidation ...
    (microsoft.public.win2000.dns)
  • Re: WINS and DNS issue
    ... When I said the that DNS server is configured to to replicate to all other ... Ive had a look at the options under replication, ... It says to set this if you want a 2000 server to load the zone. ...
    (microsoft.public.win2000.dns)